Check your file. Keep it local.
Check a file’s SHA-256 checksum locally. Compare a publisher’s digest, process large files in chunks, and save a checksum without uploading your file.
Verify a download in three steps
- 01Get a trusted reference
Copy the SHA-256 value from the publisher’s authenticated download page. Select the checksum for the exact version and platform you downloaded.
- 02Choose and calculate
Select the downloaded file. A background worker reads it in 4 MiB chunks, so large files do not need one giant memory buffer. Keep this tab open until it finishes.
- 03Compare and keep a record
Paste the expected value and read the result. A filename in a checksum record is checked exactly. Copy your digest or download a .sha256 record for later use.
ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015adIntegrity is not publisher identity
Frequently Asked Questions
Does my file leave my device?
The file is read by a local browser worker. File contents, names and expected checksums are excluded from tool analytics. Nothing is saved by this tool after you clear it or close the tab.
Which checksum formats work?
Use a bare 64-character hexadecimal SHA-256 value, a GNU line with two spaces or a space and * before the filename, or SHA256 (filename) = digest. Uppercase hex is accepted. Lists and escaped filenames are not. Downloads use a bare digest for names containing control characters or backslashes.
Can I check large files?
Yes. The worker reads 4 MiB chunks and reports progress. Available storage access, browser support and device performance still matter. Cancel stops the worker and discards partial results; selecting another file clears the previous result.