Software safety / 2026-11-19

How to verify a download with a SHA-256 checksum

What the long string of letters and numbers beside a download is for, how to check it on Windows, macOS and Linux, and what a matching checksum does and does not prove.

Small business

By MyEvent Labs

Many download pages show a long string of letters and numbers labelled SHA-256, or link to a file called SHA256SUMS. Most people ignore it. It takes about a minute to use, and it answers one specific question: is the file on my disk exactly the file the publisher released?

This guide covers what a checksum is, the one command you need on each operating system, and the limits of what a match tells you.

What a checksum is

SHA-256 is a hash function. It reads a file of any size and produces a fixed 64-character fingerprint. Two properties make it useful:

  • The same file always gives the same fingerprint. It does not matter which computer or operating system calculates it.
  • Any change gives a completely different fingerprint. Altering a single byte, whether through a corrupted download or deliberate tampering, changes the result beyond recognition.

So if the fingerprint you calculate matches the one the publisher printed, your copy is byte-for-byte identical to theirs.

When it is worth checking

You do not need to verify every file. It is worth the minute when:

  • The file is an installer or a command-line tool, which will run with your permissions.
  • The download was large, slow or interrupted, and you want to rule out corruption before you troubleshoot anything else.
  • The file came from a mirror, a content delivery network or a colleague, rather than directly from the publisher.
  • You are installing the same file on several machines and want to know they all have the same build.

Windows

Open PowerShell in the folder that holds the download and run:

Get-FileHash .\tool-windows-x64.zip -Algorithm SHA256

PowerShell prints the hash in capitals. Publishers usually print it in lower case. The letters are the same either way, and you can let PowerShell do the comparison so you are not reading 64 characters by eye:

(Get-FileHash .\tool-windows-x64.zip).Hash -eq "paste-the-published-hash-here"

It answers True or False. In the older Command Prompt, certutil -hashfile tool-windows-x64.zip SHA256 gives the same fingerprint.

macOS

Open Terminal and run:

shasum -a 256 ~/Downloads/tool-macos-arm64.tar.gz

The -a 256 part matters. Without it, shasum uses the older SHA-1 algorithm and the result will never match a SHA-256 value.

Linux

sha256sum tool-linux-x64.tar.gz

If the publisher provides a SHA256SUMS file that lists several downloads, save it into the same folder and let the tool do the comparison:

sha256sum -c SHA256SUMS --ignore-missing

Each file you have downloaded is reported as OK or FAILED. The --ignore-missing option stops it complaining about the platforms you did not download.

If the checksum does not match

Do not run the file. A mismatch has a short list of causes, and most are dull:

  1. The download was incomplete. Compare the file size with the one on the page, delete the file and download it again.
  2. You are comparing against the wrong entry. A SHA256SUMS file has one line per platform and per version. Check the file name on the line matches yours exactly.
  3. The release was updated. If the publisher replaced a build, an old page or a cached copy can show an outdated hash.
  4. The file was altered. This is the rare case the check exists for. If a second download from the official page still does not match, stop and tell the publisher.

What a match does not prove

A checksum proves integrity, not trustworthiness. It is worth being clear about the difference.

  • It does not prove the software is safe. A faithfully downloaded copy of a harmful program still matches its checksum.
  • It does not prove who published it. If the page you downloaded from was itself tampered with, an attacker could replace both the file and the hash printed beside it. A checksum is strongest when you read it from a different place to the file, or when the page is the publisher's own site served over HTTPS.
  • It is not a signature. Code signing ties a file to a verified publisher identity and is checked by the operating system. A checksum is a simpler tool that you check yourself.

In practice the two work together. Signing tells you who built the file. The checksum tells you that the copy you hold is the one they released.

How we publish checksums

We publish SHA-256 values for our own downloads so you can run exactly this check. The Tab Cleaner page prints the hash of its ZIP beside the download, and command-line tools such as Postr link a SHA256SUMS file that covers every platform archive in the release.

A one-minute habit

  1. Download the file from the publisher's own page.
  2. Calculate the SHA-256 with the command for your system.
  3. Compare it with the published value, letting the computer do the comparison where it can.
  4. If it does not match, download again before you do anything else.

It is a small step, and it removes a whole class of doubt before you install something.

This sits inside the work we do . Discuss a digital project

MORE FROM INSIGHTS

Software safety / 2026-11-19

How to check a browser extension before you install it ↗

How to read the permissions an extension asks for, what the common ones really allow, and how to load an extension from a ZIP in developer mode in Chrome or Edge.

Software safety / 2026-11-19

Why Windows and macOS warn you about an app you just downloaded ↗

What the SmartScreen and Gatekeeper warnings actually mean, what code signing does and does not tell you, and how to decide whether to open an app the system has flagged.