Map Extract
Free tool

Verify a file checksum

Paste the checksum printed on a download page, choose the file you downloaded and get a clear match or no match. The checker works out which algorithm the checksum uses from its length and compares the file against all of them.

Runs in your browser. Nothing you enter is uploaded.

Checking a download

  1. Copy the expected checksum

    Find it on the vendor's download or release page, often labelled SHA-256, checksum or hash. Copy the whole value.

  2. Paste it into the box

    The note underneath says what it looks like: MD5 for 32 characters, SHA-1 for 40, SHA-256 for 64, SHA-384 for 96 and SHA-512 for 128. Anything else is reported as not a recognised length.

  3. Choose the file

    Pick the file you downloaded. It is read on your device and hashed with all five algorithms.

  4. Read the verdict

    A green Match names the algorithm that agreed. A red No match means the file differs from the one the checksum describes and should be downloaded again from the official source.

  5. Look at the full table if needed

    Every hash of the file is listed, which helps if a vendor publishes two different checksums or labels them unclearly.

Example: confirming a supplier's price list was not edited

A wholesaler emails a CSV price list to a farm shop (both fictional) and includes its SHA-256 in the message so the shop can be sure the attachment is the version that was sent. The original file gives a match.

A copy where one price was changed from 3.20 to 3.40 gives a completely different SHA-256, so the checker shows No match. Even a single character changed anywhere in the file has that effect.

Input
Expected: c73dd73aa54ce47e09cef066127df637643930402dd96b15f7e4dcb3f7d79215
File: pricelist.csv (75 bytes)
Result
Looks like SHA-256.
✓ Match: pricelist.csv has the expected SHA-256 checksum.

Edited copy: SHA-256 a7f88e42843c67b9886c4f2c32930ec2072fdeb8c12a23f064242fa808bb5b05
✗ No match.

When a checksum does not match

  • Check you copied the whole checksum, with no missing characters at either end. Spaces and capital letters do not matter.
  • Make sure you chose the same file the checksum is for; installers often come in several versions for different systems.
  • Download the file again, directly from the vendor rather than a mirror or a link in an email, and check again.
  • If it still does not match, do not open or install it. Tell the vendor, because their file or their published checksum is wrong.

Questions people ask

How do I verify a SHA-256 checksum on Windows?

You can run certutil -hashfile yourfile SHA256 in Command Prompt and compare the output by eye. This page does the same calculation in your browser and compares the result for you, which avoids misreading a 64-character string. Either way, the expected value must come from the official source.

Is MD5 good enough to check a download?

MD5 still catches accidental corruption, such as an interrupted download. It is not safe against deliberate tampering, because attackers can craft two different files with the same MD5. If the publisher offers SHA-256, use that. The checker accepts MD5 for older sites that publish nothing else.

Does the file get uploaded?

No. The file is read by your browser and hashed on your device. Nothing is sent to Map Extract or any other server, which also means large files are limited only by your computer's memory and the time it takes to read them.

Why do I get No match before choosing a file?

You will not: the verdict only appears once there is both an expected checksum and a file. If you paste the checksum after choosing the file, the result updates immediately. The hashes of the file stay in the table so you can compare against more than one value.

Where your data goes

The file you choose is read and hashed entirely in your browser. Neither the file nor the checksum is sent to Map Extract or anyone else.

Checked against the tool on

Top