Practical guide
Calculate and Verify a File Checksum
By MultiZest · Updated
How to use this tool
- Select a file up to 100 MB and choose the hash algorithm used by the publisher.
- Paste the expected hexadecimal digest if you have one, or leave it blank to calculate only.
- Run the calculation and review Match, Mismatch or Hash calculated. Copy or download the report.
Worked example
A publisher supplies a 64-character SHA-256 digest. Choose SHA-256, paste that digest and select your download. A mismatch means the supplied digest and file bytes do not agree; check the reference, algorithm and download.
Use a trustworthy comparison value
A digest can detect accidental changes only relative to its reference. If a compromised source supplies both a malicious file and its hash, the two will still match. Obtain expected hashes through a source appropriate to the sensitivity of the download.
SHA-256 uses 64 hexadecimal characters, SHA-384 uses 96 and SHA-512 uses 128. Uppercase and lowercase hex are accepted. Algorithm names, filenames and checksum-file prefixes should not be included in the expected-digest field.
Browser memory and permissions
Hashing uses the browser Web Crypto API and requires HTTPS or localhost. The selected file is read into memory, with a 100 MB limit to reduce browser pressure. An empty file is valid and has a defined hash.
The tool does not scan for malware, verify a software publisher’s digital signature or upload the file. Closing the page discards the calculation unless you saved its report.
Get the reference from a source you trust
A checksum comparison is only as useful as its reference. If you download an archive from a publisher, obtain the expected digest through the publisher’s trusted release channel and choose the stated algorithm. A digest copied from an unrelated comment may describe a different version or an untrusted file.
Select the actual downloaded file rather than a renamed substitute or extracted folder. A ZIP archive, one file inside that ZIP and a later repackaged archive are different byte sequences. Their hashes need not match even when some of their visible content is similar.
Investigate a mismatch before assuming a cause
Check the version, filename, algorithm and completeness of the download. A partial transfer or an updated release can explain a mismatch, but do not invent an explanation merely to accept it. Obtain the correct reference or download the intended file again before relying on the result.
A matching digest confirms agreement with the supplied reference; it does not scan for malware or prove that the publisher is trustworthy. Keep ordinary security checks in the workflow, and avoid loading a very large file on a memory-limited device when a local command-line verifier would be more appropriate.
Questions and troubleshooting
Does a matching checksum prove a file is safe?
No. It establishes agreement with the supplied digest. The safety and authenticity of that reference still matter.
Why does SHA-256 reject my expected digest?
Enter exactly 64 hexadecimal characters, without the algorithm label, filename or checksum-file formatting.
Does a matching SHA-256 checksum mean the file is safe?
It means its bytes match the supplied SHA-256 reference. Trust in the reference and the file’s safety are separate questions. Obtain the digest from a trusted release source.
Continue with a related tool
Generate SHA-256, SHA-512, SHA-1, or MD5 hashes locally for text and checksum comparisons.
UUID v4 & v7 Generator →Generate up to 1,000 random UUIDv4 or time-ordered UUIDv7 identifiers using browser cryptographic randomness.
Base64 Converter →Encode strings and files to Base64 or decode Base64 back to original content.
More detailed guides
Sources and further reading
Found an error or an unclear instruction? Report it. Read our editorial policy and privacy policy.