SHA-384 Hash Generator
HG-11Paste text to get its SHA-384 hash, 96 hex characters long. Your browser computes it as you type, and the text is read as UTF-8.
Runs in your browser. Nothing is uploaded.
Text (hashed as UTF-8)
SHA-384 hash
How to use it
- Type or paste your text into the input box. Sample loads the quick brown fox sentence.
- The SHA-384 hash appears as you type.
- Choose lowercase hex, UPPERCASE hex or Base64. Base64 is the form used in sha384- integrity attributes.
- Tick Ignore one trailing line break if your text ends with a newline you do not want hashed.
- Copy the result, or download it as a .txt file.
What SHA-384 is
SHA-384 is part of the SHA-2 family in FIPS 180-4. It uses the SHA-512 steps with its own starting values and keeps the first 48 bytes of the result, which is 96 hex characters or 64 Base64 characters. Your browser computes it through the Web Crypto API, so no hashing code was added for it on this page. It is the same function you would call with crypto.subtle.digest and the name SHA-384.
Where SHA-384 shows up
Subresource Integrity attributes on script and link tags accept sha256-, sha384- and sha512- values, with the digest written in Base64. Pick the Base64 output here to get that form for text you hashed. TLS cipher suites and some signature schemes also name SHA-384. It is a fast hash, so on its own it is the wrong choice for storing passwords, which needs a slow, salted function.
Exactly what gets hashed
The text is encoded as UTF-8 and hashed as typed. A trailing space or line break changes the result, so use the trailing line break option when your text came from a file that ends with a newline. A lone surrogate half is replaced with U+FFFD first. The tool hashes text, not files: a binary file or a file saved with different line endings would give a different hash than the same words typed here.
Questions people ask
How do I get the SHA-384 hash of a string?
Type or paste the string into the input box and the SHA-384 hash appears immediately. Choose hex or Base64, then copy the value or download it as a .txt file. Hashing happens in your browser.
How long is a SHA-384 hash?
It is 384 bits, so 48 bytes. In hex that is 96 characters, and in Base64 it is 64 characters with no padding. The length stays the same however much text you hash.
What is the difference between SHA-384 and SHA-512?
They run the same algorithm on 64-bit words, but SHA-384 starts from different values and returns only the first 384 bits. The two produce unrelated-looking results for the same text. SHA-384 also resists length extension on its output better, since part of the state is never shown.
Can I use this for a Subresource Integrity hash?
Only for text you paste in. An integrity value is the Base64 digest of the exact bytes of the file the browser downloads, so a text box can mislead you on line endings or encoding. For a real file, hash the file on disk with a command line tool.
Is SHA-384 secure?
No practical attacks are known on SHA-384, and it is approved in FIPS 180-4. It is a quick hash, so do not use it by itself to store passwords; use bcrypt, scrypt or Argon2 with a salt for that.
Why is my SHA-384 hash different from another tool?
Most often the input bytes differ: a final newline, different line endings, or another text encoding. This page hashes UTF-8 exactly as typed. Check those three things on the other side before suspecting the algorithm.
About this tool
SHA-384 is computed by your browser's built-in Web Crypto. It is SHA-512 with different starting values and a result cut to 48 bytes (96 hex characters), and it is the digest behind the sha384- value in a Subresource Integrity attribute. It is a fast general-purpose hash, so do not use it alone to store passwords: that needs a slow, salted function such as bcrypt, scrypt or Argon2, which this tool is not. The text is hashed exactly as typed, as UTF-8 (a lone surrogate half becomes U+FFFD first), so a trailing line break or a space changes the result; "Ignore one trailing line break" removes one. It hashes text, not files: a file saved with different line endings would give a different hash than the same words typed here.