File Checksum Verifier
Calculate MD5, SHA-1, SHA-256, SHA-512 and more for any file, even very large ones, and check it against the published checksum.
Runs in your browser Your input never leaves your device.
Drop files here, or (up to 20).
Files are read in this page, in pieces, and never uploaded. Large files are fine.
Report a problem with this tool
About this tool
A checksum is a short fingerprint of a file's contents: change one bit and the fingerprint changes completely. Download pages for operating-system images, installers and software releases publish the fingerprint so you can check that your copy is complete and has not been altered. Drop a file here and the tool computes its MD5, SHA-1, SHA-224, SHA-256, SHA-384, SHA-512, SHA3-256, BLAKE3 and CRC-32 checksums; the common four are on by default. Paste the checksum from the download page, or the whole contents of a SHA256SUMS file, and the tool tells you whether it matches and which algorithm it matched. The file is read in 8 MB pieces and hashed in your browser with WebAssembly, so even files of several gigabytes work without being loaded into memory at once, and nothing is uploaded. A match proves your copy is identical to the one the checksum was made from; it proves the file is genuine only if you got the checksum from a trustworthy place that is separate from the download itself, and ideally a signed one. MD5, SHA-1 and CRC-32 are fine for spotting a broken download but must not be trusted against deliberate tampering; prefer SHA-256 or stronger. Results are lowercase hex, the same as the sha256sum and md5sum commands print.
How to use it
- Drop one or more files on the page, or choose them.
- Choose the algorithms you need; SHA-256 is the usual one.
- Paste the expected checksum, or the contents of a checksum file, if you have one.
- Read the result: a green tick means the checksum matches.
Common problems
- It says the checksum does not match
- The file is not the one the checksum was made for. Download it again, preferably from the original site, and check that the download finished. Also check that you compared against the right file's checksum and the right algorithm.
- It says the expected value has a length none of the chosen algorithms produces
- Tick the algorithm that matches the length: 32 hex characters is MD5, 40 is SHA-1, 64 is SHA-256 (also SHA3-256 and BLAKE3), 96 is SHA-384 and 128 is SHA-512.
- A matching checksum from the same page as the download is not proof it is safe
- If an attacker can change the file they can change the number next to it. Use a checksum or signature published on a separate, trusted channel, and a stronger algorithm than MD5 or SHA-1.
- Hashing a huge file is slow
- The speed depends on your device and on how many algorithms are ticked. Untick the algorithms you do not need, since each extra one adds work. You can cancel at any time.