Checksum / Hash Verifier
Compare an expected hash (published by a source) and a computed hash (obtained on your end) to verify that a downloaded file is intact and unaltered.
How it works
After downloading a file (installer, ISO image, source code archive), reputable sites often publish its cryptographic fingerprint (for example a SHA-256) next to the download link, so you can verify that the received file wasn't corrupted during transfer or altered by a third party. First compute the hash of the downloaded file (using this site's "Hash Generator" tool), paste it here next to the hash published by the source site, then compare the two: the tool normalizes case and spaces before comparing, to avoid false negatives from a simple case difference.
The published hash and my computed hash are different, what should I do?
Don't trust the downloaded file. A mismatch means either that the download got corrupted (re-download it), or — more rarely but more seriously — that the file was altered between the original server and you (compromised mirror, man-in-the-middle attack). In this second case, don't run it and re-download from the official source, if possible over a different connection.
Does this tool compute the hash of the file itself?
No, it only compares two text strings you've already obtained elsewhere. To compute the hash of a file or text, use this site's "Hash Generator" tool (SHA-256, SHA-1, MD5, etc.), then copy the result here to compare it against the one published by the source.
Privacy: the comparison happens entirely in your browser via WebAssembly — your hashes are never sent to a server.