How to use it
- Keep SHA-256 ticked (preselected here) and choose the files, or press Try a sample.
- Press Calculate checksums.
- Copy a value with its copy button, or press Download checksum file for SHA256SUMS.txt.
- To check a copy later, paste the value or drop the SHA256SUMS file with the file.
Worked example
The sample file abc.txt holds the three letters abc. Its SHA-256 is ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad, and the downloaded SHA256SUMS.txt holds that value, two spaces and abc.txt.
Formats and limits
| Input | Any files |
|---|---|
| Output | SHA-256 hashes, SHA256SUMS.txt |
| 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
- A checksum shows whether a file changed; it does not prove who made it.
- Very large files take time, since every byte is read.
- MD5 and SHA-1 are offered too, but they are not safe against deliberate tampering.
Questions
What is in the SHA256SUMS.txt file?
One line per file: the 64-character SHA-256 value, two spaces and the file name. That is the layout that sha256sum -c on Linux and this tool read back.
Can I add MD5 or SHA-512 as well?
Yes. Tick more algorithms and each file gets every hash. With more than one algorithm ticked, the download is named CHECKSUMS.txt.
How do I verify a file against a checksum later?
Paste the expected value, or drop the SHA256SUMS file, together with the file. Each file then shows whether it matches.
Are my files uploaded?
No. The files are hashed in your browser and nothing is uploaded.
Privacy
Runs on your device. Files and text are processed in this browser tab and are not uploaded.
This page opens the File checksum verifier ready for this task. See the privacy policy for how toolsdocks handles data.