SHA-256 and SHA-512 checksum
Check that a download arrived intact: drop the file, paste the checksum from the website, and see if they match.
Check that a download arrived intact: drop the file, paste the checksum from the website, and see if they match.
Does your download match the publisher’s copy? FluffyBench’s Hash Checksum compares their checksum with your local file’s fingerprint, without uploading the file.
Think of a checksum as a fingerprint made from a file’s contents. Compare the publisher’s fingerprint with one calculated from your download, using the same recipe (the hash algorithm).
Two paths to a checksum comparison
The publisher’s checksum must belong to the exact file version you downloaded.
SHA-256 and SHA-512 are different recipes; compare like with like.
A filename can stay the same when the contents change. The fingerprint comes from the contents.
Changing the text abb to abc changes just 1 input bit, yet nearly every character in its SHA-256 fingerprint changes. That’s why even a tiny edit can be easy to spot in a checksum comparison.
One changed input bit, two complete SHA-256 results
A bit is a single 0 or 1. The final bit of b changes to make c.
Red marks the 59 hexadecimal characters that differ, out of 64 in each result.
The checksum reveals a difference; it doesn't locate or repair the edit.
Here’s the file check in FluffyBench’s Hash Checksum, demonstrated with a sample photo and a checksum calculated from that same file.
These text demonstrations keep abc as the input and change the expected checksum. The verdict distinguishes a match, a difference and an unusable reference.
Checking a piece of text? Text mode hashes what you type as UTF-8, the byte representation of that text.