SHA-384 is a member of the SHA-2 family from NIST FIPS 180-4. It is a truncated form of SHA-512 with different initial values, producing a 384-bit (48-byte) digest shown as 96 hex characters.

How is SHA-384 different from SHA-512?

SHA-384 uses the same 64-bit internal computation as SHA-512 but starts from distinct initialisation constants and outputs only the first 384 bits. This makes it resistant to length-extension attacks that affect SHA-512.

Is my text sent anywhere?

No. The digest is computed entirely in your browser via the Web Crypto API, so the input never leaves your device and is safe for sensitive data.

When should I choose SHA-384?

SHA-384 is common in TLS cipher suites and certificates where a 192-bit security level is desired and length-extension resistance matters, while keeping output shorter than full SHA-512.

SHA-384 Hash Generator

What this SHA-384 generator does

This tool computes the SHA-384 cryptographic hash of any text you enter, returning a fixed 384-bit value as 96 hexadecimal characters. SHA-384 appears throughout modern TLS, code-signing, and certificate infrastructure where a strong 64-bit-word hash with truncated output is preferred.

How it works

SHA-384 belongs to the SHA-2 family defined in NIST FIPS 180-4. Internally it runs the same compression function as SHA-512 — operating on 64-bit words across 80 rounds in 1024-bit message blocks — but seeds the eight working variables with a different set of initial hash values. After processing the padded message, only the first 384 bits (the first six 64-bit words) of the state are output. This tool calls the browser’s native crypto.subtle.digest("SHA-384", data) so results match the standard byte-for-byte.

Tips and notes

Because output is truncated, SHA-384 resists the length-extension attacks that affect plain SHA-256 and SHA-512.
The same input always produces the same digest; one changed byte changes the entire hash.
Example: the empty string hashes to 38b060a751ac96384cd9327eb1b1e36a21fdb71114be07434c0cc7bf63f6e1da274edebfe76f65fbd51ad2f14898b95b.
Do not use a bare hash for storing passwords — use a salted slow KDF such as Argon2 or bcrypt.