Generate file hashes online
Get a file's checksum — MD5, SHA-1, SHA-256, and SHA-512, all four at once — the usual reason being to confirm a download is genuine and untampered, against a hash the publisher already quoted. Add your file, optionally paste the hash you were given, and download the report.
A hash is a short fingerprint of a file's exact bytes: change even one bit anywhere in the file and every algorithm's output changes completely. Two files with the same hash are, for any practical purpose, the same file.
Your file never leaves your device. Every hash is computed entirely in your browser, so nothing is uploaded, stored, or scanned — which matters here more than most tools, since a file worth checking a hash on is often one you have not fully trusted yet.
or drop them here — nothing is uploaded
How to hash generator
Add your file
Drop one or more files into the box, or click to browse. Any file type works — this does not read or care about the contents.
Paste a hash to check against, if you have one
Optional. If a download page quoted a hash, paste it in and the report will say whether your file matches — the algorithm is detected automatically from the hash's length.
Generate and download
Press Hash Generator. A small text report downloads for each file with all four hashes, and the match result if you provided one.
Frequently asked questions
Is my file uploaded anywhere?
No. Every hash is computed in your browser using JavaScript, so your file stays on your device. You can confirm this by opening your browser devtools Network tab while working — there are no upload requests. This is exactly the case where that guarantee matters most, since you may be checking a file precisely because you do not yet trust it.
Which algorithm should I use?
Whichever one the publisher quoted — that's the whole point of a checksum, matching what someone else already computed. If you're generating a hash for your own use with no existing constraint, SHA-256 is the current standard default: fast, well-supported, and with no known practical collision attack. MD5 and SHA-1 are both cryptographically broken and still included only because plenty of legacy tooling and older download pages still quote them.
How does the automatic match detection work?
By length. MD5 hashes are 32 hex characters, SHA-1 is 40, SHA-256 is 64, and SHA-512 is 128 — those lengths don't overlap, so whatever you paste is compared against the one algorithm it could actually belong to. The comparison ignores case and surrounding whitespace, since hashes are sometimes quoted in capitals.
A file's hash doesn't match what I was given. What does that mean?
The file differs from the one the hash was generated for — even by a single byte. That can mean a corrupted or incomplete download, a file that was modified after the hash was published, or a hash copied incorrectly. It does not, on its own, prove anything malicious; re-download the file and check again before assuming the worst.
Is there a limit on how many files?
Twenty at a time, which is a limit of your device rather than our policy — everything is held in memory while it works.
Can this hash text I paste in, not a file?
Not directly — save the text as a file first (a .txt file works fine) and add that. Hashing is defined over bytes, and a file is the most unambiguous way to hand this tool exactly the bytes you mean, with no risk of an editor silently changing line endings or encoding underneath you.