SHA -384
Generate a SHA-384 hash from any text in your browser. Produces a 384-bit digest as 96 hex characters using the browser native crypto.subtle API. SHA-384 is a truncated form of SHA-512.
Text in, SHA-384 out
Every input maps to a fixed 384-bit digest (96 hex characters). Changing one byte randomises the entire output.
Hello, world!
55bc556b0d2fe0fce582ba5fe07baafff035653638c7ac0d5494c2a64c0bea1cc57331c7c12a45cdbca7f4c34a089eeb
What you will use SHA-384 for
SHA-384 fingerprints data so you can detect changes, verify integrity, and build authenticated protocols.
Security audits
Verify that a file you downloaded matches the official checksum.
API authentication
Many APIs sign requests with SHA-384 or HMAC-SHA-384.
File integrity
Detect corruption or tampering across storage and transport.
Tokens & IDs
Build deterministic IDs from input data using SHA-384.
How to generate a SHA-384 hash
Paste your text
Drop any text — UTF-8 is handled automatically.
Set options
Pick lowercase or uppercase.
Click Generate
Or leave auto-hash on for live updates.
Copy or download
Grab the 96-char hex digest.
Frequently asked questions
SHA-384 processes input through the Merkle-Damgård construction, producing a fixed 384-bit digest. It is deterministic and one-way.
Yes — SHA-384 is part of the SHA-2 family (FIPS 180-4). No practical preimage or collision attacks are known as of 2026.
No — hashes are one-way. Short or common inputs may be found in rainbow tables, but there is no general decryption.
Usually whitespace, trailing newlines, or line endings (LF vs CRLF). Also confirm both tools UTF-8 encode the input.
Yes. No signup, no limits, no ads. Everything runs entirely in your browser.
About SHA-384 hashing
SHA-384 is a cryptographic hash function in the SHA-2 family standardised by NIST in FIPS 180-4. It compresses arbitrary input into a fixed 384-bit digest.
Properties
- Deterministic — same input always produces the same digest.
- Fixed-size output — 384 bits / 96 hex characters.
- Avalanche — changing one input bit randomises about half the output bits.
- Hardware-accelerated in modern browsers via the Web Crypto API.
When to use which
- SHA-256 — the default for most modern protocols (TLS, JWT, Bitcoin).
- SHA-384 / SHA-512 — when you want a longer digest or run on 64-bit-heavy hardware.
- HMAC-SHA-* — for authenticated messages with a shared secret key.