Cryptography Tools
SHA3-384 Hash Generator
Calculate a SHA3-384 digest from UTF-8 text and inspect its 96-character lowercase hexadecimal output.
✓ Every tool runs in your browser. We do not upload your input or output.
Keyboard shortcuts
Ctrl/⌘ + Enter: process
Ctrl/⌘ + Shift + F: full screen
Esc: exit full screen
Ctrl/⌘ + F in editor: search
How to use
- Paste the text named by a SHA3-384 test or specification.
- Run the tool and read the 384-bit digest.
- Compare the full 96-character value with a trusted reference.
- Copy or download the result with the algorithm name.
Examples
Check a release note
The output length is the same as SHA-384, but the digest differs.
Release manifest v3.1
A 96-character SHA3-384 hex digest
Check a 384-bit SHA-3 value
SHA3-384 produces a fixed-length digest from the SHA-3 family. It is appropriate when a specification explicitly asks for SHA3-384, particularly when checking a known test vector. SHA-384 produces the same number of output bits but belongs to SHA-2 and yields a different value. Include the full name when storing a checksum so later readers do not infer the algorithm from length alone.
This page hashes the exact editor text after UTF-8 encoding. It does not trim whitespace or normalize line endings. When a comparison fails, review the source bytes and the other tool’s selected algorithm before assuming either implementation is broken. Uploaded text is handled locally in the browser; the site has no endpoint for digest calculation. Like other plain hashes, this result can help compare content but cannot prove who supplied it. See the NIST SHA-3 standard for the formal definition.
When writing tests, include the expected hex length as well as the value. A 96-character result helps catch accidental selection of a 256-bit or 512-bit variant. It cannot distinguish SHA3-384 from SHA-384 by length, so compare a known digest too.
Frequently asked questions
How does it differ from SHA-384?
SHA3-384 belongs to SHA-3; SHA-384 belongs to SHA-2.
Is output always 96 hex characters?
Yes. Its fixed 384-bit output is 48 bytes or 96 hex characters.
Does this encrypt data?
No. A digest is not reversible encryption.
What changes the result?
Any difference in UTF-8 bytes, including whitespace or line endings.