SHA3-384 hash generator
SHA3-384 produces a 384-bit digest with the SHA-3 sponge construction. It offers roughly 192 bits of collision resistance, making it the SHA-3 counterpart to SHA-384 for high-assurance applications. This SHA3-384 generator hashes text or uploaded files in your browser.
Example
Input:
The quick brown fox jumps over the lazy dogSHA3-384 hash:
7063465e08a93bce31cd89d2e3ca8f602498696e253592ed26f07bf7e703cf328581e1471a7ba7ab119b1a9ebdf8be41SHA-3 vs SHA-2
SHA-3 is not an upgrade of SHA-2 but a completely different design. After the attacks on MD5 and SHA-1, NIST ran an open competition (2007–2012) to obtain a backup hash based on different mathematics. The winner, Keccak by Bertoni, Daemen, Peeters and Van Assche, became FIPS 202 in 2015. Instead of the Merkle–Damgård structure, it uses a sponge: input is absorbed into a 1600-bit state and output is squeezed out, with 24 rounds of the Keccak-f permutation in between. SHA-2 remains secure, so SHA3-384 is chosen mainly for diversity, length-extension resistance or where a specification requires it.
SHA3-384 at a glance
| Property | Value |
|---|---|
| Digest size | 384 bits (48 bytes, 96 hex characters) |
| Rate / capacity | 832 / 768 bits |
| Collision resistance | About 192 bits |
| Preimage resistance | About 384 bits |
| Length extension | Not vulnerable |
The larger capacity leaves less room for input per permutation (104 bytes), so SHA3-384 is slower than SHA3-256 — roughly 30% in typical software implementations. That is the trade-off for its bigger security margin.
When to use it
- Pairing with 384-bit elliptic curves (P-384) where a specification prefers SHA-3 over SHA-2.
- Long-term integrity for archives and records that must stay trustworthy for decades.
- Security profiles requiring 192-bit strength with algorithm diversity from SHA-2.
Test vector: SHA3-384 of abc begins with ec01498288516fc926459f58e2c6ad8d…, matching the NIST examples for FIPS 202.
Comparing hashes across tools
The tool encodes text as UTF-8. Python’s hashlib.sha3_384(s.encode()).hexdigest() and openssl dgst -sha3-384 should match exactly; if not, check for trailing newlines and line endings. Output can be shown in lowercase or uppercase — the value is the same.
For a comparison with SHA-2’s equivalent, see SHA-384. For 256-bit strength, SHA3-512 is the next step up. SHA-3 is a fast hash, so do not use it to store passwords. Hashing happens locally.
SHA3-384 in other languages
// Node.js
crypto.createHash("sha3-384").update(data).digest("hex");
// Java 9+
MessageDigest.getInstance("SHA3-384").digest(bytes);
// Go 1.24+ (earlier: golang.org/x/crypto/sha3)
sha3.Sum384(data)
// .NET 8+, where the operating system supports it
SHA3_384.HashData(bytes);Keccak-384 is not SHA3-384
Before FIPS 202 was finalized, NIST changed the padding rule of Keccak, adding domain-separation bits. Libraries written against the original submission, and anything labeled “Keccak”, such as the Keccak hash generator and Ethereum's Keccak-256, therefore produce different output for the same input. If your value never matches, check which of the two the other system actually uses.