Checksum / hash

Compute SHA-256 and SHA-1 of any file locally - verify downloads and file integrity.

Checksum / hashFREE
Drop a file here or browse SHA-256 & SHA-1 computed on your device

How checksums work

A checksum is a short fingerprint of a file. Run the same file through the same hash function and you always get the same value; change a single byte and the value changes completely. That makes checksums the standard way to confirm a download arrived intact, or that two files are truly identical.

This tool computes SHA-256 and SHA-1 with your browser's built-in Web Crypto engine, so even large files are hashed on your own machine. To check a download, compare the SHA-256 here against the one the vendor publishes. If they match, the file is genuine and complete.

Good to know

  • SHA-256 is the modern default for verifying downloads and releases.
  • SHA-1 is here for older tools that still list it, but it is no longer safe against collisions.
  • Everything runs locally through the Web Crypto API, so the file stays on your device.
  • MD5 is left out on purpose: it is broken for integrity checks.

Frequently asked questions

What is a checksum good for?
Two things, mostly: confirming a download was not corrupted or tampered with, and checking whether two files are byte for byte identical.
SHA-256 or SHA-1: which should I use?
Use SHA-256. Only fall back to SHA-1 when you are matching a value from an older tool that still publishes it.
Is my file uploaded to compute the hash?
No. The hashing runs in your browser through the Web Crypto API, so the file never leaves your computer.
Why is there no MD5?
MD5 has been broken for years, since two different files can share one MD5, so it is not safe for checking integrity. We stick to SHA.