Using File Hash Verifier
I built this for the moment every careful downloader knows: the publisher posts a SHA-256 checksum next to the installer, and you're supposed to check it. Paste your file here and I'll compute its fingerprint right in your browser — then paste the expected hash and I'll tell you instantly whether they match.
How to use it
- 1
Choose your file
Pick any file from your device — an installer, an ISO, a ZIP, a document. I read its bytes locally; nothing is uploaded anywhere.
- 2
Pick the algorithm
Use SHA-256 for most published checksums, or switch to SHA-384 or SHA-512 when the publisher used a stronger digest. Changing the algorithm re-hashes the same file instantly.
- 3
Paste the expected hash and compare
Copy the checksum from the publisher's download page into the expected-hash box. I'll compare the two (ignoring case and stray whitespace) and show a green match or a red mismatch warning.
Why use this privately?
A hash mismatch means the file you received is not the file the publisher signed off on — it could be corrupted in transit, or it could be tampered with, and those two look identical until you check. Most verification tools either upload your file to a server (defeating the point when the file is sensitive) or only work on text. I run the Web Crypto digest on your actual file bytes inside your own tab, so your downloads stay private while you confirm they're genuine. It's the same check security professionals run, minus the command line.
Who is this for?
Built for US users verifying software installers, Linux ISOs, datasets, and sensitive documents before trusting them.