Add your input
A local file or text, plus an optional expected checksum.
Code drawer
File checksum verifier
Confirm a download matches the checksum its publisher listed.
Privacy built inYour work stays with you
Checksum
Choose a file or enter text.
Your work stays private in your browser while you use this tool.
What does file checksum verifier do?
The file checksum verifier calculates a SHA-256, SHA-384, or SHA-512 digest of a local file or of text you paste, and compares it against a checksum you supply. Comparison ignores case and surrounding whitespace, because published checksums are written both ways. The file is read in the page and never uploaded.
- Input
- A local file or text, plus an optional expected checksum.
- Result
- The digest in lowercase hex and a match or mismatch verdict.
- Price
- Free
- Account
- Not required
How to use file checksum verifier
Choose your settings
Confirm a download matches the checksum its publisher listed.
Save or copy
The digest in lowercase hex and a match or mismatch verdict.
A practical tip
Paste the publisher's checksum to compare — case and stray spaces are ignored.
When to use file checksum verifier
Confirm a downloaded installer matches the checksum on the publisher's release page.
Check that a file copied between machines arrived without corruption.
Produce a digest to publish alongside a file you are distributing.
Worked example
A concrete file checksum verifier example
- Input
- Text 'abc' with SHA-256 selected
- Result
- ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad.
What to expect
How it works
The selected bytes are passed to the Web Crypto digest function and the result is rendered as lowercase hexadecimal. When an expected checksum is supplied, both values are lowercased and stripped of whitespace before comparison, so a checksum pasted from release notes matches regardless of formatting.
Know before using
Limits and edge cases
- The whole file is held in memory because the Web Crypto digest is not streaming, which is why an explicit size cap applies. Very large files may fail on memory-constrained devices.
- A matching checksum proves the bytes are the ones the checksum describes. It does not prove who produced them, so a checksum taken from the same page as the download is worth little on its own.
Standards and sources
Common questions
File checksum verifier FAQ
Is file checksum verifier free to use?
Yes. File checksum verifier is free to use.
Does file checksum verifier keep my work private?
Yes. Your work stays private while you use the tool — nothing you enter is uploaded.
Why are MD5 and SHA-1 not offered?
Both have practical collision attacks, meaning two different files can be made to share a digest. Offering them beside SHA-256 would imply they are comparable choices for verifying integrity, and they are not.
Does a matching checksum mean the file is safe?
It means the file is byte-for-byte what the checksum describes. If the checksum itself came from a compromised or untrusted source, a match confirms nothing useful, so take the expected value from a channel independent of the download.