Hash · Checksum · Integrity

Verify file integrity in your browser

Drop a file or paste text — compute MD5, SHA-1, SHA-256, or SHA-512. Nothing leaves your device.

Drop a file or paste text below to compute its hash.

SHA-256

Computing…

Input

Drop file here or click to browse

Large files (ISO images, backups) are processed locally — nothing is uploaded

SHA-256 is recommended for integrity checks. MD5 and SHA-1 are provided for legacy compatibility only.

Storing ISOs or backups? A dedicated NAS-rated drive from WD or Seagate keeps your backup library reliable and checksumable for years. See NAS and backup drives →

What a checksum actually proves

A cryptographic hash function takes a file of any size and produces a fixed-length fingerprint — change even one bit of the file and the hash comes out completely different. Comparing a downloaded file's hash against the one the publisher listed confirms the file transferred intact and matches exactly what they published; it does not confirm the file is safe or malware-free, only that it's identical to the source.

Which algorithm to use

SHA-256 is the current standard for file integrity verification — use it if the publisher offers a choice. MD5 and SHA-1 are both cryptographically broken (collisions are practical to engineer) and shouldn't be trusted for anything security-sensitive, but they're still common for basic accidental-corruption checks on older software distributions where that's all that's offered.

Why do MD5 and SHA-1 still show up if they're broken?

They're broken specifically for security purposes — an attacker can deliberately craft two different files with the same MD5/SHA-1 hash. For catching accidental corruption during a download (the far more common real-world case), they still work fine; just don't rely on them to detect deliberate tampering.

Why don't my file's hash and the published hash match?

Either the download is corrupted/incomplete, or you're comparing against the wrong file version. Re-download and recheck first — that resolves the overwhelming majority of mismatches — before assuming anything more serious.

Does this tool upload my file anywhere to check it?

No — the hash is computed entirely in your browser using the Web Crypto API. The file itself never leaves your device.

From the blog: Backups That Look Good on Paper and Fail When You Need Them

All computation happens in your browser. No data is sent to any server.