file checksum verifier
Drop in a file and get its digests, then paste the expected value for a straight match or no-match verdict. The file is read locally and never uploaded, so this works on anything, including files you could not send to a third party.
Runs in your browser — nothing is uploadedWhy verify a download
A checksum published by the source and computed by you proves the bytes arrived intact and were not altered in between. It catches truncated downloads, corrupted mirrors and interception. It only means something if the digest came from a channel you trust more than the download itself.
Which digest to compare
Use SHA-256 when the publisher offers it. MD5 and CRC32 are still widely published and are fine for catching accidental corruption, but neither resists deliberate tampering: a matching MD5 does not prove a file was not modified on purpose.
Verifying files from this site
Every file in the corpus publishes its SHA-256 on its own page, and the whole set is listed in one SHA256SUMS file. Drop any download in here and compare. Each test pack also contains its own SHA256SUMS for the files inside it.
Questions
Is my file uploaded?
No. It is read with the browser's File API and hashed in the page. It never goes to a server, which is why this works for files you are not allowed to share.
Which checksum should I compare?
SHA-256 where it is offered. MD5 and CRC32 detect accidental corruption but not deliberate modification.
Why do I get a different hash than the website shows?
Usually the download was truncated, or a proxy altered it, or you are hashing a decompressed copy rather than the file as served. Check the byte count first.
Can it handle large files?
It reads the file in chunks, so size is bounded by your browser's memory rather than an upload limit.