Match an older download list
Use MD5 only when the release actually supplies an MD5 reference. Do not compare it with SHA256.
Legacy compatibility · Text
Calculate MD5 from UTF-8, Hex or Base64 text. Compare a trusted expected digest locally.
MD5 calculated
0 decoded bytes · UTF-8 · input changes update automatically
Browser-local hashing. Inputs masked in Clarity.
No account. No uploads. Just your browser.
| Algorithm | What differs |
|---|---|
| MD5 | 128-bit legacy digest; broken collision resistance. |
| SHA256 | 256-bit SHA-2 digest; use for new integrity workflows with a trusted reference. |
Start empty, paste UTF-8 text, or choose Hex or Base64 for encoded bytes.
MD5 returns 32 lowercase hex characters. Copy digest preserves the whole output.
Paste a trusted reference, or enable HMAC only for a keyed protocol.
Use MD5 only when the release actually supplies an MD5 reference. Do not compare it with SHA256.
Hash the exact bytes expected by that system. A successful reproduction does not make MD5 collision-resistant.
Publish a modern checksum alongside legacy MD5 when compatibility requires both.
MD5 produces a 128-bit result: 32 hexadecimal characters. Use it to compare legacy checksum lists, not to authenticate a download or store passwords. MD5 has known collisions, so a matching digest does not establish authenticity.
A typical .md5 list contains a digest, two spaces, and the exact filename. Select MD5 before reading that list. SHA256 and MD5 values cannot be compared to each other.
Type or paste text for an automatic result. UTF-8 preserves whitespace and line endings. Hex accepts pairs of digits with optional whitespace; Base64 requires the standard padded alphabet. Invalid encoding stops calculation instead of hashing a different input.
The default result is the digest of zero bytes. The abc example contains exactly 61 62 63 in hex with no newline. Adding Enter changes the bytes and therefore the result.
Paste a complete hexadecimal expected value to see Match or Mismatch. Outer whitespace and uppercase hex are accepted; incomplete digests, filenames and embedded spaces are not.
HMAC-MD5 calculates a keyed hash. Enable HMAC and enter the secret in its own encoding. An empty key is a valid key and differs from turning HMAC off. Keys are never saved or included in exported reports.
The MD5 file checksum tool reads raw bytes in chunks and supports batch manifests. Text mode is limited to 8 MiB decoded input; use file mode for larger data.
No input is uploaded. Only a light/dark theme preference is stored. Copy and report downloads remain on your device.
MD5 · 0 bytes · no HMAC. Empty input is not the same as no file selected.
d41d8cd98f00b204e9800998ecf8427eNo. MD5 generates a 128-bit fingerprint; it does not encrypt text or provide a decrypt operation.
Each hexadecimal character represents four bits. A 128-bit MD5 digest is therefore 32 hex characters, including leading zeroes.
Yes. Practical collision attacks are why MD5 is unsuitable for signatures or new security designs. Matching MD5 values do not establish unique content.
No. HMAC-MD5 combines a secret key and the message through the HMAC construction. Use it only when an existing protocol specifically requires it; a plain MD5 reference will not match.
UTF-8 hashes literal text. Hex and standard padded Base64 decode to bytes first. abc, Hex 616263 and Base64 YWJj represent the same bytes; invalid encodings stop calculation.
Yes. Text is not trimmed. A trailing newline, carriage return, byte-order mark or extra space changes the byte sequence and usually the result.
Paste exactly 32 hexadecimal characters. Uppercase and outer whitespace are accepted. Match means equality with your reference, not proof of a trustworthy source.
Text and keys stay in browser memory, not URLs or localStorage. The tool saves only your theme preference; Clarity may use its own identifiers, as explained in Privacy. Text mode accepts up to 8 MiB of decoded bytes; use file mode for larger inputs.