Choose an exact-content question
Select files when you want to compare their bytes, not their visual similarity. Different metadata or encodings can make two apparently identical pictures produce different hashes. Up to 50 files fit in one batch, limited to 100 MB each and 500 MB total. The worker reads one-megabyte chunks and can be cancelled.
Verify a single download independently
To check a published checksum, select exactly one file and paste the 64 hexadecimal SHA-256 characters from a trusted source. Uppercase or lowercase is accepted. A mismatch means the bytes do not match that checksum; it does not diagnose why. Check that you selected the correct release, platform and file before downloading again.
Read duplicate groups carefully
Files with equal size and SHA-256 receive the same duplicate group. Different names are retained so you can identify the copies. This is a practical cryptographic-content comparison rather than a mathematical proof or a perceptual search. The tool never chooses which copy is authoritative and never deletes or renames anything.
Keep a report with the right privacy expectations
CSV and JSON include file names, byte sizes, hashes and group numbers. CSV protects formula-like names; JSON retains names exactly. A report can reveal private project or document names even without file contents, so share it deliberately. Empty files are valid and share the standard SHA-256 for empty content.
Do not confuse integrity with safety
A matching hash is not an antivirus result or a signature identifying a publisher. Obtain the expected checksum through a trustworthy channel. If a large batch reaches the 30-second limit, retry fewer files; the tool does not return a partial report as success. Save the report before clearing or leaving this local workspace.