Overview
Introduction
SHA3-384 sits between SHA3-256 and SHA3-512 in the SHA-3 family, offering a wider security capacity than SHA3-256 at the cost of somewhat lower throughput per byte hashed.
This tool computes SHA3-384's 384-bit digest of any text you provide, entirely in your browser, for matching specs that require this exact SHA-3 variant.
What Is SHA3-384 Hash Calculator?
SHA3-384 is part of the SHA-3 family standardized by NIST in FIPS 202 (2015), producing a 384-bit digest (96 hex characters) via the same Keccak-f[1600] sponge construction underlying every SHA-3 variant, configured with a wider internal capacity than SHA3-256.
That wider capacity trades some throughput for a larger security margin, a pattern shared with SHA-2's SHA-384, though the two use entirely unrelated internal designs.
How SHA3-384 Hash Calculator Works
Your UTF-8 encoded text is padded with SHA-3's domain-separated multi-rate padding and absorbed into a 1600-bit internal state through repeated Keccak-f permutation rounds, using SHA3-384's specific rate/capacity split.
Once all input is absorbed, 384 bits are squeezed out of the state and hex-encoded into the 96-character digest this tool returns.
When To Use SHA3-384 Hash Calculator
Use SHA3-384 when a specific standard, certificate profile, or protocol requires it by name.
For general-purpose SHA-3 hashing without that constraint, SHA3-256 is the more commonly deployed choice; reach for SHA3-384 specifically when you need to match a spec calling for 384-bit output within the SHA-3 family.
Often used alongside SHA3-256 Hash Calculator, SHA3-512 Hash Calculator and Random SHA3-384 Hash Generator.
Features
Advantages
- Wider security capacity than SHA3-256, useful when a spec calls for that larger margin.
- Structurally independent from SHA-2, offering cryptographic diversity for defense-in-depth designs.
- Naturally resistant to length-extension attacks, like every SHA-3 sponge-construction variant.
Limitations
- Slower per byte than SHA3-256 due to its narrower absorption rate, on top of producing more output.
- Less commonly required in real-world protocols than SHA3-256 or SHA-256.
- Not related to or interchangeable with SHA-384 (SHA-2) despite sharing the same output length.
Examples
Best Practices & Notes
Best Practices
- Choose SHA3-384 to match a specific spec requirement, not as a general-purpose default over SHA3-256.
- Don't assume SHA3-384 and SHA-384 (SHA-2) are interchangeable, they use unrelated designs and produce different digests.
- If throughput matters and 384-bit SHA-3 output isn't a hard requirement, SHA3-256 is the faster, more common choice.
Developer Notes
This tool uses @noble/hashes' audited SHA-3/Keccak implementation, computing the digest synchronously in the browser from the UTF-8 byte encoding of your input via TextEncoder.
SHA3-384 Hash Calculator Use Cases
- Matching a certificate profile or protocol that specifically requires SHA3-384
- Computing a wider-capacity SHA-3 digest for a defense-in-depth design
- Reproducing a known SHA3-384 test vector while debugging another implementation
- Cross-checking a value from a system that already outputs SHA3-384 digests
Common Mistakes
- Assuming SHA3-384 and SHA-384 produce the same or related output; they're unrelated algorithms that happen to share an output length.
- Choosing SHA3-384 by default instead of the more common SHA3-256 without a specific requirement.
- Underestimating the throughput cost of the wider capacity when hashing large volumes of data.
Tips
- If nothing specifically requires SHA3-384, SHA3-256 is the more common, faster SHA-3 choice.
- Keep SHA3-384 and SHA-384 (SHA-2) digests clearly labeled in any system that computes both, they're easy to mix up given the identical output length.