File Checksum Calculator
Software publishers print a checksum next to each download so you can confirm the file you received is the file they built. Comparing by eye is error-prone; this page does it for you.
- The file is read with the File API in 4 MB slices and fed to a streaming hasher compiled to WebAssembly. Memory use stays flat whether the file is 1 MB or 8 GB.
- Tick the algorithms you need. SHA-256 is what most projects publish today; MD5 and SHA-1 still appear on older download pages.
- Paste the expected checksum. Spaces, dashes and case are ignored, and the result says which algorithm matched.
A matching SHA-256 proves the bytes are identical to what the publisher hashed. It does not prove the publisher is trustworthy, and a matching MD5 only rules out accidental corruption, since an attacker could craft a collision. Prefer signed checksums (GPG or Sigstore) where available.
What leaves your browser
The file is read locally and never uploaded. No request leaves the page during hashing. Hashword has no server-side file handling at all.
How large a file can I check?
As large as your browser can read from disk. Multi-gigabyte ISOs work; only 4 MB is in memory at a time.
The checksum does not match. Is the file dangerous?
It is different from what the publisher hashed. Most often the download was interrupted or you compared the wrong algorithm. Re-download from the official source and check again before running anything.
Which is better, SHA-256 or MD5 for checksums?
SHA-256. MD5 collisions can be crafted deliberately, so a malicious file can carry a valid MD5. SHA-256 has no such weakness.
How do I get checksums on the command line?
sha256sum file on Linux, shasum -a 256 file on macOS, Get-FileHash file in PowerShell. This page gives the same output without a terminal.