Hash File Verifier
Check a download against its published checksum. Paste a hash, sha256sum line or SRI value; the algorithm is detected and the file is hashed locally.
The interactive tool loads here when JavaScript runs.
About this toolWhat is Hash File Verifier?
The Hash File Verifier checks that a file matches the checksum published for it. Choose the file, paste the expected value from the download page and click Verify File. The tool hashes the file in your browser and compares the result with the expected value, ignoring case, surrounding spaces and colon separators.
It accepts the formats checksum files actually use: a bare hex digest, a sha256sum or md5sum line ("hash filename" or "hash *filename"), BSD or openssl output ("SHA256 (file.iso) = hash"), colon-separated hex, and Subresource Integrity values such as sha384-<base64> from npm or a script tag. With Algorithm on auto-detect it picks MD5, SHA-1, SHA-256, SHA-384 or SHA-512 from the length of the hash or the SRI prefix.
The file is read into memory and never uploaded. SHA hashes use the Web Crypto API and MD5 uses an established JavaScript implementation; both give the same output as sha256sum, shasum, certutil and Get-FileHash.
- MD5, SHA-1, SHA-256, SHA-384 and SHA-512
- Auto-detects the algorithm from hash length or SRI prefix
- Accepts sha256sum, BSD, colon-hex and SRI formats
- Case- and whitespace-insensitive comparison
- Files are hashed locally and never uploaded
Updated
How to use Hash File Verifier
- Click Select File and choose the downloaded file.
- Paste the expected value into Expected Hash: a hex digest, a line from a SHA256SUMS file, BSD-style output or an SRI value.
- Leave Algorithm on Auto-detect, or choose one if the publisher's value is ambiguous.
- Click Verify File. Verification Results shows the calculated hash, the algorithm used and a pass or fail banner.
Worked examples
A sha256sum line pasted as-is
Input
efc9197ad2d06ab99b50a13539f765a35877c49c396772e936f4e56121e1c8c5 release-notes.txt
Output
SHA-256, Hash Verification Passed
For a file containing exactly "Release 4.2.0 approved for production." with no trailing newline. The filename after the two spaces is ignored and 64 hex characters select SHA-256.
MD5 in uppercase
Input
5425028AF4415088EB2B76DF468033E7
Output
MD5, Hash Verification Passed
Hex digests are case-insensitive, and 32 characters means MD5. Changing one character of the expected value turns the result into a failure.
Background and insight
A checksum proves the bytes you have are the bytes the publisher hashed. That catches truncated downloads, bad mirrors and disk corruption. It does not prove who published the file: if an attacker can replace the download, they can usually replace the checksum on the same page too. For that you need a digital signature, which is what GPG signatures, Sigstore and code-signing certificates provide.
Hash length identifies the algorithm: 32 hex characters is MD5, 40 is SHA-1, 64 is SHA-256, 96 is SHA-384 and 128 is SHA-512. MD5 and SHA-1 are broken for collision resistance (SHA-1 publicly since the 2017 SHAttered collision), so an attacker who controls both files can make two with the same hash. They still catch accidental corruption, but prefer SHA-256 when the publisher offers it.
Earlier versions of this tool only computed SHA-256 and compared the raw input, so pasting a line straight from a SHA256SUMS file, or a hash with a trailing space, reported a mismatch on a perfectly good file. The parser now strips filenames and separators before comparing.
Common use cases
Verifying OS images and installers
Check a Linux ISO, firmware image or installer against the SHA256SUMS file before flashing or running it.
Confirming a transfer
Make sure a large file copied over a flaky network or USB stick arrived intact.
Checking package integrity
Compare a downloaded tarball with the sha512 integrity value in a package-lock.json.
Support and QA
Confirm a customer or tester has exactly the build you shipped.
Tips and limitations
- Get the checksum from a different channel than the file if you can (the project's HTTPS site rather than a mirror), or verify the publisher's signature on the checksum file.
- The whole file is loaded into memory, so files of several gigabytes may fail in some browsers. Use sha256sum or Get-FileHash for very large images.
- If verification fails, re-download before assuming tampering. Interrupted downloads are far more common than attacks.
- A 40-character value could be SHA-1 or RIPEMD-160; auto-detect assumes SHA-1, which is what publishers use in practice.
- To hash text rather than a file, use the Hash Generator.
Sources and further reading
- FIPS 180-4: Secure Hash Standard (SHS), NIST. The SHA-1 and SHA-2 family
- Announcing the first SHA1 collision, Google Security Blog. The 2017 SHAttered result
- sha2 utilities (sha256sum and related), GNU Coreutils. The checksum file format the parser accepts
- Sigstore overview, Sigstore. Signing releases so the publisher can be verified, not just the bytes
Frequently asked questions
How do I verify the SHA-256 checksum of a downloaded file?
Select the file, paste the SHA-256 value from the download page and click Verify File. The tool hashes the file locally and compares it with your value. On the command line the equivalents are sha256sum file on Linux, shasum -a 256 file on macOS and Get-FileHash file on Windows.
Why does the checksum not match even though the file seems fine?
The usual causes are a partial or interrupted download, comparing against the checksum for a different version or architecture, or using the wrong algorithm. Re-download the file, check the filename next to the published hash, and make sure the hash length matches the algorithm.
Does a matching checksum prove the file is safe?
It proves the file is identical to the one the checksum was made from. If the checksum came from the same server as a tampered file, it proves nothing about the publisher. A signature from a key you trust is what proves authenticity.
Is it safe to check MD5 checksums?
For catching accidental corruption, yes. MD5 is broken against deliberate collisions, so it cannot protect against an attacker who controls the file. If the publisher offers SHA-256 as well, verify that instead.
Can I paste a line from a SHA256SUMS file directly?
Yes. Lines in the "hash filename" or "hash *filename" form, BSD lines such as SHA256 (file) = hash, colon-separated hex and sha384- SRI values are all recognised. The filename part is ignored, so make sure you copied the line for the right file.
Is my file uploaded when I verify it?
No. The browser reads the file and hashes it in the page with the Web Crypto API (or a local MD5 implementation). Nothing is sent over the network, which also means very large files are limited by your browser's memory.
Is there an in-depth guide to Hash File Verifier?
Yes. “Checksums vs Digital Signatures: How to Verify What You Download” covers the background, how it works, common pitfalls and worked examples. Read the full guide.
Related Tools You May Like
Free, in-browser tools that pair well with this one.