What this tool calculates
SHA-384 belongs to SHA-2 and outputs 384 bits, represented by 96 hexadecimal characters. It uses a distinct initialization from SHA-512; it is not correct to calculate SHA-512 and simply keep the first 96 characters. This tool calculates the SHA-384 algorithm itself.
Use this page when a specification, signature workflow or integration explicitly identifies SHA-384. Keeping the algorithm name next to an exported digest helps avoid mixing it with a truncated value from another function. Hexadecimal letter case is only a display convention; it does not change the digest bytes.
A digest alone is neither encryption nor a digital signature. To reproduce a known value, check message encoding, all whitespace and the exact file bytes. If a protocol calls for HMAC-SHA384, use the separate HMAC tool: appending a key to a message is not an equivalent construction.
Worked example
UTF-8 · abc · SHA-384
cb00753f45a35e8bb5a03d699ac65007272c32ab0eded1631a8b605a43ff5bed8086072ba1e7cc2358baeca134c825a7
How to calculate and compare
- Enter the exact text in Input text, or choose Example to load
abc. Text is encoded as UTF-8; spaces and line endings are preserved. - In single-text mode, non-empty input up to 64 KiB updates after a short pause. Click Generate hash for empty input or larger text. Changing the input clears the previous result.
- To check a saved file instead, open File checksum, confirm the algorithm, and choose or drop the file. File mode reads its original bytes and starts automatically.
For line-by-line results, enable One hash per line, choose whether to include empty lines, then click Generate hash. Line mode does not calculate automatically. CRLF, LF and CR separate records and are not included in each line's digest. Duplicate lines retain their original line numbers.
Paste only the complete hexadecimal reference into Compare expected value (optional) and click Check. Letter case and surrounding pasted whitespace are ignored; internal spaces and the wrong length are rejected. Copy retains the full result. TXT and CSV exports include identifiers, algorithm names and digests, not source text or secret keys.
Limits, privacy and next steps
Text is limited to 10 MiB and line mode to 10,000 records, including empty records before filtering. Files are limited to 50 queue entries and 1 GiB each, read sequentially in 2 MiB chunks. These limits protect browser resources; they do not guarantee fast processing on every phone. Cancel if needed. Calculation takes place in the browser, while normal page and asset requests still reach the hosting service.
Using the exact SHA-384 variant a specification requests
A SHA-384 digest is 48 bytes. Hex represents each byte with two characters, producing the 96-character value returned here. A signature or integration may encode those same digest bytes as Base64 instead; a visible length difference is not enough to conclude that the hash algorithm is wrong.
SHA-384 shares a family with SHA-512 but has different initial values. Keeping the first 96 characters of a SHA-512 digest will not reproduce SHA-384. Select SHA-384 before processing the file, and preserve the full output. If a signed document or certificate mentions SHA-384, this calculator can reproduce a raw digest, but it does not create or validate the signature or parse that container's signed byte range.
A direct check of the SHA-384 truncation mistake
Use Example on this page and on SHA-512. Compare SHA-384 of abc with the first 96 characters of SHA-512 of abc. They differ even though the displayed lengths agree.
SHA-384 / abc:
cb00753f45a35e8bb5a03d699ac65007272c32ab0eded1631a8b605a43ff5bed8086072ba1e7cc2358baeca134c825a7
SHA-512 / abc / first 96 hex characters only (NOT SHA-384):
ddaf35a193617abacc417349ae20413112e6fa4e89a97ea20a9eeee64b55d39a2192992a274fc1a836ba3c23a3feebbd
SHA-384 format and construction mistakes
| Observed problem | Why it happens | What to do |
|---|---|---|
| A shortened SHA-512 does not match | SHA-384 is not a substring of ordinary SHA-512 | Recalculate with SHA-384 selected. |
| The expected value is Base64 | The comparison field accepts hexadecimal | Decode and re-encode the digest correctly, or obtain a hex reference. |
| The certificate's signature is much longer | A signature is not the raw digest | Use the relevant signature-verification tool and signed-byte rules. |