Hashes/Crypto
Checksum Verifier
Verify the integrity of a file or text — paste the expected hash and the tool will detect the algorithm among 13 supported ones.
Computed hashes
Sites publish a checksum next to a download so users can confirm the file arrived intact and hasn't been tampered with. This tool hashes your file and compares it against the expected value, detecting the algorithm automatically.
How to use it
- Pick a file or paste text, then paste the expected hash published by the source.
- The tool auto-detects the algorithm from the hash's length among the 13 it supports (MD5, SHA-1, SHA-256, and others) and shows whether the result matches.
- If the algorithm is known ahead of time, you can select it manually for a more precise check.
Common uses
- Verifying an ISO image or installer after downloading it, before burning it to media.
- Confirming an archive of important data survived a network transfer intact.
- Cross-checking a package manager's checksum against the one the developer published.
Things to keep in mind
A checksum check protects against accidental corruption and confirms file integrity, but it doesn't guarantee the original itself wasn't compromised at the source — that requires a digital signature.
If the checksum doesn't match, re-download the file first: the most common cause is corruption in transit, not tampering.
Article about this tool: Checksum Verifier: how to check that a file isn't corrupted
Frequently asked questions
What's the point of comparing checksums instead of just trusting a download?
A checksum lets you confirm a file wasn't corrupted during transfer or tampered with, by comparing the hash you compute locally against the one published by the source — if they don't match, the file is different from what was published.
Which algorithm should I use to verify a checksum?
Use whichever algorithm the source published the checksum in — usually SHA-256 today, though older SHA-1 or MD5 checksums are still common for legacy files. The algorithm must match exactly, since a hash from one algorithm can't be compared to another.
Does verifying my file upload it anywhere?
No. The file is read and hashed entirely in your browser — it's never uploaded to a server.
Why is CRC32 sometimes used for checksums instead of SHA-256?
CRC32 is much faster, but it's trivially easy to forge on purpose — fine for detecting accidental corruption during transfer (archivers, network protocols), but unsuitable as protection against an attacker who wants to tamper with a file undetected.
What should I do if the checksum doesn't match?
First, re-download the file — the most common cause of a mismatch is corruption during transfer. If it still doesn't match after re-downloading, don't use the file: the source may have updated it without updating the published checksum, or the file may have been tampered with.