MD5 checksum

Use an MD5 checksum for accidental corruption, not trust

An MD5 checksum is a compact, 32-character fingerprint calculated from every byte in a file. Change one byte and the fingerprint normally changes completely. That makes MD5 useful when a download page, archive mirror, camera workflow, or older software project publishes an MD5 value and you need to know whether your copy arrived intact. Paste that published value above, choose the file on your device, and the comparison is performed for you. You should not have to compare two dense hexadecimal strings by eye.

The limit matters as much as the result. MD5 has practical collision attacks: a determined attacker can construct different inputs with the same checksum. A match is therefore evidence against an interrupted transfer, a damaged archive, or the wrong file version. It is not proof that nobody deliberately replaced the file. That warning remains next to the result even when the answer is Match because it is part of the meaning, not legal text to hide after the useful part.

How to check an MD5 checksum

Get the expected checksum from the source that supplied the file. It may be a bare value, a line such as d41d8cd98f00b204e9800998ecf8427e  filename, or a small MD5SUMS file containing one line per download. Paste it into the publisher field, then select the exact file you downloaded. The page reads the file and reports Match only when all 32 hexadecimal characters are equal. A missing character, a copied invisible character, or a SHA checksum of another length gets an explanation instead of a guess.

No match does not by itself mean malware. The common explanations are ordinary: the transfer ended early, a mirror contains a stale release, or the published checksum belongs to another platform build. Windows x64, ARM, and macOS packages have different bytes and therefore different checksums even when their version names look alike. Download the file again from the publisher, confirm that you selected the matching edition, and repeat the check before drawing a stronger conclusion.

Prefer SHA-256 when the publisher offers both

Some older projects list MD5 because existing scripts and package archives expect it. You do not need to reject that value when accidental corruption is the only question available to answer. But when the same page lists SHA-256, use the stronger value with the SHA256 checksum checker. SHA-256 has a longer 64-character output and is the appropriate default for security-conscious file verification. Keeping the two algorithms on separate pages prevents a green MD5 result from being presented as if it carried SHA-256’s security meaning.

A checksum also depends on where its expected value came from. If an attacker can replace a file and edit the checksum printed beside it, either algorithm will faithfully say those two attacker-controlled items agree. Obtain the expected value from the publisher’s own HTTPS page, signed release notes, or another channel you already trust. A forum comment or an unrelated mirror is weaker evidence even when its string is formatted correctly.

Large files are streamed instead of buffered

Browser cryptography does not expose MD5, so this page uses a small implementation of the algorithm defined in RFC 1321. More importantly, it is incremental. The browser reads a 256 KB slice, updates four words of hash state, releases that slice, and continues. A multi-gigabyte disk image does not have to fit in one JavaScript buffer. The progress bar counts bytes that have actually passed through the calculation rather than estimating a completion time.

The implementation is checked against RFC 1321’s published test vectors and against independent system implementations on binary data, including empty input, NUL bytes, and lengths around the internal 64-byte block boundary. Chunk sizes deliberately vary in the tests because a streaming hash that works only when reads happen to align with its blocks is not a streaming hash at all.

Your file stays in this browser tab

File bytes are read directly from the file handle your browser provides. They are not sent to an upload endpoint, stored in an account, or passed to a third-party script. That is both more private and more practical for large archives. You can verify the behavior yourself by opening the browser network panel before selecting a file; the local-processing walkthrough explains what to look for and how to repeat the check on any site making the same claim.

An MD5 value cannot be decrypted

MD5 is a hash, not encryption. There is no key and no reverse operation that recovers the original file from 32 characters. Sites that claim to decrypt common hashes usually search a database of values previously calculated from likely passwords; they do not reverse the algorithm. For files, the useful operation is comparison: calculate the fingerprint of the copy you possess and compare it with a value calculated from the source copy.