Runs locally in your browser. Nothing you enter is uploaded to our servers.
Result will appear here
Tips for file checksums
Compare against the publisher’s published hash, not a random copy.
A matching checksum verifies integrity, not authenticity alone.
Re-download if the hash mismatches — do not “force install”.
Prefer SHA-256 over MD5 when both are offered.
Hash the exact file you will run, after any unzip step.
Checksum a file without uploading it
Processing stays in your browser — your input is not uploaded to our servers.
A checksum tells you whether a download matches the publisher’s digest. The file is hashed in the browser — it is not sent to our servers.
Compare the hex to the value on the official page. Matching checksums do not prove the publisher is honest, only that the bytes match that digest.
Checksum a local file
Choose the file
Use the file you actually downloaded, not a renamed copy you are unsure about.
Compute the digest
Pick the algorithm published next to the download (often SHA-256).
Compare character by character
A single differing nibble means a different file.
File checksum FAQ
Does the file upload?
No. Hashing runs locally in the browser.
SHA-256 vs MD5?
Use whatever the publisher printed. MD5 collisions exist; prefer SHA-256 when you control both sides.
Can I checksum a folder?
This tool hashes one file. Archive the folder first if you need a single digest.