128-bit · broken for security · still common
Computes the MD5 message digest (128 bits / 16 bytes) from any text input. NOT cryptographically secure — collisions are trivial. Still used for legacy checksums and file integrity. Pure JavaScript, client-side only.
Input text box — the MD5 digest appears instantly in the MD5 hash display.Copy hash to copy the 32-character hex digest to your clipboard.Uppercase hex to switch the digest between lowercase and uppercase letters.Show Base64 too to also see the 16-byte digest rendered as Base64.Clear to reset the input and start over.Older release pages and mirrors publish MD5 checksums. Recompute a file's digest locally to confirm it downloaded intact.
MD5 gives a stable 128-bit tag for any input — handy for comparing, bucketing, or looking up records when security isn't a concern.
Many APIs, caches, and databases still key on MD5. Generate matching hashes to integrate with or migrate off them.
Reproduce MD5 output to trace legacy auth, session, or checksum logic and confirm a routine produces the expected digest.
Produce stable, near-unique keys for test fixtures, filenames, and internal tools from arbitrary input.
Hashing runs entirely in your browser. Nothing is uploaded, logged, or sent to a server — safe for local files and sensitive strings.
MD5 is a hashing algorithm defined in RFC 1321. It maps any input to a fixed 128-bit (16-byte) digest, usually shown as 32 lowercase hex characters.
No. MD5 has been cryptographically broken since 2004, and collisions can be generated in seconds. Never use it for passwords, signatures, or any security purpose — use SHA-256 or better.
Non-cryptographic uses: legacy file checksums, quick fingerprints, deduplication, and deterministic IDs. It's fine when an attacker isn't a threat, but not for protecting against tampering.
Because 128 bits equals 16 bytes, and each byte is written as two hex digits — so the digest is always exactly 32 hex characters, no matter the input size.
It renders the same 16-byte digest in Base64 instead of hex — a shorter, 24-character string ending in == that's handy when space matters.
Yes. MD5 has an avalanche effect: even a single changed bit produces a completely different digest, so you can't predict the change from the output.
Never. All hashing happens locally in JavaScript. Your input is not sent to, stored on, or logged by any server.