Good uses
Compare software releases, ISO images, firmware, exported backups, archives, or files transferred between machines against a separately published SHA-256 digest.
Tools · Privacy-first
SHA-256 File Verifier
Calculate the SHA-256 digest of any local file and optionally compare it with a value published by the file’s author. Use it to check downloads, release artifacts, backups, disk images, or any situation where you need to confirm that two byte-for-byte files are identical.
A matching digest proves that the selected file has the same bytes as the source of the expected hash. It does not prove who published the file or that the expected hash itself came from a trusted source.
Runs locally
Your file stays in this browser.
Local input: one file and an optional expected SHA-256 digest. Network effect: none.
Local file4 MiB worker chunksSHA-256 digest
Hashing runs in a separate browser worker with progress and cancellation. File bytes, names, and expected hashes are not added to the URL, browser storage, or site analytics.
Local input
Select and verify a file
Choose a file to verify
Drop a file here or open the local file picker. Nothing is uploaded.
File name
Size
Type
Last modified
Optional: paste a 64-character hexadecimal SHA-256 digest.
0%0 B / 0 B
Select any file. Hashing starts only after you press “Calculate SHA-256”.
Verification result
Calculated file digest
Comparison
Does it match?
Add an expected digest to compare locally.
Always obtain the expected hash through a channel you trust. A checksum copied from the same compromised download location may provide no independent assurance.
Purpose and limits
Verify exact bytes, then verify the source
What a match proves
A match means the selected file and the expected digest describe the same byte sequence with extremely high confidence. Even a one-bit change produces a different digest.
What it does not prove
SHA-256 is not a digital signature. A match does not identify the publisher, validate a release signature, scan for malware, or make untrusted software safe to run.
Large files
The worker reads slices of up to 4 MiB and keeps hashing off the main interface. Processing time still depends on file size, storage speed, browser, and device performance.
Expected hash format
Paste exactly 64 hexadecimal characters. Uppercase is accepted, whitespace is ignored, and an optional sha256: prefix is removed before comparison.
Privacy boundary
The browser grants this page access only to the file you select. The page processes its bytes locally and provides no upload or server-query path.