Account

What new tool do you want?

Security & Privacy

File Checksum / Hash Verifier (SHA-256, MD5)

Calculate SHA-256, SHA-1, SHA-512 and MD5 checksums of any file in your browser — and compare with the published hash to verify a download.

How to use

  1. 1Choose or drop a file — the hashes are calculated locally.
  2. 2Paste the checksum from the download page to see if it matches.

Frequently asked questions

Why verify a checksum?

It proves the file you downloaded is exactly the one published — not corrupted or tampered with.

Which hash should I use?

SHA-256 is the standard today. MD5 and SHA-1 are fine for spotting corruption but not for security.

Is the file uploaded?

No — hashing runs in your browser, so even large or private files never leave your device.

What a matching checksum actually proves

A hash function turns a file's exact bytes into a fixed-length fingerprint, and changing even one byte produces a completely different result — so a match means the file you have is byte-for-byte identical to the one the publisher hashed. It doesn't prove the publisher is trustworthy or that the file is free of malware; it only proves your download wasn't corrupted in transit, truncated by a flaky connection, or swapped out by a man-in-the-middle on an insecure mirror. Checksums answer "is this the exact file they published," not "is this file safe."

Worked example: File Checksum / Hash Verifier

A file containing just the text "hello" (no newline) hashes to 2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824 in SHA-256 and 5d41402abc4b2a76b9719d911017c592 in MD5 — you can verify this yourself with `echo -n hello | shasum -a 256`. An empty file always hashes to the same well-known SHA-256 value, e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855, regardless of its filename — a useful sanity check if a "0 bytes" download looks suspicious.

Why MD5 has a file-size limit here and SHA doesn't

SHA-256, SHA-1 and SHA-512 are computed with the browser's native Web Crypto API (crypto.subtle.digest), which is implemented in optimized native code and handles large files efficiently. MD5 isn't exposed by that API at all — browsers dropped it for being cryptographically broken — so this tool runs a pure-JavaScript MD5 implementation instead, which is far slower on large inputs. That's why MD5 is capped at 512MB here: past that, the JS implementation would stall the browser tab rather than finish in reasonable time. If you only need to confirm a download isn't corrupted, prefer SHA-256 when it's offered rather than waiting on MD5 for a large file.

Nothing leaves your device

The whole process — reading the file into memory, hashing it, and comparing against the pasted checksum — happens in your browser tab via the File and Web Crypto APIs. No upload occurs, which is why this works for arbitrarily large or sensitive files (an ISO image, a private backup) just as well as a small download.

You can paste a checksum line, filename and all

The compare box ignores capital letters, and you do not have to say which algorithm you copied. It looks for one unbroken run of hexadecimal: 128 characters for SHA-512, 64 for SHA-256, 40 for SHA-1, or 32 for MD5, preferring the longer match. A line from a download page — the hash, then spaces, then the filename — works, because the filename is ignored. The matching row is highlighted. The hashes themselves are shown in lowercase. If the file is larger than 512 MB, MD5 is skipped. A correct MD5 pasted for a file that large will say there is no match, while the SHA-256, SHA-1, and SHA-512 rows are still listed.

A file that will not fit fails before any hash appears

The whole file is read before the first hash is shown. If it will not fit, you see Couldn't read this file — it may be too large for your browser's memory. That is separate from the 512 MB limit on MD5. A smaller file can still fail when the tab runs out of memory, and a file over 512 MB can still show SHA-256, SHA-1, and SHA-512 when the read succeeds. The rows appear in that order, then MD5, and each row shows up as soon as it is ready, so you can copy SHA-256 while SHA-512 is still calculating. Over 512 MB, the MD5 row is simply missing.

Related tools

More: Security & Privacy