About SHA-384 Hash Generator
This SHA-384 hash generator computes the SHA-384 digest of your text or file. SHA-384 produces a 384-bit value, written as 96 hexadecimal characters. It is free, needs no sign-up and runs in your browser, so nothing you enter is uploaded.
SHA-384 is a truncated form of SHA-512. It uses the same 64-bit machinery with different starting values and keeps the first 384 bits. Truncation also means it is not open to the length-extension trick that affects plain SHA-256 and SHA-512, because part of the internal state is never shown.
You will meet SHA-384 in places that ask for a stronger-than-SHA-256 margin, such as some TLS cipher suites, the P-384 elliptic curve, and the integrity attribute of web pages, where a Subresource Integrity value is written as sha384- followed by the Base64 digest. If you need that value, tick Base64 output.
The digest comes from the Web Crypto API in your browser. A SHA-384 of the text "abc" starts with cb00753f45a35e8b and is 96 hex characters long, or 64 characters in Base64.
How to use SHA-384 Hash Generator
- Choose an algorithm from the row of buttons: MD5, SHA-1, SHA-224, SHA-256, SHA-384, SHA-512, SHA3-256, SHA3-512 or CRC32. SHA-256 is a good default.
- Choose Text and type or paste your input, or choose File and pick a file from your device. The hash updates as you type.
- Read the digest in the result box. Tick Uppercase for capital hex letters, or Base64 output to show the digest in Base64 instead of hex.
- For a keyed hash, tick HMAC with secret key and enter the key. The result is then labelled HMAC-SHA-256 (or whichever algorithm you chose).
- To verify a download or a value from documentation, paste the expected hash into Compare with a known hash. The tool says Match or No match.
- Use Copy to put the digest on your clipboard.
Features
- Nine algorithms: MD5, SHA-1, SHA-224, SHA-256, SHA-384, SHA-512, SHA3-256, SHA3-512 and CRC32.
- Hashes text as UTF-8, so accented letters, other scripts and emoji hash the same way as on a server or in a command-line tool.
- Hashes a file you choose from your device. The file is read in your browser and never uploaded.
- HMAC with a secret key for every algorithm except CRC32, following RFC 2104.
- Hex output in lowercase or uppercase, or Base64 output.
- Compare with a known hash. Case, spaces and a leading 0x are ignored, and the expected value can be hex or Base64.
- SHA-1, SHA-256, SHA-384 and SHA-512 use the Web Crypto API in your browser, which is fast and well tested.
- A warning appears when you pick MD5, SHA-1 or CRC32, because they are not safe for security purposes.
- One-click copy of the result.
Worked examples
SHA-384 of "abc" gives cb00753f45a35e8bb5a03d699ac65007272c32ab0eded1631a8b605a43ff5bed8086072ba1e7cc2358baeca134c825a7
The FIPS 180 test vector.
SHA-384 of an empty input gives 38b060a751ac96384cd9327eb1b1e36a21fdb71114be07434c0cc7bf63f6e1da274edebfe76f65fbd51ad2f14898b95b
Privacy: how it works
- The text, the file and the HMAC key stay in your browser tab. Nothing is sent to Ulkaa or to any other server, which you can confirm in the Network tab of your browser developer tools.
- Because the work happens on your own device, large files are limited by your browser memory rather than by an upload limit.
Tips
- To verify a download, choose File, pick the downloaded file, and paste the publisher hash into the compare box. A match means the bytes are identical to what the publisher hashed.
- Hash the same text twice with a trailing space added once. Seeing two unrelated digests is the quickest way to understand the avalanche effect.
- A hash you found on the same page as the download only protects against corruption. It cannot protect you if the page itself was altered.
- HMAC takes the key as plain text. If your key is hex or Base64, decode it first, or the result will not match another system.
Frequently asked questions
Is it really free?
Yes. There is no price, no trial and no credit card. Ulkaa Tool does the work with your own device, so there is no server bill to pass on to you.
Do I need an account?
No. There is no sign-up and no login. Open the page and use it. An Ulkaa account is not needed for anything on this tool.
Does it run in my browser?
Yes. Your text and files are processed by code running in your browser tab, on your own device.
Is my data uploaded?
No. Your text and files are never sent to Ulkaa or to anyone else. You can check this yourself by watching the Network tab in your browser developer tools while you use the tool.
How do I make a Subresource Integrity hash?
Hash the exact file with SHA-384, tick Base64 output, and write the result in the integrity attribute as sha384- followed by the value. Choose File as the input so the bytes are the ones the browser will download.
Is SHA-384 better than SHA-256?
It has a larger output and a higher security margin, at a similar cost on 64-bit processors. For most uses SHA-256 is already enough. Use SHA-384 when a standard or a policy asks for it.
More Hash Generator pages
- Hash GeneratorHash text or a file with MD5, SHA-1, SHA-2, SHA-3 or CRC32, add an HMAC key, and check the result against a known hash.
- MD5 Hash GeneratorGet the 128-bit MD5 hash of text or a file as 32 hexadecimal characters.
- SHA-1 Hash GeneratorGet the 160-bit SHA-1 hash of text or a file as 40 hexadecimal characters.
- SHA-224 Hash GeneratorGet the 224-bit SHA-224 hash of text or a file as 56 hexadecimal characters.
- SHA-256 Hash GeneratorGet the 256-bit SHA-256 hash of text or a file as 64 hexadecimal characters.
- SHA-512 Hash GeneratorGet the 512-bit SHA-512 hash of text or a file as 128 hexadecimal characters.
- SHA3-256 Hash GeneratorGet the 256-bit SHA3-256 hash of text or a file as 64 hexadecimal characters.
- SHA3-512 Hash GeneratorGet the 512-bit SHA3-512 hash of text or a file as 128 hexadecimal characters.
- CRC32 Checksum CalculatorCalculate the 32-bit CRC32 checksum of text or a file as 8 hexadecimal characters.
- HMAC-SHA256 GeneratorSign a message with a secret key using HMAC-SHA256 and read the result as hex or Base64.
- File Checksum CalculatorHash a file on your device and compare it with the checksum the publisher gave you.