SHA-384 Hash Generator
Generate the SHA-384 hash of any text instantly in your browser. UTF-8, hex or Base64 input; hex or Base64 output. Free, private, no upload.
Runs entirely in your browser. Your data is never uploaded.
What is SHA-384 Hash Generator?
SHA-384 is a SHA-2 hash with a 384-bit (96 hex character) output, built on the 64-bit SHA-512 engine with its own initial value. This tool computes the 384-bit SHA-384 digest of text or raw bytes (hex or Base64) as you type and shows it as 96 hex characters or Base64.
How to use SHA-384 Hash Generator
- Type or paste your input into Text to hash — the digest updates as you type (an empty box shows the hash of empty input).
- Choose the Input encoding: Text (UTF-8) hashes the characters as UTF-8, Hex bytes or Base64 hash the decoded raw bytes.
- Pick the Output format (hex lowercase, hex uppercase or Base64) and click Copy.
Example
abc
cb00753f45a35e8bb5a03d699ac65007272c32ab0eded1631a8b605a43ff5bed8086072ba1e7cc2358baeca134c825a7
SHA-384 of the 3 ASCII bytes "abc" (UTF-8, hex lowercase output), the standard test vector.
When to use SHA-384 Hash Generator
Use the SHA-384 text tool to hash strings: reproduce a value from documentation or code, build test vectors, compare an API signature input, or check what a program should output. Do not use it to check a downloaded file: copying file contents into a text box changes line endings and encoding, so use the SHA-384 file checksum tool. Use SHA-256 when you need maximum compatibility and a shorter value.
How SHA-384 Hash Generator works
SHA-384 uses the SHA-512 compression function: 1024-bit blocks, 80 rounds on eight 64-bit words and a 128-bit length field. It starts from a different initial value (from the 9th–16th primes) and keeps only the first six 64-bit words. Truncation also makes it resistant to length-extension attacks. The text is first converted to bytes (UTF-8 by default), so the same characters always give the same hash.
Common Use Cases
- Check the expected SHA-384 of a string in a unit test or fixture
- Hash hex bytes copied from a debugger, packet capture or protocol spec
- Compare SHA-384 output between two programming languages that disagree
- Generate deterministic identifiers or cache keys from text
- Get the Base64 form of a SHA-384 digest for headers or configuration files
Security Note
SHA-384 has no known practical attacks. Plain hashes are also not suitable for storing passwords: use a slow, salted password hash such as Argon2, scrypt or bcrypt. Everything is computed locally in your browser; nothing you type is sent anywhere.
FAQs
Why choose SHA-384 over SHA-256?
It offers a higher security margin (192-bit collision resistance), is immune to length extension because it is truncated, and is required by suites such as CNSA and TLS_AES_256_GCM_SHA384. On 64-bit CPUs it is often faster than SHA-256 for large inputs.
Where do I see SHA-384?
In Subresource Integrity attributes (integrity="sha384-…", which use the Base64 form — pick Base64 output), TLS 1.3 cipher suites and ECDSA P-384 signatures.
Why does the hash change completely when I change one character?
That is the avalanche effect every cryptographic hash is designed for: flipping one input bit changes about half of the 384 output bits, so similar inputs give unrelated digests.
Does a trailing space or newline matter?
Yes. The hash covers every byte, so abc and abc followed by a newline give different SHA-384 values. Make sure the input contains exactly the bytes you intend to hash.