Generate hashes for text and files
Hash text or a file, then compare it with a supplied checksum. Choose the same algorithm; a match alone does not prove the publisher is trustworthy.
Generate and compare hashes
Enter text or choose a file; this tool computes the digests in your browser.
Drop a file here or choose from your device
Any file type, up to 200 MBHash algorithms
Use the same algorithm as the checksum you are comparing.
Hash results 0
Compare a checksum
Paste a checksum from a source you trust to compare it with the data you just hashed.
Generate and compare hashes in 3 steps
Enter text or choose a file
Text is encoded as UTF-8. Files use their original bytes and must be at most 200 MB; large files need enough browser memory.
Match the reference checksum’s algorithm
You can calculate several digests at once. Use MD5 and SHA-1 only for legacy comparison; SHA-256, SHA-384 and SHA-512 are SHA-2 algorithms.
Paste a checksum from a trusted source
After a digest appears, select Compare. Hex letter case does not affect the result. If it differs, check the file and algorithm before using it.
Choose an algorithm for comparison
If the file publisher provides a checksum, use the algorithm they specify. Hex length can suggest an algorithm but cannot establish where the checksum came from.
| Algorithm | Hex length | Use |
|---|---|---|
| MD5 / SHA-1 | 32 / 40 | Compare legacy checksums; avoid in new security designs. |
| SHA-256 | 64 | Compare a SHA-256 checksum published by a trusted source. |
| SHA-384 / SHA-512 | 96 / 128 | Use when the reference checksum specifies this algorithm. |
If a checksum does not match
- Different algorithm
- Match the algorithm named by the source. Compare only checks the digests you have generated.
- Different file or text bytes
- Get the exact file again. For text, spaces, line breaks and UTF-8 bytes all affect the digest.
- File too large or browser memory error
- The file limit is 200 MB. The tool reads the whole file into memory before hashing, so low-memory devices can fail below this limit.
What a hash can and cannot show
A digest is a comparison value, not encryption or a digital signature. A match means your data has the same digest as the pasted checksum; if both file and checksum come from a compromised source, this comparison cannot detect it. Tool code reads input and hashes it in your browser without uploading the file. Do not use MD5, SHA-1 or a plain fast hash for password storage; see OWASP password storage guidance. OWASP.
Comments & feedback
Loading ratings…
Write a commentNo account needed