File Integrity Checker
Compute SHA-256 or SHA-1 checksums for your files and verify them against a trusted hash list to confirm nothing was corrupted or tampered with.
Files to Verify
Expected Checksums (optional)
Accepts standard sha256sum / sha1sum output format ("hash filename"), or one bare hash to check every file against it.
How to use File Integrity Checker
- Add the files to check. Optionally paste expected hashes as standard
sha256sumorsha1sumlines, or paste one bare hash to compare against every selected file. - Choose SHA-256 or SHA-1 to match the algorithm used for the expected checksum, then select Compute & Verify.
- Review each computed hash and its status: Verified, Mismatch, or No expected hash. A hash calculated without a trusted reference is only a fingerprint, not proof that a file is authentic.
How checksum verification works
A cryptographic hash function turns a file's contents into a fixed-length fingerprint. Even a single changed bit produces a completely different hash, so comparing the hash of a file you have against a known-good hash tells you, with near certainty, whether the file is identical to the original.
Verify downloads, backups, and transferred files
Select files and, when you have one, paste the expected SHA-256 or SHA-1 checksum. The checker computes a hash for each file and compares it with the supplied digest, including standard checksum-list lines that pair a hash with a filename. A match indicates the bytes agree with that expected value; a mismatch means the file differs or the supplied checksum does not correspond to it.
For a meaningful verification, obtain the expected checksum from a source you already trust, such as the software publisher's official download page. Computing a hash without a trusted reference gives you a fingerprint, but by itself does not prove who created the file or whether it is safe. SHA-256 is generally preferred for new checks; SHA-1 is included for compatibility with older checksum lists.
SHA-256 vs SHA-1 — which should I use?
Use whichever algorithm the checksum you were given uses. SHA-256 is stronger and more common today; SHA-1 is still widely published for legacy downloads but is fine for integrity checks (just not for security-critical signatures).
Can I check a file without an expected checksum?
Yes. The tool will calculate and display its SHA-256 or SHA-1 hash, but without a trusted expected value there is nothing to compare it against.
What does a checksum mismatch mean?
The file's computed digest does not match the expected digest provided. Confirm that you chose the correct algorithm and checksum, then download or copy the file again from its trusted source if needed.