MD5 digests, computed in your browser.
MD5 produces a 128-bit digest, written as 32 hexadecimal characters.
Enter some text above to see its MD5 digest.
From the maker of MakeUUID
What MD5 is good for, and what it is not.
MD5 is broken for anything security related. Practical collisions - two different inputs with the same digest - have been public since 2004 and can now be produced in seconds on a laptop, and chosen-prefix collisions make it possible to craft two meaningful files that hash identically. Never use MD5 for signatures, certificates, integrity checks against a hostile party, or password storage.
What MD5 is still fine for is work where nobody is trying to fool you: cache keys, sharding keys, deduplicating files in a pipeline you control, or spotting accidental corruption in a transfer. It is fast, it is short, and every language has it in the standard library, which is why it survives in so many codebases.
If you are checking a download against a published checksum, prefer the SHA-256 value when the project offers one. If you inherited MD5 in a protocol you cannot change, treat the digest as an identifier rather than as proof of anything.