Hashed on your device โ€” never uploaded

File Hash Checker

Calculate SHA-256, SHA-1 and MD5 checksums of any file and verify downloads against the hash published by the developer โ€” without the file ever leaving your machine.

Drop any file here or click to browse Tap to choose a file
Any file type ยท hashed locally in your browser

What is a file hash and why verify it?

A hash (checksum) is a short fingerprint computed from a file's entire contents. Change even one byte of the file and the fingerprint changes completely. That makes hashes the standard way to answer two everyday questions: "Is this download exactly what the developer published?" and "Are these two files identical?"

Software projects publish a SHA-256 checksum next to their download links precisely for this. After downloading, you compute the hash of your copy and compare. A match proves the file wasn't corrupted in transit and wasn't tampered with by a mirror, proxy, or malware. A mismatch means: don't run that installer.

This tool computes three common algorithms at once: SHA-256 (the modern standard you should prefer), SHA-1 and MD5 (older, still widely published for legacy reasons โ€” fine for integrity checks, no longer trusted against deliberate forgery). Paste the expected hash into the field above and the tool highlights the match automatically โ€” no squinting at 64 hex characters.

Files you verify are often installers, backups or private archives. Hashing here happens fully on your device via the browser's built-in crypto engine โ€” nothing is uploaded, and there are no artificial size limits.

Frequently asked questions

Which algorithm should I use?
Compare whatever the publisher provided. If you have a choice, use SHA-256. MD5 and SHA-1 still detect accidental corruption fine, but can't be trusted against a deliberate attacker.
Is there a size limit?
The practical limit is your device's free memory โ€” files up to a gigabyte or two hash comfortably on a typical laptop, in a few seconds.
Can I compare two files?
Yes โ€” hash the first file, copy its SHA-256 into the "expected hash" field, then drop the second file. A green match means the files are byte-for-byte identical.

Related tools