How a Checksum Spots a Changed File
A computer file is a sequence of bytes: small numeric values that encode everything from text to video. A checksum algorithm processes those bytes and produces a much shorter value. That value is stored or sent alongside the file so it can be calculated again later.
After a transfer, the receiving computer runs the same calculation on its copy. If even one byte changed, the new checksum will usually differ from the original. The comparison gives the computer a quick warning that something went wrong, without requiring it to compare the files byte by byte.
A Detector, Not a Repair Tool
A checksum can flag corruption, but it does not identify which byte changed or restore the missing data. The file must be transferred or retrieved again, unless another system has a separate way to repair it.
Checksums also compress a large amount of data into a smaller value, so different files can sometimes produce the same checksum. For routine transmission errors, well-designed checksums make accidental changes detectable with high probability. They are not proof that two files are identical, and a basic checksum is not designed to establish who sent a file or protect against deliberate tampering.
That is why a checksum is best understood as a quick integrity check: it can tell a receiving computer when a copy deserves suspicion, before the damaged file is opened or used.
