SHA-384 Hash Generator
Turn any text into its 96-character SHA-384 hash instantly.
How to use the SHA-384 Hash Generator
- Type or paste your text in the box.
- The SHA-384 hash appears as you type.
- Click Copy to grab the result.
About the SHA-384 Hash Generator
SHA-384 sits between SHA-256 and SHA-512 in the SHA-2 family published by the NSA and NIST in 2001, and it is best understood as SHA-512 with a haircut. It runs SHA-512’s machinery — the same 64-bit words, the same rounds — but begins from a different set of initial hash values and then keeps only the leading 384 bits of the result. That gives you 96 hexadecimal characters.
The reason to want that combination is speed without bulk. Because it inherits SHA-512’s 64-bit word size, SHA-384 runs at SHA-512 pace on modern 64-bit processors — which is typically faster than SHA-256 — while emitting a digest a third shorter than SHA-512’s. You will most often meet it in high-assurance TLS cipher suites, the ones whose names end in SHA384, where it is paired with 384-bit elliptic curves so that hash strength and key strength match.
Truncation buys a real security bonus too. SHA-384 computes a 512-bit internal state but only publishes 384 bits of it, so an attacker never sees the full state — which makes it immune to the length-extension attacks that can undermine naive SHA-256 or SHA-512 constructions. There are no known practical attacks against SHA-384, and like the rest of SHA-2 it is still regarded as secure. As with every fast hash, though, it is the wrong tool for storing passwords — use bcrypt for that.
Frequently asked questions
Can I decrypt or reverse a SHA-384 hash?
No. SHA-384 is one-way, and it additionally discards 128 bits of its internal state before showing you anything. The original text simply is not present in the digest and cannot be recovered from it.
Is SHA-384 just a truncated SHA-512?
It truncates the output, but it also starts from different initial values — so SHA-384 of a text is not the first 96 characters of its SHA-512. The digests are entirely different strings.
Why is a SHA-384 hash always 96 characters?
It always outputs 384 bits and each hexadecimal character represents 4 bits, so the result is 384 divided by 4 — exactly 96 characters, no matter the input size.
When should I pick SHA-384 over SHA-256?
When you want SHA-512 speed on 64-bit hardware without a 128-character digest, or when a protocol calls for it — such as TLS suites pairing SHA-384 with 384-bit elliptic curves.
Is my text sent anywhere?
Your text is sent to our server to be hashed, because browsers cannot compute SHA-384 for you. It is hashed and immediately discarded — never logged, never stored.