File Checksum Verifier

Check a downloaded file against its published checksum. Computes MD5, SHA-1, SHA-256, SHA-384 and SHA-512 locally and tells you instantly if the hash matches.

Drop the downloaded file here or click to select it

Expected checksum (optional)

Paste the hash from the download page. sha256sum output ("hash filename") also works. The algorithm is detected from the length.

Runs entirely in your browser. Your data is never uploaded.

What is File Checksum Verifier?

Software downloads often list a checksum (a SHA-256 or MD5 hash) so you can confirm the file arrived intact. Drop the file here and paste the expected checksum: the tool computes MD5, SHA-1, SHA-256, SHA-384 and SHA-512 in one pass and tells you whether the matching hash is identical. The file is read locally and never uploaded.

How to use File Checksum Verifier

Drop the downloaded file onto the box (or click to select it).
Paste the published value into Expected checksum; a full sha256sum line also works.
Read the result: a green matches message or a red does NOT match warning.
Copy any of the five computed hashes if you need them.

Example

Input

A text file containing "hello world" and a line break

Output

SHA-256: a948904f2f0f479b8f8197694b30184b0d2ed1c1cd2a1ec0fb85d299a192a447
MD5: 6f5902ac237024bdd0c176cb93063dc4

When to use File Checksum Verifier

Use it after downloading ISO images, installers, firmware or backups to detect corruption or tampering in transit. A matching checksum only proves the file equals the one the checksum was made from; if an attacker controls the download page they can change both, so prefer checksums from a separate, trusted source or signed releases. MD5 and SHA-1 are fine for detecting accidental corruption but not for security against deliberate attacks.

How File Checksum Verifier works

The file is read in 4 MB chunks and fed to incremental MD5, SHA-1, SHA-256, SHA-384 and SHA-512 hashers (WebAssembly implementations from hash-wasm), so even multi-gigabyte files can be checked without loading them fully into memory. The expected value is cleaned up (spaces, colons, file names, uppercase) and its length identifies the algorithm: 32 hex characters = MD5, 40 = SHA-1, 64 = SHA-256, 96 = SHA-384, 128 = SHA-512. The two hex strings are then compared.

Common Use Cases

Verifying a Linux ISO before writing it to a USB stick
Checking that a large backup copied without errors
Confirming a firmware or installer matches the vendor's SHA-256
Getting all common hashes of a file in one go

FAQs

Is my file uploaded?

No. The file is read by your browser and hashed locally; nothing leaves your device.

Which algorithm should I use?

Use the one the publisher lists. SHA-256 is the most common today. The tool detects it automatically from the length of the expected value.

What if the checksum does not match?

Download the file again, preferably from the official source. A mismatch means the file is corrupted, incomplete or not the file the checksum belongs to.