Verystep Guides Verystep Guides

How to Hash a File and Verify a Checksum

Two minutes with a checksum tells you if that download arrived intact — or if you should delete it and start again.

Published November 14, 2026 - A Verystep guide

Illustration of a downloaded document with a fingerprint swirl and a shield with a check mark

Grab the expected checksum from the publisher's official page, note its algorithm, then hash your downloaded file with that same algorithm and compare the full strings in lowercase. A complete match means the file is bit-for-bit what was hashed; a mismatch means re-download from the official source and don't run it. This guide covers the steps in order, a worked check, and the limits — a checksum only protects you if the checksum itself came through a channel you trust.

Verify a download, step by step

It takes two minutes. Skip it and you're trusting that a big file crossed the internet untouched and that you grabbed it from the right place. Most days you'd be fine. The check exists for the day you wouldn't. Follow the steps in order — the algorithm match in step two is where most failed checks actually go wrong.

  1. Find the expected checksum on the publisher's official page or release notes and note which algorithm it uses.
  2. Open the hash tool and select the same algorithm — SHA-256, SHA-512 or MD5 — before you pick a file.
  3. Choose the file you downloaded; it stays on your device and is read locally in chunks, never uploaded.
  4. Wait for the hash to finish, especially on large files close to the 256 MB limit, then copy the full result.
  5. Compare the full strings in lowercase, ignoring any spaces or colons the publisher added for readability.
  6. If they match exactly, the file is bit-for-bit what was hashed; if they don't, delete it and re-download from the official source.
  7. If no checksum was published, hash a second copy from another source and compare the two — identical only proves the copies match, not that either is genuine.

A practical tip on comparing. Don't eyeball the first eight characters and call it done. Paste both strings into a text editor, one above the other, and scan the whole length. Better still, use find: search for your computed value inside the publisher's page. A full-length hit is a match. Anything less is a guess.

A worked check, start to finish

Say you've just downloaded an installer and the release page lists a SHA-256 checksum beside it. Copy that string first and keep it somewhere you won't lose it. Then open the tool, pick SHA-256 — not MD5, not SHA-512 — and choose the file you actually downloaded, not an older copy sitting in the same folder. That mix-up happens more than you'd think.

Document icon with a fingerprint-like swirl and two matching rows with a check mark
Same file, same algorithm, same string — that's a match. Nothing shorter counts.

Let it run. A small file finishes fast. A file near the 256 MB limit takes a moment because the browser reads it locally in chunks — nothing's uploaded, so your connection speed doesn't matter, but your patience might be tested on an old machine. When the result appears, compare every character. If the publisher printed the value in uppercase blocks with spaces, lower-case yours mentally and ignore the spacing. The hex digits themselves have to agree, all of them.

Match? Install with a clear conscience. Mismatch? Don't run it to see what happens. Delete it, go back to the official source, download again, and hash the fresh copy. If it still doesn't match, stop and contact the publisher — don't hunt for a mirror that gives you the answer you wanted.

What a match does — and doesn't — prove

A matching hash proves one narrow thing, and it proves it well: the file on your disk is bit-for-bit identical to the file that produced the published checksum. No flipped bits in transit. No truncation. No quiet edit along the way. That's worth having.

It doesn't prove the file is safe, well-built, or even from who you think it's from — not on its own. The whole check leans on the checksum itself arriving through a channel you trust. If you copied the expected value from the same dodgy page that served you a tampered file, an attacker can just publish a matching fake checksum next to it. Match achieved. Protection zero. So get the checksum from the publisher's official site or signed release notes, ideally over HTTPS, and treat a checksum pasted into a random forum post as decoration.

The no-checksum case is weaker still. Hash two copies from two places and compare them. If they agree, you've shown the copies are identical — useful against a corrupt download — but you haven't shown either copy is genuine. Say that plainly to yourself before you proceed.

Mistakes that make good checks fail

Wrong algorithm is number one. A SHA-256 value will never match an MD5 value for the same file, because they're different functions producing different lengths. If your result is much shorter than the published string, you've picked the wrong algorithm. Go back and check the label, not the file.

Hashing the wrong thing is close behind. People hash the .zip when the publisher hashed the file inside it, or they hash a file after it's been extracted, renamed and re-saved. Hash exactly what was published, in exactly the form you downloaded it. And if you're hashing text instead of a file, watch line endings and a trailing newline — the tool hashes text too, and a single extra character changes the whole result.

About MD5: it's in the tool for legacy checksums only, because plenty of older releases still publish MD5 values and you can't verify those any other way. Don't choose it for anything new if you've got a choice. Publishers who still offer SHA-256 are giving you the stronger check — take it.

Hash your file without uploading it

The Verystep hash tool computes SHA-256, SHA-512 or MD5 in your browser. Pick a file up to 256 MB and it's read locally in chunks — never uploaded — or paste text to hash that instead. Select the same algorithm the publisher used, then compare the full result.

Open the SHA-256 Hash Generator ->

Last verified November 14, 2026 — workflow and limits checked against the live Verystep hash tool page (SHA-256 / SHA-512 / MD5, local chunked file reading, 256 MB maximum, no upload).

Frequently asked questions

What should I do if the checksums don’t match?

Don't install or run the file. Delete it, re-download from the publisher's official source, and hash the fresh copy. If it still doesn't match, stop there and contact the publisher rather than trying mirrors until one happens to match.

Can I compare just the first few characters?

No — compare the whole string. Two different files can share a short opening by chance in your quick glance, and a near-match is still a mismatch. Paste both values into an editor, compare in lowercase, and ignore only the spaces or colons some publishers add for readability.

Is my file uploaded when I hash it here?

No. The file's read locally in chunks in your browser, up to a 256 MB maximum, and the hash is computed on your device. Nothing's sent to a server, which is also why a large file's speed depends on your machine, not your connection.

Why is MD5 still offered if SHA-256 exists?

For legacy checksums only. Plenty of older releases publish MD5 values and nothing else, so you need MD5 to verify those at all. When a publisher offers SHA-256 as well, use that instead — and never compare values across algorithms, because they'll never match.

What if the publisher gives no checksum at all?

You can still hash two copies downloaded from different sources and compare them. If they agree, you've ruled out a one-off corrupt download. You haven't proved either copy is genuine, though — that assurance only comes from a checksum supplied through a trusted channel.

More guides