How to use
- Choose a file and the algorithms you need.
- Paste the expected hash, or drop the publisher's checksum file.
- The result shows Match or Mismatch for each file.
Worked example
The SHA-256 of the three-byte text “abc” is ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad.
Supported formats and limits
| Input | Any file, Optional .sha256 / .md5 / SHA256SUMS file |
|---|---|
| Output | Hashes, Match / mismatch result |
| Limits | No size limit beyond your device; files are read in 4 MB chunks. |
| Engine | Streaming hashing with hash-wasm in a Web Worker |
Limitations
- MD5 and SHA-1 detect accidental corruption but are not safe against deliberate tampering.
Questions
What does a matching checksum prove?
That your file is identical to the one the expected hash was made from. It does not prove that file is safe or genuine; that depends on getting the expected hash from a source you trust, such as the publisher's own site.
Which algorithm should I compare?
Whichever the publisher lists. Paste the hash and its algorithm is detected from its length; SHA-256 or SHA-512 are preferable to MD5 and SHA-1, which are no longer collision-resistant.
Guides
Privacy
Runs on your device. Files and text are processed in this browser tab and are not uploaded.
See the privacy policy for how toolsdocks handles data.