Developer · Hashing
SHA-384 hash generator.
Compute the SHA-384 digest of text or a file as hex or Base64, locally in your browser using SubtleCrypto.
How to use the SHA-384 generator
- Type or paste text into the box, or choose a file to hash instead.
- Press the generate button and wait a moment for large files.
- Copy the value, then compare it with the checksum or signature you were given.
About SHA-384
SHA-384 produces a 384-bit digest, written as 96 hexadecimal characters. SHA-384 is a SHA-2 variant that runs the SHA-512 algorithm with different starting values and truncates the result. It appears in TLS cipher suites and in Subresource Integrity attributes, where a browser checks a script against a hash you publish.
Your input stays on your device
The calculation runs in your browser inside a sealed frame that cannot make network requests, so the text, file or key you enter is never uploaded. The advertising on this page sits outside the frame and cannot see what you enter.
- Line endings and trailing spaces change the result, so paste exactly what you mean to hash.
- Hashing is one-way: you cannot recover the original input from the digest.
- If a file and text are both provided, the file is hashed.
About SHA-384
SHA-384 is a SHA-2 function from FIPS 180-4. It runs the SHA-512 compression function on 64-bit words with different starting values and truncates the result to 384 bits (48 bytes, 96 hexadecimal characters).
You will meet it in the TLS 1.3 cipher suite TLS_AES_256_GCM_SHA384 (RFC 8446) and in the sha384- digests used for Subresource Integrity attributes, where the value is the Base64 form: switch the output to Base64 above to copy it. Text is hashed as UTF-8 bytes.
Known-answer examples
Use these to confirm the tool matches the standard. The Try button loads the input.
| Input | SHA-384 (hex) | Source | |
|---|---|---|---|
| Empty string | 38b060a751ac96384cd9327eb1b1e36a21fdb71114be07434c0cc7bf63f6e1da274edebfe76f65fbd51ad2f14898b95b | zero-length input | |
| abc | cb00753f45a35e8bb5a03d699ac65007272c32ab0eded1631a8b605a43ff5bed8086072ba1e7cc2358baeca134c825a7 | FIPS 180-4 / RFC 6234 | |
| abcdefghbcdefghi… (112 chars) | 09330c33f71147e83d192fc782cd1b4753111b173b3b05d22fa08086e3b0f712fcc7c71a557e2db966c3e9fa91746039 | FIPS 180-4 / RFC 6234 |
The empty-input digests are not among the FIPS 180-4 examples; they are the digests of a zero-length message and match OpenSSL in our test suite.
Sources (retrieved October 2026):
Frequently asked questions
How long is a SHA-384 hash?
384 bits: 48 bytes, 96 hexadecimal characters, or 64 Base64 characters. The size never changes with the input.
How is SHA-384 different from SHA-512?
Both use the same 64-bit core. SHA-384 starts from different initial values and keeps only the first 384 bits, so the two digests of the same input are unrelated strings, not truncations of each other.
How do I make a Subresource Integrity value?
Hash the exact file bytes, set the output to Base64 and prefix it with sha384-. Verify the result against the file your server actually delivers.
Is my data uploaded?
No. The digest is computed locally with SubtleCrypto. Nothing is sent or stored.
Integrity, not password storage
SHA-384 has no known practical attacks and is suitable for signatures and integrity checks. Like all fast hashes it is the wrong tool for storing passwords; use Argon2id, bcrypt or PBKDF2 as OWASP recommends.