SHA-384 hash generator
Tool processing runs in your browser — your pastes/files are not uploaded to our servers for processing. Ads (if shown) load separately and do not receive your tool inputs.Advertising · Details
Quick answer
SHA-384 produces a 384-bit (96-hex-character) digest from the SHA-2 family. TryDevSnip runs it with Web Crypto locally — your input is not uploaded to our servers for hashing.
SHA-384 truncates a SHA-512-class construction and is common when specs ask for a longer digest than SHA-256 without full SHA-512 output.
Digest size: 384-bit (96 hex chars)
SHA-384 is suitable for integrity and many TLS profiles. Still avoid raw SHA-384 as a password storage scheme.
SHA-384 at a glance
| Digest size | 384-bit (96 hex chars) |
|---|---|
| Output form | Lowercase hex, 96 characters, fixed length regardless of input |
| Reversible? | No — one-way; SHA-384 shares its internal construction with SHA-512 (same round function, different initial values) and is simply truncated to a shorter output |
| Runs where | In your browser via the Web Crypto API (crypto.subtle.digest) — input is never uploaded |
Reading a checksum comparison
SHA-384 sees far less everyday use than SHA-256 or SHA-512, so when a comparison fails here it is worth double-checking you copied the full 96-character string before suspecting the file itself.
- Hash the right thing. Digesting an archive is not the same as digesting the file inside it, and a trailing newline changes a text digest. Most "wrong hash" reports are actually a different input.
- Compare case-insensitively. The same digest is printed lowercase by some tools and uppercase by others. A mismatch in case alone is not a mismatch.
- One bit changes everything. A single altered byte produces a completely different digest, so "nearly matching" hashes carry no meaning — it is equal or it is not.
- Matching proves integrity, not trust. As with any current SHA-2 member, a correct match from a source you trust is meaningful evidence of integrity. It says nothing about authenticity if the source supplying both the file and the hash can't be trusted.
- Not a password hash. A long digest is not a substitute for a slow one. Credentials need a deliberately slow, salted function such as Argon2, bcrypt, or scrypt — not SHA-384.
Other hashes: SHA-1 · SHA-256 · SHA-512 · MD5
Frequently asked questions
How do I generate a SHA-384 hash?
SHA-384 produces a 384-bit (96-hex-character) digest from the SHA-2 family. TryDevSnip runs it with Web Crypto locally — your input is not uploaded to our servers for hashing.
How long is a SHA-384 digest?
SHA-384 outputs a 384-bit (96 hex chars) hexadecimal string on TryDevSnip.
Is SHA-384 safe for passwords?
SHA-384 is suitable for integrity and many TLS profiles. Still avoid raw SHA-384 as a password storage scheme.
Is my text or file uploaded?
No. TryDevSnip hashes in your browser. Nothing you type or select is uploaded to our servers for processing.