File checksum calculator
Runs in your browserCalculate SHA-256, SHA-512, SHA-1, MD5 and BLAKE2 checksums of files in your browser and compare them with an expected hash or a SHA256SUMS file. Nothing is uploaded.
Drop the file you downloaded and paste the checksum from the website. The tool tells you whether they match.
What a checksum proves, and what it doesn’t
A matching checksum proves the file is exactly the one the checksum was made from: not corrupted on the way, not changed on a mirror. It doesn’t prove who made it. If an attacker can change the download page, they can change the checksum too. That’s why projects sign the checksum file: gpg --verify SHA256SUMS.gpg SHA256SUMS.
Check a download on Linux, macOS and Windows
sha256sum ubuntu.iso sha256sum -c SHA256SUMS --ignore-missing # check against the list
shasum -a 256 ubuntu.iso shasum -a 256 -c SHA256SUMS --ignore-missing
Get-FileHash .\ubuntu.iso -Algorithm SHA256 certutil -hashfile ubuntu.iso SHA256
echo "EXPECTED_HASH ubuntu.iso" | sha256sum -c -
Choosing the algorithm
The default for downloads today. Collisions are not practical.
Fine to catch broken downloads, not against attackers: collisions can be made on purpose.
A SHA256SUMS file has one line per file: hash, two spaces, name. The tool reads that, the BSD form SHA256 (file) = …, PowerShell and certutil output.
Questions about the file checksum
How do I check the SHA-256 of a download?
Drop the file above and paste the SHA-256 from the download page. Or run sha256sum file (Linux), shasum -a 256 file (macOS) or Get-FileHash file (Windows).
Is my file uploaded?
No. It is read in chunks by your browser and hashed locally; even multi-gigabyte ISO images never leave your computer.
The checksum doesn’t match. What now?
Download again, ideally from the official site rather than a mirror. If it still differs, compare the algorithm (a SHA-512 can’t match a SHA-256) and the file name.