File Integrity
Downloads can be truncated, mirrors can be tampered with and backups can silently rot. File integrity tools compute checksums of local files so you can compare them with the value published by a vendor, or check two files against each other, without uploading anything.
File Checksum
Calculate MD5, SHA-2, SHA-3, BLAKE3 and CRC32 checksums of files and verify them against an expected value.
100 MB, 1 file → unlimited on Ultra
File Compare
Check whether two files are byte-for-byte identical using SHA-256.
Free account · 500 MB → unlimited on Ultra
Which tool to choose
- File Checksum
- You have a file and an expected value, or need checksums for a list of files.
- File Compare
- You have two files and only need to know whether they are identical.
What these tools solve
- Verify an installer, ISO image or firmware against the checksum on the vendor’s website.
- Produce a sha256sum-style list for several files at once.
- Confirm that two copies of a file are byte-for-byte identical.
When they are useful
- Before installing software downloaded from a mirror.
- After copying data to a backup drive or between servers.
- When two files have the same name and size and you need to know whether they really match.
How it works
Files are read in chunks with the File API and fed to incremental hash functions in WebAssembly, so a file does not have to fit in memory and progress is shown while it is processed. Expected values are normalised (case, spaces, colons and a 0x prefix are ignored) before comparison.
Limits and good practice
- Largest file per plan: 100 MB without an account, 500 MB on Free, 2 GB on Basic, 5 GB on Standard, 10 GB on Plus, unlimited on Ultra.
- Files at once in File Checksum: 1 without an account, up to 50 on Plus and unlimited on Ultra.
- A matching checksum proves the file equals the published one; it does not prove the publisher is trustworthy. Prefer checksums served over HTTPS or signed by the vendor.
- Very large files are limited by the speed of your disk and browser rather than by the tool.
Questions about integrity
Help centerWhy are MD5, SHA-1 and CRC32 marked as weak?
Practical collision attacks exist for MD5 and SHA-1, and CRC32 is an error-detecting code, not a cryptographic hash. They are still useful to match legacy checksums, but must not be relied on to resist deliberate tampering.
How do I verify a downloaded file?
Open File Checksum, choose the algorithm the vendor publishes (usually SHA-256), drop the file and paste the published value into Expected checksum. A green “Matches” badge means your file is identical to the one the vendor hashed.
Does the expected checksum have to be in a particular format?
No. Upper or lower case, spaces, colons and a 0x prefix are ignored when comparing. Paste the value exactly as the vendor shows it.
How large can a file be?
It depends on your plan: 100 MB without an account, 500 MB on Free, 2 GB on Basic, 5 GB on Standard, 10 GB on Plus and unlimited on Ultra. Files are read in chunks, so they do not need to fit in memory.
Can I hash several files at once?
Yes. File Checksum accepts several files and lists a checksum for each, plus a sha256sum-style list you can copy. The number of files at once is 3 on Free, 25 on Standard and unlimited on Ultra.
When should I use File Compare instead of File Checksum?
Use File Compare when you have two files and only want to know whether they are identical. Use File Checksum when you compare one file with a published value, or need checksums to keep.