Why check a file checksum
A checksum, or file hash, is a short string calculated from every byte of a file. Change a single byte and the checksum changes completely. When a publisher lists the SHA-256 of an installer, a firmware update or a disk image next to the download link, you can calculate the hash of the file you received and compare: if both match, the download is complete and has not been altered on the way. For the hash of a plain text, use the SHA256 generator instead.
This tool calculates checksums for one or many files at once, with no size limit for SHA-256, MD5 and CRC32. Files are read in chunks inside your browser, with a progress bar, so a 4 GB disk image works as well as a small PDF. Your files stay on your device and nothing is uploaded.
How to use it
- Click “Choose files” or drop the files onto the tool.
- Under “Algorithms”, tick SHA-256, SHA-1, SHA-384, SHA-512, MD5 or CRC32. Your choice is remembered for next time.
- Paste the published hash into “Expected checksum”. Upper case and spaces are ignored, and the algorithm is recognised from the length: 64 characters means SHA-256, 32 means MD5. A green “Match” or a red “Different” tells you the answer at a glance.
- To verify a batch, load the checksum file shipped with the downloads (
.sha256,.md5and similar) with “Open a checksum file”, or drop it together with the files. Every line in thechecksum file_nameformat is checked. - “Copy all results” gives you lines in the same format, ready to save as your own checksum file.
Known values to test with
| File | Algorithm | Checksum |
|---|---|---|
| 3 bytes “abc” | SHA-256 | ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad |
| 3 bytes “abc” | SHA-1 | a9993e364706816aba3e25717850c26c9cd0d89d |
| 3 bytes “abc” | CRC32 | 352441c2 |
| empty file | MD5 | d41d8cd98f00b204e9800998ecf8427e |
If you save “abc” in a text editor that adds a line break at the end, the file is 4 bytes long and every checksum changes. That trailing newline is the most common reason for an unexpected “Different”. To hash the bare text without that newline, the MD5 encrypt page does it directly.
Which algorithm should you use?
- SHA-256 (64 characters) is the hash most publishers list today. Use it whenever it is offered.
- SHA-384 and SHA-512 (96 and 128 characters) are longer variants found on some open source projects and signed documents.
- SHA-1 (40 characters) and MD5 (32 characters) still catch a broken download, but two different files with the same hash can now be crafted on purpose: they no longer protect against tampering.
- CRC32 (8 characters) is a simple error-detecting code used inside ZIP archives. It spots a damaged file and nothing more.
SHA-1, SHA-384 and SHA-512 are computed in one block in memory, so they are limited to files of 1 GB or less. For a 6 GB image, compare its SHA-256. For a short text, the SHA1 encrypt page gives the same SHA-1 hash without any file.
FAQ
Is my file uploaded anywhere?
No. It is read and hashed in your browser. The page sends no request during the calculation and keeps working offline once loaded.
How long does a large file take?
One or two seconds per 100 MB on a recent computer, longer on a phone. The page stays responsive while the file is read, and “Stop” cancels the calculation at any time.
The checksums don't match. What now?
First make sure you are comparing the same algorithm and the same version of the file. If they are, delete the file and download it again: an interrupted or corrupted download gives a different hash.
Does a matching hash mean the file is safe?
It proves you have the exact file the hash describes. If the hash sits on the same server as the file, an attacker who swapped one could swap the other, so take the hash from the publisher's official page over https.