How File Checksums (SHA-256) Verify Your Downloads
Software download pages often show a long string of letters and digits labelled SHA-256 or checksum. Most people ignore it, which is understandable, but it is one of the simplest and most useful safety checks available. In a minute, it can tell you whether the file on your computer is exactly the file the publisher released, or whether it was damaged or altered on the way. This guide explains what a checksum is, how to verify one, and what a match does and does not prove.
What a checksum is
A checksum, more precisely a cryptographic hash, is a fixed-length fingerprint calculated from a file's contents. SHA-256 always produces 64 hexadecimal characters, whether the file is a tiny text note or a multi-gigabyte installer. Two properties make it useful:
- It is deterministic. The same file always gives the same fingerprint.
- It is extremely sensitive. Change a single byte of the file and the fingerprint changes completely, in a way that looks random.
It also works one way: you cannot rebuild the file from its fingerprint, and it is infeasible to craft a different file with the same SHA-256 on purpose. That is why a published checksum can serve as an identity check for a download.
Why verify a download at all?
Files can go wrong in two ways. Accidentally, a download can be interrupted or corrupted by a bad connection, a failing disk or a faulty cache, so that the file looks fine but fails halfway through installation. Deliberately, a file can be replaced with a modified one on a compromised mirror or a look-alike site. A checksum check catches the first kind reliably and, under the right conditions, helps with the second.
Step by step with Verify checksum
- Download the file as usual. Find the checksum the publisher lists, usually next to the download link, in a text file such as
SHA256SUMS, or in the release notes. Note which algorithm it names. - Open Verify checksum.
- Choose the downloaded file from your device. The file is hashed locally in your browser; it is not uploaded.
- Paste the published checksum into the box. You may paste a single value, or the contents of a checksum list, including lines in the common "hash, then filename" format.
- Click Verify. The tool tells you whether the values match.
If you just want the number, File Hash calculates MD5, SHA-1, SHA-256 and SHA-512 for up to 20 files at once, and lets you pick which algorithms to show. Text Hash does the same for pasted text.
Reading the result
A match means the file's bytes are identical to those the checksum was made from. A mismatch means something differs, and you should not run or open the file. Before you worry, rule out the usual harmless causes:
- You compared against the wrong algorithm; a SHA-256 value is 64 characters long, a SHA-1 value 40, an MD5 value 32.
- You compared against a different version or a different platform's installer.
- The download was truncated. Download again and retry.
- You copied extra spaces or missed a character. Letter case does not matter for hexadecimal checksums.
If a fresh download from the official source still mismatches, treat the file as untrustworthy and report it to the publisher.
What a matching checksum does not prove
This part is important. A match proves that your copy equals the file the checksum describes. It does not prove that the file is safe. If an attacker controls the web page, they can change both the file and the checksum shown beside it, and the two will match perfectly. For that reason:
- Prefer a checksum published on a different, trusted channel than the download itself, such as the project's official site, while the file comes from a mirror.
- Prefer publishers who also sign their releases with a cryptographic signature; verifying that signature offers stronger assurance than a plain checksum, though it takes more tooling than a browser tool offers.
- Remember that a checksum says nothing about whether the original software is malicious. Download from official sources and keep your security software on.
Which algorithm should I use?
Use whatever the publisher provides, but if you have a choice, choose SHA-256 or SHA-512. MD5 and SHA-1 are older and have known weaknesses against deliberate tampering. They still catch accidental corruption, which is why they remain on many download pages, but they are not suitable where someone might try to forge a collision. Also note that hashing a password with a plain fast hash is not secure storage, so do not use these tools or algorithms as a substitute for password hashing in an application. If you need a strong password for an account, Password Generator creates random ones.
Other practical uses
You can use checksums for your own files too. Before archiving an important backup or sending a large file, record its SHA-256; later you can recompute it to prove nothing has changed. To check that two files are identical without opening them, hash both and compare. When you send a ZIP created with Create ZIP, include the checksum in your message so the recipient can confirm integrity. For sensitive files, File Encrypt adds password-based encryption, which is a different job: encryption hides contents, a checksum verifies integrity. Both run on your device, a topic covered in our guide to how browser-based conversion keeps files private.
A short habit worth building: whenever a project publishes both a file and a checksum, take thirty seconds to compare them, and note the result somewhere. If you manage downloads for a team, paste the expected checksum into your instructions so everyone can verify the same way. Over time this turns a rarely used security feature into a normal part of installing software, and it costs almost nothing.Written by SmarTech Apps. General information only, not legal or professional advice. Questions or corrections? Contact us.