File Checksum Checker
Check that a downloaded file is intact by comparing its hash with the checksum the publisher lists, all in your browser.
Verify a File Checksum Online
Projects that distribute installers, disk images or archives usually publish a checksum next to each download. Hashing the file you received and comparing it with that value proves the two are byte-for-byte identical: nothing was truncated, corrupted in transit or swapped along the way.
This page opens the Hash Generator on its File tab. The file is read and hashed inside your browser, never uploaded.
Recognising a checksum by its length
| Hex characters | Algorithm | Typical file names |
|---|---|---|
| 32 | MD5 | MD5SUMS, .md5 |
| 40 | SHA-1 | SHA1SUMS, .sha1 |
| 64 | SHA-256 | SHA256SUMS, .sha256 |
| 96 | SHA-384 | .sha384 |
| 128 | SHA-512 | SHA512SUMS, .sha512 |
What a checksum does and does not prove
A match proves the file equals the one that was hashed. It does not by itself prove who made it: if an attacker controls the download page, they can replace both file and checksum. That is why security-sensitive projects also sign their checksum files with GPG or publish them on a separate channel. For everyday downloads, matching a SHA-256 checksum from the official site is a strong and practical check.
Checking on the command line
- Linux:
sha256sum -c SHA256SUMSchecks every file listed. - macOS:
shasum -a 256 file.dmgand compare by eye. - Windows PowerShell:
(Get-FileHash file.exe).Hash -eq 'EXPECTED'returns True or False. - Windows cmd:
certutil -hashfile file.exe SHA256.
Tips
- Copy the checksum rather than retyping it; one wrong character means no match.
- Upper and lower case do not matter in hex; the comparison ignores case.
- The browser limit here is 50 MB per file. For larger images, use the commands above.
Need a hash of text rather than a file? Use SHA-256, SHA-512 or MD5.