File integrity
SHA-256 of multiple files.
Hash a batch of files or a whole folder, download a sums.txt in sha256sum format, check files against a manifest you were given, or compare two manifests to see what changed. Files stay on your device.
Hash many files at once and keep a manifest
A checksum is a fingerprint of a file's exact bytes: change one bit and the SHA-256 changes completely. Checking one download against one published hash is easy; checking a folder of 200 files, or proving that a backup still matches the original, needs a manifest, a text file with one hash and one file name per line. This page builds that manifest in your browser, checks files against a manifest somebody else gave you, and compares two manifests to show what was added, removed or changed. Files are read on your device and never uploaded.
Three jobs in one page
- Create. Choose files, or a folder to keep relative paths, pick SHA-256 (the default), SHA-512, SHA-384, SHA-1 or MD5, and press Run. You get a table and a
sums.txtyou can download or copy. - Verify. Paste a manifest you received, such as the
SHA256SUMSfile that comes with a software release, choose the files, and press Run. Each line shows OK, FAILED or Missing, and files you chose that the manifest does not list are reported too. The result mirrorssha256sum -c. - Compare. Paste an old and a new manifest into A and B. The tool lists identical, changed, removed and added files, for example to check what a backup, a deployment or a vendor update altered.
The manifest format
The output is the GNU coreutils format: the hash in lower-case hex, two spaces, then the file name, one file per line with LF line endings. For example:
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 empty.txt
ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad docs/abc.txt
Those two values are the well-known SHA-256 test values for an empty input and for the three bytes abc, so you can confirm any tool against them. The parser also accepts a * before the name (binary mode), Windows backslashes, lines that start with #, and the BSD form SHA256 (name) = hash that BSD-style tools print. The algorithm is read from the hash length: 32 hex digits for MD5, 40 for SHA-1, 64 for SHA-256, 96 for SHA-384 and 128 for SHA-512.
Worked example: verifying a release
You download three files from a project plus its SHA256SUMS. Paste the contents of SHA256SUMS into the verify box, choose the three files and press Run. Two lines say OK and one says FAILED with the expected and actual values side by side. The FAILED file is a truncated download, so download it again. Had it said Missing instead, the manifest names a file you did not select, or the downloaded file was renamed, for example tool (1).zip. Names are matched exactly first and by base name if that is unambiguous.
Choosing an algorithm
- SHA-256 is the usual choice and what most projects publish.
- SHA-512 and SHA-384 are fine where a publisher uses them.
- SHA-1 and MD5 are cryptographically broken: collisions can be constructed deliberately (see RFC 6151 for MD5). They still detect accidental corruption and some older sites publish only them, so they are offered, but do not rely on them to detect tampering.
Common mistakes
- Trusting a hash that came from the same place as the file. Whoever can replace the file can replace the hash. Prefer a hash from a separate channel or a signed one.
- Comparing different algorithms. A 40-digit value is SHA-1 and will never match a SHA-256. The tool reads the algorithm from the length and tells you if two manifests disagree.
- Hashing an archive and expecting the contents to match. The hash of a ZIP is not the hash of the files inside it.
- Choosing files separately and losing paths. Pick the folder instead so names such as
docs/abc.txtare recorded; flat file selections record only the file name. - Line-ending changes. Opening a text file in an editor that rewrites line endings changes its hash. Compare the original bytes.
Limits and what it does not do
- Each file is read into memory to hash it, because the browser's Web Crypto digest works on a whole buffer. The limits are 128 MB per file, 1 GB hashed per run and 500 files per run; files over 128 MB are refused and the rest are skipped and reported. The file is read in 8 MB slices into one buffer, and the Cancel button stops a run between slices.
- It reports only whether bytes match. A matching hash does not prove a file is safe, and the tool does not check any list of known-bad or known-good hashes.
- It does not hash directories' metadata (permissions, timestamps) and does not walk hidden system folders the browser omits.
- SHA algorithms use the browser's built-in Web Crypto. MD5, which Web Crypto does not provide, is computed by a small routine in the page, tested against reference values.
Your files never leave the browser
The tool runs in an isolated frame with no network permission and no advertising or analytics code. Files are read from your disk by your browser and hashed locally; manifests you paste stay in the page. The sums.txt is created in memory and saved by your browser. The ads on this page sit outside the frame and cannot see your files or manifests.
Common mix-ups
-
Often assumedA 40-character hash and a 64-character hash are the same checksum in two lengths.
What the source saysThey come from different algorithms. FIPS 180-4 defines SHA-1 (160-bit digest, 40 hex digits) and SHA-256 (256-bit digest, 64 hex digits) separately, so one can never match the other for the same file. [1]
-
Often assumedMD5 is fine for any file check, including proving a download was not tampered with.
What the source saysRFC 6151 says MD5 is no longer acceptable where collision resistance is required. It still catches accidental corruption, but for tamper checks use SHA-256 and get the expected hash from a separate trusted channel. [2]
- NIST FIPS 180-4: Secure Hash Standard (SHA-1 and SHA-2)
- RFC 6151: Updated Security Considerations for the MD5 Message-Digest Algorithm
Checked against these sources on .
Frequently asked questions
How do I get the SHA-256 of multiple files at once?
Choose several files, or a whole folder, in this tool and press Run. It shows a SHA-256 for each file and builds a sums.txt you can download. Everything happens in your browser.
How do I verify files against a SHA256SUMS file?
Paste the contents of the SHA256SUMS file into the verify box, choose the files and press Run. Each line is reported as OK, FAILED or Missing, the same results sha256sum -c would give.
What format is the sums.txt?
The GNU coreutils format: the lower-case hex hash, two spaces, the file name, one per line with LF line endings. sha256sum -c sums.txt on Linux or shasum -a 256 -c sums.txt on macOS can check it.
How do I compare two manifests?
Paste the older manifest into A and the newer into B and press Run. The tool lists files that are identical, changed, only in A (removed) and only in B (added), matching by file name.
Is it safe to use MD5 or SHA-1?
They detect accidental corruption but are broken against deliberate tampering, because collisions can be created. Use SHA-256 or SHA-512 whenever you have a choice.
Does a matching hash mean the file is safe?
No. It means the file is byte-identical to what was hashed. If the hash itself came from an untrustworthy source, or the original file was malicious, a match proves nothing about safety. The tool does not check known-bad lists.
What are the size limits?
128 MB per file, 1 GB hashed per run and 500 files per run, because each file is read into memory for the browser’s Web Crypto digest. Files over 128 MB are refused, extra files are ignored, and anything over the budget is skipped and reported. You can cancel a run at any time.
Are my files or manifests uploaded?
No. Files are hashed locally inside a frame with no network access and no ad or analytics code. Manifests you paste stay in the page.
Sources
Sources last checked 2026-11-11.
- Secure Hash Standard, NIST FIPS 180-4: csrc.nist.gov/pubs/fips/180-4/upd1/final (SHA-1 and SHA-2 definitions and test values).
- The MD5 Message-Digest Algorithm, RFC 1321: www.rfc-editor.org/rfc/rfc1321 (MD5 definition).
- Updated Security Considerations for MD5, RFC 6151: www.rfc-editor.org/rfc/rfc6151 (MD5 collision weaknesses).
- sha256sum manual page, Linux man-pages: man7.org/linux/man-pages/man1/sha256sum.1.html (check-file format and options).
- SubtleCrypto.digest(), MDN: developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/digest (browser hashing on a whole buffer).