Compute SHA-1, SHA-256, SHA-384 or SHA-512 digests of any text with the browser’s native crypto. Nothing is uploaded.
How the hash generator works
It computes a cryptographic digest of your text using the browser’s native Web Crypto API. SHA-256 is the modern default; SHA-1, SHA-384 and SHA-512 are also offered. The text never leaves the page.
Frequently asked questions
What is a hash used for?
Verifying integrity. The same input always produces the same digest, so you can confirm a file or message has not changed.
Why no MD5?
MD5 is broken for security and is not exposed by the browser crypto API. SHA-256 is the recommended replacement.
Is my text uploaded?
No. Hashing runs locally in the page.
How to use it
- Type or paste the text you need to hash into the input field. The field accepts any length of text, including whitespace and special characters.
- Select an algorithm from the dropdown menu: SHA-1, SHA-256, SHA-384, or SHA-512.
- The hash appears below once the browser finishes computing it. SHA-256 produces a 64-character hexadecimal string; SHA-512 produces 128 characters; SHA-384 produces 96 characters; SHA-1 produces 40 characters.
- Copy the resulting digest or compare it side by side with a reference value to verify that the input has not changed.
Where it comes in handy
After downloading a 4.2 GB installer from a mirror site, paste its filename and size into the tool along with the SHA-256 checksum the vendor published. If the computed 64-character digest matches, the download completed without corruption.
When exchanging a short verification message like VERIFY:a1b2c3 through a chat app or email, hash both copies and compare the outputs. A mismatch means one copy was altered in transit.
In a code review where a 200-line Python script reads a fixed configuration string, paste the exact string and the expected SHA-256 value to confirm that invisible Unicode differences or copy-paste errors are not causing the script to reject the file.
Worth knowing
- SHA-1 is deprecated for security use. The 40-character output can be generated faster than SHA-256, but collision attacks against SHA-1 are practical. Use SHA-256 unless a legacy system explicitly requires SHA-1.
- Unicode normalization is not applied automatically. The characters “é” can be encoded as a single precomposed code point or as “e” plus a combining acute accent. These two forms produce different digests even though they look identical on screen.
- MD5 is not available. The browser Web Crypto API does not expose MD5, and no option exists to compute it. The tool cannot generate MD5 digests under any circumstance.