File Verifier

A checksum is a fixed-length digest calculated from a file's bytes. Renaming the file does not affect it, and changing the contents will usually produce a different value. A digest is not a unique file ID, so matching checksums alone cannot prove that two files are identical.

Downloads can fail partway, become corrupted during transfer, or be modified. A SHA-256 match against a digest obtained from a trusted source is strong evidence that the file arrived unchanged, but it is not absolute proof of identity or authenticity.

Drop your file on this page. We calculate its hashes instantly. Click “Paste hash” and paste an expected value from a trusted source. The tool autodetects the algorithm, shows match or mismatch, and highlights exactly where the digests diverge.

Your file may be corrupted or modified. When you paste an expected hash, diverging characters are highlighted so you can see exactly where they differ. Delete the file and download again from the original source. If it still doesn't match after a fresh download, contact whoever provided the file.

Yes. After dropping your first file, click “Compare file” and drop a second one. The tool calculates all four hashes for both files and shows a match or mismatch for each algorithm. A SHA-256 match is strong evidence that the contents are the same, but a hash match is not mathematical proof of file identity.

Use SHA-256 with an expected digest from a trusted source for integrity or security checks. SHA-512 is also suitable when the source provides it. MD5 and SHA-1 are included only for nonsecurity compatibility checks and must not be used to establish authenticity.

Yes. A hash has a fixed number of possible values, so different files can share the same digest. An accidental SHA-256 collision is extraordinarily unlikely, but MD5 and SHA-1 have known collision attacks and are not safe for security checks.

Sign in to your Digiwava account, then drop a ZIP file. We compare its SHA-256 digest with Digiwava's package records. A match is strong evidence that the contents match the recorded package, and you'll see the product details. If the seller has released a newer version, we note that too. Hash calculation works without signing in; package matching requires an account.

No. Your file stays on your device and all calculations happen in your browser. For ZIP files, signed-in users have the computed checksum sent to Digiwava to check for a matching product (see the “Verified package” question). When you close the tab, nothing remains.