Security Tools

Checksum Verifier

Verify a downloaded file's integrity by comparing its checksum against a published value — instantly inside your browser.

Private by default Instant results No signup
Checksum VerifierLive
Computed SHA-256 checksum
Overview

Why verify a checksum?

Software downloads are often published alongside a checksum — a hash of the exact file — so you can confirm the file you downloaded matches exactly what the publisher released, with no corruption from a bad download and no tampering from a compromised mirror. This tool computes a file's checksum locally and compares it against the one you paste in.

Guide

How to use it

1Upload or drag in the file you want to verify
2Choose the algorithm the publisher used
3Paste the expected checksum
4Check whether it matches

How the verification works

The file's exact bytes are hashed locally using the algorithm you select — MD5, SHA-1, SHA-256, or SHA-512 — and the result is compared case-insensitively against the checksum you paste in. If they match exactly, the file is byte-for-byte identical to what the checksum was generated from.

Why it helps

Features & benefits

Supports MD5, SHA-1, SHA-256, and SHA-512
Clear match/mismatch result
Case-insensitive comparison
Works entirely on your local file — no upload needed
100% private — nothing leaves the device

Why this runs entirely in your browser

The file you're verifying stays on your device — hashing happens in JavaScript locally in the tab, and the file itself is never uploaded anywhere.

Common uses

Verifying a downloaded installer or ISO matches its published checksum, checking a file wasn't corrupted during transfer, or confirming a file hasn't been tampered with before running it.

Frequently asked questions

A few things people usually want to know before trusting the numbers.

Use whichever one the publisher provided a checksum for — it's usually labeled clearly, like "SHA256SUMS" or "MD5 checksum". SHA-256 is the most common choice for modern software releases.

The file differs from what the checksum was generated from — this could mean a corrupted or incomplete download, or in rarer cases, a tampered file. Try re-downloading before assuming the worst.

No — the comparison is case-insensitive, so it doesn't matter whether the published checksum uses uppercase or lowercase hex digits.

No. The file never leaves your device — hashing happens locally in your browser using its raw bytes.

No. Everything happens locally in your browser. Nothing about the file is sent to a server, stored, or shared.