Generate MD5 digests from text or uploaded files: 128 bits, 32 hexadecimal characters. MD5 is cryptographically broken and is for legacy use only.
Runs in your browser — your input is processed on this device and never uploaded.
Pasted text up to 100 MiB, read as UTF-8, or files up to 2 GiB each.
Results appear here.
MD5 produces 128 bits for any input: 16 raw bytes, or 32 hexadecimal characters. It is cryptographically broken, but decades of software still emit MD5 values, and reproducing one from such a system is a legitimate reason to compute it.
MD5 is cryptographically broken. Collisions can be produced on demand, which means two different inputs can be made to share a digest deliberately and cheaply.
It survives because it is embedded in decades of software. Legacy file formats, old database columns, package metadata and internal deduplication schemes all still emit MD5. Reproducing a value from such a system is the use this tool is for.
For any new cryptographic fingerprint, use BLAKE3, SHA-256 or SHA3. All are unbroken and none are meaningfully harder to use.
If the goal is detecting accidental corruption rather than resisting an attacker, CRC-32 and Adler-32 are faster and honest about being non-cryptographic. For passwords, Argon2id Hash Generator is the only appropriate option here.
The distinction that matters: a matching MD5 can still tell you a file survived a transfer intact, because random corruption will not accidentally land on a colliding value. What it cannot do is tell you nobody changed the file on purpose.
Warning
MD5 must not be used for passwords, digital signatures, certificates, authentication, or integrity against deliberate modification. Treating a matching digest as proof of trustworthiness is the mistake its brokenness enables.
Find similar tools by category or tag.