Home › Toolkit › Utilities › File Hash Checker

🧬 File Hash Checker

A download claims a checksum; is your copy the real one? Hash the file here — MD5 and the SHA family, computed over the raw bytes on your own device — and compare digit for digit.

About this tool

A hash is a fingerprint computed from data: run the algorithm over a file and you get a fixed-length string that changes completely if even one byte differs. Publishers post SHA-256 checksums beside downloads so you can prove the file you received is the file they sent — not corrupted in transit, not swapped by anyone in between. This checker computes MD5, SHA-1, SHA-256 and SHA-512 over the file's raw bytes, using the browser's own cryptographic engine for the SHA family and a hand-written MD5 for completeness.

The privacy property is the point of doing this in a browser: the file never leaves your device. Hashing a confidential document on a stranger's server would defeat the purpose of checking it. One distinction to keep: a matching hash proves the file matches the checksum — so the checksum itself must come from a trustworthy place, ideally the publisher's own site over HTTPS, not the same page that served the download.

How to use it

  1. Choose the file (or type text if no file is chosen).
  2. Press Compute hashes.
  3. Compare the SHA-256 line with the publisher's checksum — they must match character for character.

Good to know

  • Compare the middle as well as the ends; the eye skips, the clipboard does not — paste both into a document and eyeball them in the same font.
  • MD5 and SHA-1 are fine for spotting accidental corruption, but collisions can be crafted for both; trust SHA-256 or SHA-512 for security decisions.
  • A hash of text here uses its UTF-8 bytes — the same bytes any standard tool would hash.

Frequently asked questions

Is my file uploaded?

No. Hashing happens on your device; only the fingerprint strings are shown.

Which hash should I compare?

SHA-256 is the common standard publishers post. If they offer SHA-512, that is stronger still.

The hashes differ but the file opens fine — what now?

Treat it as not the publisher's file: re-download from the official source. A changed byte in an installer is exactly what checksums exist to catch.

More Utilities tools

Making videos too? Try our YouTube Channel Audit, or browse the full Toolkit and the free YouTube tools.