SHA-384 generator

5 of 1 ratings

Create a SHA-384 hash online from any text or file in seconds. This SHA-384 generator outputs a fixed 384-bit digest as a 96-character hexadecimal string. It’s ideal for file integrity verification, API signatures, package publishing, and content addressing. Common needs include SHA-384 checksum verification, SHA-384 hash of a string, and calculate SHA-384 of a file online.

What is SHA-384?

SHA-384 is a member of the SHA-2 family (alongside SHA-256/512). Technically it’s the SHA-512 algorithm with different initial values and a truncated 384-bit output. It delivers strong collision resistance with shorter digests than SHA-512, making it a good balance between security and bandwidth/storage.

How to use the SHA-384 Generator

  1. Enter text or upload a file to hash.
  2. Click Generate to compute the SHA-384 digest.
  3. Copy the 96-character hex output and compare it with a published checksum or store it for reference.

When should you use it?

  • Release validation: Publish or verify a SHA-384 checksum for installers, archives, and binaries.
  • Artifact integrity: Fingerprint build outputs in CI/CD and deployment pipelines.
  • API & signing: Use as the digest input for digital signatures (e.g., ECDSA/RSA) where SHA-384 is required.
  • Data deduplication: Create deterministic identifiers for large assets.

Who is this for?

  • Developers generating secure checksums for packages and APIs.
  • DevOps & SRE teams validating artifacts across environments.
  • Security practitioners standardizing on SHA-2 family digests.
  • Researchers & students comparing SHA-256, SHA-384, and SHA-512.

Best practices & caveats

  • Passwords: Don’t store raw SHA-384 of passwords. Use a KDF such as Argon2, bcrypt, or PBKDF2 with salt and work factors.
  • Exact bytes matter: Encoding (UTF-8 vs UTF-16), hidden whitespace, and line endings (\n vs \r\n) change the result.
  • Avalanche effect: Any 1-bit change yields a completely different digest—verify you’re hashing the intended data.
  • Interoperability: If partners expect SHA-256 or SHA-512, consider publishing multiple checksums.

Examples

SHA-384 of a string

Input:  "hello world"
Output: fdbd8e75a67f29f701a4e040385e2e23986303ea10239211af907fcbb83578b3
        e417cb71ce646efd0819dd8c088de1bd

SHA-384 of a file (command-line reference)

# macOS/*nix
shasum -a 384 /path/to/file

# Linux
sha384sum /path/to/file

# Windows PowerShell
Get-FileHash -Algorithm SHA384 "C:\path\to\file"

FAQ

Is SHA-384 secure?

Yes. SHA-384 is part of the SHA-2 family and is considered secure for integrity and signing workflows. For passwords, always use a dedicated KDF.

Can I decrypt a SHA-384 hash?

No. Hashes are one-way. “Decryption” sites only match against precomputed databases (rainbow tables).

Why doesn’t my digest match the publisher’s?

Confirm you hashed the exact same bytes—watch for encoding differences, newline changes, or hashing a zipped file instead of the raw file.

Share

Popular tools