Category: Developer tools

Checksum Compare

System ideaMissing a tool?

Verify a download against its published hash

Paste the checksum a publisher listed, pick the file you downloaded, and see straight away whether they match. The file is read in your browser and never uploaded.

No file selected.
Computed digest (SHA-256)
The result will appear here.
Paste the published checksum to compare it.

The file is read in your browser and never uploaded.

Everything on this page is processed in your browser. Nothing is uploaded.

What this tool does

Publishing a checksum next to a download is how a project lets you tell a good copy from a corrupted or tampered one, and comparing sixty-four hex characters by eye is exactly the job people do badly. Paste what the publisher listed: the length says which digest it is, your file is hashed with the same algorithm, and the answer is one line instead of two strings to squint at. The checksum is accepted in the forms it actually arrives in, whether that is bare hex, the sha256sum output with the filename still attached, a sha256 prefix or colon-separated pairs. The file is read by the browser itself, so nothing is sent anywhere and the check still works offline.

How to use it

  1. Copy the checksum from the publisher's download page and paste it in as it stands — bare hex, sha256sum output with the filename still attached, a sha256 prefix or colon-separated pairs are all accepted, so there is no need to tidy it up first.
  2. Choose the file you actually downloaded, or switch to text mode if you only want to check a snippet rather than a file.
  3. Read the verdict line: the digests either match or they do not, so you never have to compare two strings character by character.

Privacy

This tool runs entirely in your browser. Your input is never uploaded, stored or shared — closing the tab removes it.

Frequently asked questions

How do I use Checksum Compare?
Three steps: paste the checksum published alongside the download, choose the file you downloaded (or switch to text to check a snippet), and read the verdict — the digests either match or they do not.
What form can the published checksum be in?
Paste it in the form it actually arrives in: bare hex, the sha256sum output with the filename still attached, a sha256 prefix, or colon-separated pairs. The length of what you paste says which digest it is, and your file is hashed with the same algorithm.
How do I read the result?
The result is a single verdict line — match or no match — instead of two hex strings to squint at. To check something else, paste a different checksum or pick a different file.
Is my file, input, or result uploaded?
No. The file is read by the browser itself, and your input, settings and the comparison result stay in the browser rather than being uploaded to LocalTools. Because nothing is sent anywhere, the check still works offline.
What does this tool not support?
It does one thing: the checksum you paste against the file you choose. It does not fetch or look up the publisher's checksum for you, and there are no accounts, sync, cloud history or server-side processing. Do not assume batch or export features that the page does not list.