Verify a Download With an Official SHA-256 Checksum
Start with the task you actually need to finish
- Verifying a downloaded Linux distribution ISO against the checksum published on the project's website.
- Confirming a large file transfer between drives completed without corruption.
- Checking that a downloaded software installer matches the vendor's published SHA-256 hash before running it.
A practical check before you begin
Obtain the expected checksum from a trusted publisher, compute the file’s hash, and compare every character. A match supports that the bytes agree with that reference. An untrusted mirror can supply an altered file and its matching hash.
Follow the workflow and review the result
- Select the file you want to check from your device.
- Wait while the browser computes MD5, SHA-1 and SHA-256 hashes locally.
- Copy the computed hash for the algorithm the publisher provided.
- Paste or view the publisher's published checksum alongside it.
- Compare the two values character by character, or use the built-in match indicator if available.
Why verify a download's checksum
A matching hash proves the downloaded file is byte-for-byte identical to the one the publisher released, ruling out network corruption, an interrupted download, or a tampered mirror serving a modified file.
Is my file uploaded to check the hash?
No — the file is read and hashed entirely within your browser using built-in cryptographic functions, so nothing about the file's contents is sent to any server, which is why even very large files can be checked without a lengthy upload.
MD5 versus SHA-256
MD5 and SHA-1 are fast but considered cryptographically weak for security purposes, though they remain fine for simple integrity checks such as confirming a transfer completed correctly. SHA-256 is the modern standard and is what most security-conscious software distributors now publish.
What to do if the hashes do not match
A mismatch means the file differs from the published original in some way — re-download it from the official source, and if the mismatch persists, treat the file as untrustworthy and do not run or open it.
Limits worth knowing before you rely on the output
A hash is not a malware scan or publisher-signature verification. Trust in the reference source is essential.