How long is a SHA-384 hash?

SHA-384 produces a 384-bit value, shown as a 96-character hexadecimal string.

How is SHA-384 related to SHA-512?

SHA-384 uses the same algorithm and block structure as SHA-512 but starts with different initial values and truncates the output to 384 bits.

When should I choose SHA-384 over SHA-256?

Choose SHA-384 when a longer security margin is required, such as in certain certificate or signature profiles. For most general use, SHA-256 is sufficient.

Is my input uploaded?

No. SHA-384 is computed entirely in your browser.

SHA-384 Hash Generator

Generate a SHA-384 hash from any text directly in your browser.

This tool runs entirely in your browser. Nothing you type is uploaded, logged or stored, which makes it safe for keys, tokens and other sensitive values.

What Is SHA384?

SHA-384 is a cryptographic hash function from the SHA-2 family. It produces a 384-bit hash value, rendered as a 96-character hexadecimal string. It is closely related to SHA-512: it uses the same algorithm and block structure but starts with a different initial hash value and truncates the final state to 384 bits.

SHA-384 is used in contexts that want a longer security margin than SHA-256 but do not need the full 512-bit output of SHA-512. It appears in some digital signature schemes, certificate profiles, and high-assurance integrity verification workflows.

Like other SHA-2 functions, SHA-384 is deterministic and one-way. The same input always produces the same 96-character digest, and the digest cannot be reversed to recover the input.

How to Use SHA384

Enter your text in the Input Text field.
The SHA-384 hash appears instantly as a 96-character hex string.
Compare the digest against a reference value if verifying integrity.
Copy the hash to your clipboard or download it as a text file.
Use Sample Data to load a standard test string for verification.

Features

Live SHA-384 hashing with no network calls.
384-bit output rendered as a 96-character hexadecimal string.
Copy to clipboard and download as a .txt file.
Input character counter.
Sample Data button for verification against a known vector.
Fully client-side computation via a trusted JavaScript crypto library.

Common Use Cases

High-assurance integrity verification where a longer digest than SHA-256 is desired.
Reproducing SHA-384 checksums published for sensitive software or data artifacts.
Digital signature and certificate workflows that specify SHA-384.
Comparing SHA-2 family outputs to observe how digest length scales.
Creating longer fingerprints for content-addressed storage.

How It Works

SHA-384 shares SHA-512's design. It pads the message to a multiple of 1024 bits, appends a 128-bit length field, and processes each 1024-bit block through eighty rounds of mixing using a 512-bit internal state. The difference is that SHA-384 uses a distinct set of initial values and outputs only the first 384 bits of the final state, giving a 96-character hex digest.

Because it inherits SHA-512's round structure, SHA-384 offers a large security margin while producing a shorter, more manageable digest than the full 512-bit output.

This tool computes SHA-384 locally with CryptoJS. No input or hash leaves your browser.

Security and Privacy Considerations

SHA-384 is currently considered secure for integrity verification and digital signatures. No practical collision attack is known, and its 384-bit output provides a comfortable security margin.

SHA-384 is not a password storage algorithm. It is fast and unsalted. Use bcrypt, scrypt, or Argon2 for password hashing.

Hashing is one-way. SHA-384 cannot be decrypted back to the original input.

A limitation to keep in mind: the 96-character digest is longer than SHA-256's 64 characters, which takes more storage and bandwidth. For many applications SHA-256 is sufficient; SHA-384 is chosen when extra margin is explicitly required.

All processing is local, so your input never leaves your device.

When to Use SHA384

High-assurance integrity verification where a longer digest than SHA-256 is desired.
Digital signature and certificate workflows that specify SHA-384.
Reproducing SHA-384 checksums published for sensitive software or data artifacts.
Creating longer fingerprints for content-addressed storage.

When Not to Use SHA384

Password storage — it is fast and unsalted; use bcrypt, scrypt, or Argon2.
Cases where the 96-character digest's extra storage and bandwidth are not justified and SHA-256 would suffice.
Any case where you need to recover the original data — hashing is one-way.

Practical Examples

Certificate profile conformance: some X.509 certificate and signature profiles mandate SHA-384; this tool lets you compute the matching digest during development or verification.
High-margin integrity: for long-lived archives where you want more collision margin than SHA-256 but a shorter digest than SHA-512, SHA-384 is a deliberate middle ground.

Comparison

SHA-384 vs SHA-256: SHA-384 produces a 96-character digest with a larger security margin; SHA-256 produces a 64-character digest and is sufficient for most uses. Choose SHA-384 when a profile or policy requires the extra margin.
SHA-384 vs SHA-512: both use SHA-512's internal structure, but SHA-384 truncates the output to 384 bits, giving a shorter 96-character digest than SHA-512's 128 characters.

Frequently Asked Questions

How long is a SHA-384 hash?: SHA-384 produces a 384-bit value, shown as a 96-character hexadecimal string.
How is SHA-384 related to SHA-512?: SHA-384 uses the same algorithm and block structure as SHA-512 but starts with different initial values and truncates the output to 384 bits.
When should I choose SHA-384 over SHA-256?: Choose SHA-384 when a longer security margin is required, such as in certain certificate or signature profiles. For most general use, SHA-256 is sufficient.
Is SHA-384 safe for passwords?: No. It is too fast and unsalted. Use bcrypt, scrypt, or Argon2 for password storage.
Is my input uploaded?: No. SHA-384 is computed entirely in your browser.