About SHA-384 Hash
SHA-384 Hash returns the 384-bit output of the SHA-512 branch of SHA-2, shown as 96 hexadecimal characters. It is not a truncated SHA-512 but an independent member of the family with its own initial state, built on the wider 1024-bit block design, so its word size and round structure differ from SHA-256.
That heritage is the reason to pick it. Because it belongs to the 64-bit branch of SHA-2, SHA-384 has a long record in protocols that already work with the wider construction, and its larger digest leaves a comfortable security margin — many certificate profiles and government standards accept or prefer it alongside SHA-256.
The trade-off is cost: it processes data in larger blocks and produces a longer value, so it is measurably slower than SHA-256 for the same input. Most people reach for it only when a standard or a counterparty names it specifically.
How to use SHA-384 Hash
- 1 Enter the text you want to fingerprint with SHA-384.
- 2 The 96-character digest is produced using the browser's native crypto engine.
- 3 Copy the hex string to compare against the SHA-384 value you were given.
Frequently asked questions
Is SHA-384 just SHA-512 cut short?
No. It uses different initial values and is defined as an independent function, even though it shares the block size and round count with SHA-512. The genuinely truncated variants are SHA-512/256 and SHA-512/224; SHA-384 is not one of them.
Why would I choose SHA-384 over SHA-256?
A longer digest means a larger collision margin and more headroom against future cryptanalysis. In practice the difference rarely matters day to day, so choose it when a standard or certificate profile calls for it.
Does a longer hash keep my data more private?
No. Digest length affects collision resistance, not confidentiality. A hash never conceals an input against guessing — if the input is short or predictable, anyone can hash candidates until one matches.
How long is the output exactly?
96 hexadecimal characters, representing 384 bits or 48 bytes, regardless of how long the input is.
Free, online, and private
Free to use
SHA-384 Hash is completely free. There is no account to create, no login, and no hidden charge or usage limit.
Runs online in your browser
It is a free online tool that runs entirely in your browser. Nothing to download or install — open the page and start using it right away.
Your data stays private
All processing happens locally on your device. Your input is never uploaded, stored, or tracked, so it never leaves your browser.
How SHA-384 Hash behaves in detail
These are the specifics of this implementation — the exact ranges, defaults and fixed settings you are working with.
| Parameter | Value |
|---|---|
| Algorithm | SHA-384, via crypto.subtle.digest |
| Digest width | 96 lowercase hex characters (384 bits) |
| Input handling | UTF-8 encoded before hashing, so accented letters cost more than one byte each |
| Empty input | hashed, not refused — 38b060a751ac96384cd9327eb1b1e36a21fdb71114be07434c0cc7bf63f6e1da274edebfe76f65fbd51ad2f14898b95b |
| Update mode | live on every keystroke, like the other hash pages in this set |
Compiled from the implementation of this tool and checked against it by itoolnet.
What SHA-384 Hash does not do
Knowing the edges of a tool saves more time than another list of its features. These are the cases where it will not do what you might expect.
- Nothing about the digest is configurable: the full 96 characters are always printed, with no option for base64, for uppercase, or for the truncated SHA-384/192 form that some protocols specify.
- There is no keyed mode and no comparison field on the page. A keyed digest needs the HMAC SHA-384 tool, and checking a published value means putting the two strings side by side and comparing them by eye.
- The input is text only. A file's SHA-384 is taken over its raw bytes, so pasting the file's contents re-encodes everything above U+007F as UTF-8 and the resulting digest will not match the published one.
Tested and documented by itoolnet, the team that builds and maintains this site.