Advertisement

SHA-384 hash generator

Generate the SHA-384 digest of any text with your browser's built-in Web Crypto API. SHA-384 is the 384-bit truncated variant of SHA-512, shown as 96 hex characters.

Input

SHA-384 digests are 96 hexadecimal characters. Computed with the Web Crypto API.

Needs a secure context (HTTPS or localhost) for the Web Crypto API. Nothing is uploaded.
SHA-384 digest

The digest appears below in hexadecimal.

-
Advertisement

SHA-384 in the SHA-2 family

SHA-384 runs the SHA-512 compression function with its own initial values and truncates the 512-bit result to 384 bits. Because it uses 64-bit words like SHA-512, it is fast on 64-bit processors, and the truncation gives 192 bits of collision resistance, matching the security level used in high-assurance cryptography.

Where SHA-384 is used

SHA-384 appears in TLS cipher suites, digital signatures paired with 384-bit elliptic curves (P-384), and government or enterprise standards that require a 192-bit security level. For everyday checksums it is overkill, but it is a reassuring default when you want a margin above SHA-256.

SHA-384 Hash FAQs

SHA-384 vs SHA-512: which is better?
Both are secure. SHA-384 is SHA-512 truncated to 384 bits, which neatly matches a 192-bit security level and avoids length-extension quirks of full SHA-512 in some protocols. Pick SHA-512 for the longest digest, SHA-384 for the 192-bit security sweet spot.
Why does this need HTTPS?
SHA-384 is computed with the Web Crypto API, which browsers only expose in secure contexts (HTTPS or localhost). On plain HTTP the digest cannot be computed.
How long is the output?
Always 96 hexadecimal characters (384 bits), no matter how long the input is.
Is SHA-384 quantum safe?
No hash function is fully quantum safe, but SHA-384's 192-bit collision resistance degrades to about 128 bits against quantum attacks, which is still considered safe. Larger digests are the standard hedge.
Can I reverse a SHA-384 hash?
No. SHA-384 is one-way; the only way to find an input is brute force, which is infeasible at 384 bits.
Advertisement