Skip to content
100% in your browser. Nothing you paste is uploaded — all processing runs locally. Read more →

File Hash Calculator

Drop a file or pick one with the file picker — get all common hashes side-by-side. Paste the publisher's expected hash to instantly verify your download. Files never leave your browser.

MD5
SHA-1
SHA-256
SHA-384
SHA-512

How to verify a download

  1. Find the publisher's expected hash. Open-source projects post it on the download page or in a SHASUMS / checksums.txt file.
  2. Paste that expected hash into the "Compare to" field above.
  3. Pick your downloaded file with the file picker.
  4. If "✓ Match" appears, the file is intact. If not, your download is corrupt or tampered with.

What hash should you compare against?

What this catches

What this does not catch

For critical downloads (OS images, security tools), pair the hash check with a signature check (gpg --verify on the detached signature file). The signature is what binds the hash to the publisher's identity.

Need text instead? Hash text on the home page. Want to learn more? Which hash function should you use?

FAQ

Is the file uploaded anywhere?

No. The file is read into memory by your browser and hashed locally. Open DevTools → Network and confirm: there are zero requests during hashing. Even multi-hundred-MB files stay on your machine.

What's the maximum file size?

Limited by your browser's memory. Typically 500 MB to 1 GB on desktop, less on mobile. For multi-GB files, use the command line: sha256sum <file> on Linux, shasum -a 256 <file> on macOS, certutil -hashfile <file> SHA256 on Windows.

Why might my hash differ from the publisher's?

Most commonly: incomplete download. Re-download and try again. Other causes: text-mode FTP/HTTP transfer changed line endings (rare today); zip/tar tools sometimes hash the unpacked content rather than the archive.

Can I hash multiple files?

One at a time, currently. For batch operations, the command line is faster: sha256sum *.iso or find . -type f -exec sha256sum {} +.