LocalToolsOffline browser tools collection

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. Paste the checksum published alongside the download.
  2. Choose the file you downloaded, or switch to text to check a snippet.
  3. Read the verdict: the digests either match or they do not.

Privacy

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

Frequently asked questions

Is my file uploaded to check it?
No. The file is read with the browser own file API and hashed in the page. It never leaves your device, which is also why the check works offline.
How does it know which algorithm to use?
From the length of the checksum you paste: 40 hex characters is SHA-1, 64 is SHA-256, 96 is SHA-384 and 128 is SHA-512. You can also pick one by hand when checking text.
The checksums do not match. What now?
Download the file again, ideally from the original source over HTTPS. A repeated mismatch means the copy differs from what the publisher signed, and it should not be run.

Back to all tools