## Why SHA-256 Replaced MD5 for Software Verification
Last month I downloaded a firmware update for a router. The manufacturer's page listed a SHA-256 checksum alongside the download link. Not MD5. Not SHA-1. SHA-256. That's the industry standard now, and there's a good reason for it.
SHA-256 produces a 64-character hexadecimal hash. It has no known practical collision attacks. While MD5 and SHA-1 have been broken for years, SHA-256 remains cryptographically sound as of 2026. Every major Linux distribution, every firmware vendor, and every serious software project publishes SHA-256 checksums for their releases.
What a SHA-256 Hash Looks Like
Here's a real example. The SHA-256 hash of an empty file is:
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
64 characters. Hexadecimal. Change one bit in the input and the entire output changes — that's the avalanche effect, and it's what makes hashes useful for detecting any modification.
How to Calculate SHA-256 of a File
### Linux and macOS
bash sha256sum ubuntu-24.04.1-desktop-amd64.iso
Output looks like:
4f3d2c1b8a7e9d6c5b4a3f2e1d0c9b8a7f6e5d4c3b2a1f0e9d8c7b6a5d4c3b2 ubuntu-24.04.1-desktop-amd64.iso
On macOS, you can also use shasum:
bash shasum -a 256 ubuntu-24.04.1-desktop-amd64.iso
### Windows
PowerShell makes this trivial:
powershell Get-FileHash ubuntu-24.04.1-desktop-amd64.iso -Algorithm SHA256
Get-FileHash defaults to SHA256, so you can even omit the algorithm flag.
### Without a Terminal
If you can't or don't want to use the command line, calculate SHA-256 in your browser. Upload the file, and the hash is computed locally — nothing leaves your machine.
Verifying a Real Ubuntu Download
Let's walk through a full verification. You download ubuntu-24.04.1-desktop-amd64.iso from the Ubuntu mirror. You also grab the SHA256SUMS file from the same directory.
bash sha256sum -c SHA256SUMS
This reads the expected hashes from the file and checks every matching file in the directory. You'll see output like:
ubuntu-24.04.1-desktop-amd64.iso: OK
But here's the catch: you downloaded both the ISO and the checksum file from the same server. If that server was compromised, both could be fake. That's why Ubuntu also publishes a GPG signature for the checksum file. The truly paranoid verify the signature first, then the checksum.
For most users, downloading over HTTPS from the official domain is sufficient. For security-critical work, verify the signature too.
Verifying Linux ISO Checksums: Ubuntu, Fedora, Debian, and Arch
An ISO file becomes your operating system. If it has been tampered with, you are installing a backdoor at the kernel level. Here is how to verify ISOs for popular distributions.
### Ubuntu
Ubuntu publishes SHA-256 checksums for every ISO. Download the SHA256SUMS file from the same directory as the ISO, then:
bash sha256sum -c SHA256SUMS
You will see `ubuntu-24.04.1-desktop-amd64.iso: OK` if the ISO matches. Ubuntu also signs the checksum file with GPG, so you can verify the checksum itself is authentic:
bash gpg --verify SHA256SUMS.gpg SHA256SUMS
### Fedora
Fedora provides a verification script:
bash ./fedora-image-checker --iso Fedora-Workstation-Live-x86_64-40.iso
Or manually compute the hash and compare it to the checksum on the Fedora download page.
### Debian
Debian publishes SHA-256, SHA-512, and MD5 sums, plus GPG signatures for all of them. They recommend verifying both the checksum and the GPG signature, since a compromised mirror could serve a matching fake ISO and fake checksum.
### Arch Linux
Arch publishes checksums on their download page. No separate checksum file needed. Arch also signs their ISOs directly with GPG, so you can verify the signature on the ISO itself.
### Why ISO Verification Matters More Than Other Files
A corrupted text file is obvious. A corrupted installer might fail partway through. But a corrupted ISO can boot fine and install a system with subtle, hard-to-detect problems. A tampered ISO can install a system that looks normal but contains a rootkit. The installer runs with full privileges, so anything malicious is present from the start.
Why Not Just Use HTTPS?
People ask this a lot. If the download is over HTTPS, doesn't that guarantee integrity?
HTTPS guarantees integrity **in transit**. It does not guarantee the file on the server is correct. The server itself could be compromised. The file could have been replaced after upload. HTTPS protects the pipe, not the source.
A checksum published separately — ideally on a different server, or signed with a GPG key — gives you a second source of truth. That's the whole point.
Common Mistakes
**Comparing only the first few characters.** A collision attack might share a prefix. Compare the entire 64-character string. Better yet, let a tool do it.
**Using a checksum from the same download page without checking the URL.** A phishing site can host both a fake binary and a matching fake checksum. Verify you're on the official domain.
**Forgetting that different versions have different hashes.** Ubuntu 24.04.1 and 24.04.0 have different SHA-256 sums. Make sure you're comparing against the right version's checksum.
When to Use SHA-256 vs Something Else
SHA-256 is the sweet spot for most use cases. It's fast enough for large files, strong enough for security verification, and supported everywhere. SHA-512 is more secure but slower and overkill for file verification. BLAKE3 is faster but less widely supported. For a deeper comparison, see our SHA-1 vs SHA-256 vs SHA-512 breakdown.
Start Verifying Your Downloads
It takes ten seconds to verify a SHA-256 checksum. It catches corrupted downloads, protects against tampered files, and gives you confidence that the software you're about to run is what the publisher intended. Make it a habit. Or just use our online SHA-256 checker and skip the terminal.,