SHA3-384 Hash Generator
Turn any text into its 96-character SHA3-384 hash instantly.
How to use the SHA3-384 Hash Generator
- Type or paste your text in the box.
- The SHA3-384 hash appears as you type.
- Click Copy to grab the result.
About the SHA3-384 Hash Generator
SHA3-384 produces a 384-bit digest written as 96 hexadecimal characters. Like the rest of the family it is Keccak underneath — the algorithm by Guido Bertoni, Joan Daemen, Michaël Peeters and Gilles Van Assche that won the NIST SHA-3 competition in 2012 and was standardised as FIPS 202 in 2015.
The 384-bit sizes exist for a specific reason: they pair naturally with 384-bit elliptic curves and with the “top secret” tier of cryptographic suites, where a 256-bit digest is considered to be cutting the margin too fine. A 384-bit hash gives 192-bit collision resistance, sitting deliberately between SHA3-256 and SHA3-512. In practice, if you are choosing SHA3-384 it is usually because a compliance profile or a key size told you to, not because 256 bits was not enough.
Worth knowing: inside Keccak, a wider digest means a larger “capacity”, which leaves a smaller rate — so SHA3-384 actually absorbs fewer bytes per permutation than SHA3-256 and is therefore slower per byte, not faster. That is the opposite of the SHA-2 family, where SHA-512 often outruns SHA-256 on 64-bit hardware. SHA-3 as a whole is generally slower than SHA-2 in software while being efficient in hardware, and none of this was because SHA-2 failed — it did not, and remains secure. SHA-3 was standardised as a structurally different backup, using a sponge construction instead of SHA-2’s Merkle–Damgård construction, which also makes SHA3-384 immune to length-extension attacks.
Frequently asked questions
Can I decrypt or reverse a SHA3-384 hash?
No. Hashing is one-way and the input is not stored inside the digest, so there is nothing to reverse. Any “SHA-3 decrypter” is just a lookup table of previously hashed common strings.
Why is my SHA3-384 hash always 96 characters?
SHA3-384 always outputs 384 bits, and each hex character represents 4 bits, so every hash is exactly 96 characters no matter how long the input is.
Is SHA3-384 faster than SHA3-512?
Yes, slightly — a narrower digest means a smaller capacity and a larger rate, so more input is absorbed per permutation. Both are slower than SHA3-256, and the difference rarely matters unless you are hashing at high volume.
When would I actually pick SHA3-384?
Usually when a standard, key size or compliance profile calls for a 384-bit digest — for example to pair with a 384-bit elliptic curve. For general-purpose hashing, SHA3-256 is the more common choice.
Is my text sent anywhere?
Your text is sent to our server to be hashed, because browsers cannot compute SHA-3. It is hashed and immediately discarded — never logged, never stored.