File Hash Verifier
Check a file against a published checksum.
Use the File Hash Verifier tool
What this file hash verifier does
A checksum is a short fingerprint of a file. If a publisher lists a SHA-256 value next to a download, computing the hash of your copy and comparing it confirms the bytes arrived unchanged.
This verifier reads the file directly into memory with the browser File API and hashes it with Web Crypto. Nothing is uploaded, and the file is discarded when you close the tab.
Why use it
- Confirm an installer, archive or database dump was not truncated or altered.
- Detect a partial or corrupted download before you run it.
- Check a release against a vendor-published digest without installing extra software.
How to use it
- 1Choose the file you downloaded.
- 2Pick the algorithm the publisher used, or let the tool guess it from the expected value length.
- 3Paste the published checksum and compare the match verdict.
Worked examples
SHA-256 installer
Input
installer.zip · expected a1b2c3… (64 hex characters)
Output
Length implies SHA-256; the computed digest either matches every character or it does not.
MD5 from an old vendor page
Input
expected value of 32 hex characters
Output
Algorithm switches to MD5 automatically, with a note that MD5 only detects corruption, not tampering.
Common mistakes
- Comparing hashes by eye and missing one changed character — always paste the expected value.
- Treating an MD5 match as proof of authenticity; MD5 and SHA-1 are broken for security purposes.
- Hashing the wrong file, such as the HTML download page instead of the archive itself.
Frequently asked questions
Is my file uploaded anywhere?
No. Hashing uses the Web Crypto API in your browser. The file is read locally and never sent to a server.
Why does the hash not match when the file opens fine?
A file can open while one byte differs, for example after an interrupted download or a vendor re-release. Compare sizes and download again from the official source.
What is the largest file supported?
Files up to 100 MB are accepted so the browser stays responsive. Larger files need a command-line tool such as sha256sum.
Should I use MD5 or SHA-256?
Use SHA-256 unless a publisher only provides MD5. MD5 is fine for spotting accidental corruption but not for verifying against deliberate modification.
Related tools
All toolsHash Generator
MD5 and SHA digests for text or files, computed locally.
Runs locally
Password Strength Checker
Estimate password strength without sending it anywhere.
Runs locallyNew
Secure Token Generator
Cryptographically random API keys and secrets.
Runs locallyNew
JSON Formatter
Beautify or minify JSON, with precise error positions.
Runs locally