Check that a download is complete and has not been changed
Software sites, Linux downloads, firmware updates and backup tools often publish a checksum next to the download link: a long string of letters and numbers such as a SHA-256 value. It is a fingerprint of the file. If the file you have gives exactly the same fingerprint, it is identical to the one the publisher released, byte for byte. If even one byte is different, because the download was cut short, corrupted on a disk, or swapped for something else, the fingerprint is completely different.
This tool works out SHA-256, SHA-1, SHA-512, SHA-384, MD5 and CRC32 checksums for any file and compares them with the value you paste. The file is read by your browser on your own device and never uploaded, so it works for large and private files too.
How to use it
- Choose the file or drop it on the box. You can check several files at once.
- Paste the expected checksum from the download page, if you have one. Capitals, spaces and a file name after the value do not matter.
- Read the result. A green "Matches" means the file is exactly right. A red "Does not match" means the file is different from the one published: download it again, and if it still does not match, do not open it.
Which checksum should I use?
- SHA-256 is the standard today and the one to trust for security. Most publishers use it.
- SHA-512 and SHA-384 are longer members of the same family, used by some projects.
- SHA-1 and MD5 are older. They still catch accidental damage, but they are no longer safe against deliberate tampering, because people can make two different files with the same value. Use them only when they are all that is published.
- CRC32 is a quick check used inside zip files and by some backup tools. It only detects accidental damage.
Good to know
- Get the checksum from the official site, ideally from a page served over https. A checksum published next to a tampered download on the same compromised server proves nothing.
- Large files are read into memory, so files of several gigabytes depend on your device's memory. A progress bar shows while each file is read.
- On the command line, the same values come from
certutil -hashfile file SHA256on Windows,shasum -a 256 fileon a Mac andsha256sum fileon Linux.
How this tool was tested
Before publishing, I ran 24 automated checks on the finished page in Microsoft Edge, which is built on Chromium like Chrome. Last full run: 15 November 2026.
- Published test values: the MD5 values from RFC 1321, including one million letter a's; SHA-256 and SHA-1 of "abc" from FIPS 180; the start of SHA-512 and SHA-384 of "abc"; and the standard CRC-32 check value of "123456789".
- Large and odd-sized files: 60 random files fed in random-sized pieces gave the same MD5 as all at once, and a 20 MB file read in 8 MB slices gave the same SHA-256 as Web Crypto in one go. Empty files work.
- Pasted checksums: plain, in capitals, followed by a file name, in the "SHA256 (file) = ..." style and as spaced pairs are all understood; text that is not a checksum is ignored.
- Using the tool: a matching checksum is marked green, one wrong character marks it red, pasting a SHA-1 turns SHA-1 on and matches it, several files at once, capitals and Copy.
What the tests did not cover: Safari and Firefox were not tested. Files of several gigabytes were not tested and depend on your device's memory. Something not working? Tell me on the contact page.
FAQ
Is a checksum the same as a hash?
Yes, in everyday use. A hash function turns a file into a fixed-length value; the value is called a hash, digest or checksum.
Can two files have the same SHA-256?
In theory, yes; in practice nobody has ever found two. A match means the files are the same.
Why are my results in small letters when the website shows capitals?
It is the same value; hexadecimal is not case-sensitive. Tick "Show in capital letters" if you prefer.