Hash Generator MD5, SHA-1, SHA-256, SHA-384 and SHA-512 hashes — computed locally as you type.

SHA-384 Hash Generator

Generate a 384-bit SHA-384 hash from any text — instant, free, and computed locally in your browser.

All hashing happens locally in your browser — your text is never uploaded to any server.

What is SHA-384?

SHA-384 is a member of the SHA-2 family: essentially SHA-512 computed with different initial values and then truncated to 384 bits. The digest is 96 hexadecimal characters long. The extra length gives a larger security margin than SHA-256, and the truncation makes length-extension attacks impractical.

Example: the SHA-384 hash of hello is 59e1748777448c69de6b800d7a33bbfb9ff1b463e44354c3553bcdb9c666fa90125a3c79f90397bdf5f6a13de828684f — the tool above is pre-filled so you can see it live.

Is SHA-384 secure?

Yes. SHA-384 shares SHA-512's strong design and offers 192 bits of collision resistance — comfortably beyond any known attack. It is approved for government and regulated use and commonly appears alongside the P-384 elliptic curve in TLS certificates and cipher suites.

Common uses of SHA-384

Other hash generators

Need a different digest? Pick another algorithm — each has its own page:

Or go back to the Hash Generator homepage to see all five hashes at once.

Why does my hash not match another tool?

Hashes are computed over bytes, not characters, so two inputs that look identical can still produce different digests. The three usual causes:

Digest sizes at a glance

Every algorithm has a fixed output length, so a quick character count tells you whether a pasted hash is complete or truncated:

AlgorithmBitsHex characters
MD512832
SHA-116040
SHA-25625664
SHA-38438496
SHA-512512128

Letter case is only display formatting: toggling Uppercase hex does not change the underlying value, and two digests that differ only by case are the same hash.

Frequently asked questions

How many characters is a SHA-384 hash?

A SHA-384 hash is always 96 hexadecimal characters, representing 384 bits, regardless of input size.

Why does SHA-384 exist if there is SHA-512?

SHA-384 is SHA-512 with different initial values, truncated to 384 bits. The truncation hides part of the internal state, which blocks length-extension attacks, and the 384-bit size matches the security level of the P-384 elliptic curve used in high-assurance TLS.

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

When a compliance regime asks for it, when pairing with P-384 certificates, or when you simply want a bigger security margin at little performance cost on 64-bit systems. Otherwise SHA-256 is the standard default.