Generate an MD5 checksum from text and copy its 32 digit hexadecimal value. Use it for legacy comparisons, not password protection.
How to use
Enter the exact text and generate the digest. Compare only with a checksum made from the same text encoding and line endings.
Example
hello produces 5d41402abc4b2a76b9719d911017c592. Hello produces a different digest because the capital letter changes the input.
FAQ
Is MD5 encryption?
No. MD5 is a hash function with known collision weaknesses. It cannot establish authenticity against an attacker and is unsuitable for secure password storage.
IETF: MD5 security considerations
A practical task
Use MD5 only where a legacy workflow explicitly requires its format. Matching a published checksum can help detect accidental changes, but it does not prove that a file came from a trusted sender. The trust of the source and the digest's collision weaknesses are separate concerns.
Another useful question
Can the original text be recovered from a hash?
The digest does not contain a reversible encrypted copy. Simple or common inputs can still be guessed and tested, which is another reason not to use plain MD5 for passwords.
Details for interpreting the result
| Detail | Explanation |
|---|---|
| Hash digests | A digest summarizes exact input bytes into a fixed length value. It is not a compressed copy that can be restored. A different digest proves a difference in input, while the security meaning of a match depends on the algorithm and threat model. |
| Collisions | A collision means different inputs share a digest. Every fixed size hash has possible collisions, but practical resistance differs. MD5 has known weaknesses, so matching MD5 values cannot establish authenticity against an attacker. |
| UTF8 bytes | UTF8 encodes characters as bytes. Basic Latin letters use one byte each, while many accented letters and other scripts use more. A byte count therefore differs from a visible character count. |
| Line endings | A line break can use LF or CRLF. They look similar in an editor but contain different characters. Byte comparisons and checksums depend on the exact representation, including a final line break. |
| Similar looking text | Two strings can look identical but use different Unicode sequences. An accented letter can be stored directly or as a letter plus an accent. Visual similarity alone does not establish byte equality. |
| Encoding and encryption | Encoding changes how data is represented so another system can read it. It does not require a secret key. Encryption protects information with a key, while hashing produces a digest for a different purpose. |
| A complete byte | A byte holds a value from 0 through 255. Binary writes that value with eight digits; hexadecimal writes it with two. Leading zeros are part of that fixed width representation and must stay in place. |
