File Checksum (SHA-256)
Software sites often publish a SHA-256 checksum next to a download. Choose the file here, paste the published value, and you will see straight away whether they match. The file is read locally and never uploaded. MD5 is not offered because browsers do not include it and it is no longer safe for verification.
Runs entirely in your browser. Your input and files are not uploaded to any server.
How to use
- Choose or drop a file (up to 1 GB).
- Wait for the checksums to be calculated.
- Paste the expected hash to compare it automatically.
Examples
Paste the SHA-256 from the vendor’s download page; a green match means the file is intact.
Hash both files and compare the SHA-256 values.
Privacy
Runs entirely in your browser. Your input and files are not uploaded to any server. See the privacy policy for what is stored in your browser (favorites and history only). Privacy policy
Check it yourself: open your browser’s developer tools, select the Network tab and use the tool. Your file never appears in an upload request. Once this page is saved for offline use, you can also disconnect from the internet and keep working. Ads and anonymous visit statistics, when enabled, make their own requests, but they never receive your files or text.
Frequently asked questions
Why is there no MD5?
The Web Crypto API in browsers does not implement MD5, and MD5 collisions are easy to create, so it cannot prove a file was not tampered with.
Is the file uploaded?
No. It is read into memory in this tab and hashed with crypto.subtle.
Why the 1 GB limit?
The browser hashing API needs the whole file in memory at once. Larger files may crash the tab on phones.