Developer
Encoders, converters & dev utilities
MD5 Hash Generator
Generate the MD5 hash of any text or file. MD5 (RFC 1321) is a 128-bit digest, printed as 32 lowercase hex characters, that maps any input to a fixed-length fingerprint. It is still widely used as a fast, non-security checksum — verifying that a download or a copy arrived intact — but it is cryptographically broken: practical collisions exist, so MD5 must never be used for security, signatures, or password storage. Worked example: MD5 of the empty string "" is d41d8cd98f00b204e9800998ecf8427e, and MD5("abc") is 900150983cd24fb0d6963f7d28e17f72. Hashing runs 100% in your browser, so your input never leaves the page. Free, no login.
MD5 (RFC 1321) = a 128-bit digest → 32 lowercase hex characters; one-way, fixed length
- Byte-exact test vector: MD5("") = d41d8cd98f00b204e9800998ecf8427e
- Byte-exact test vector: MD5("abc") = 900150983cd24fb0d6963f7d28e17f72
- BROKEN for security: practical collisions exist — use MD5 only as a non-security checksum
- Hashing is one-way and not encryption; runs 100% client-side, your input is never uploaded
Frequently asked questions
How do I generate an MD5 hash?
Paste text or drop a file and the tool computes its MD5 digest — a 128-bit value shown as 32 hex characters. For example MD5 of the empty string is d41d8cd98f00b204e9800998ecf8427e and MD5("abc") is 900150983cd24fb0d6963f7d28e17f72. The hashing happens entirely in your browser, so nothing you enter is uploaded to a server.
Is MD5 secure?
No. MD5 is cryptographically broken: attackers can construct two different inputs with the same MD5 hash (a collision) cheaply, so it must not be used for digital signatures, certificates, integrity against a malicious party, or anything security-sensitive. It is still fine as a fast checksum for detecting accidental corruption (a bad download, a flipped bit). For security use SHA-256 or stronger, and for passwords use bcrypt, scrypt, or argon2.
Can I reverse an MD5 hash back to the original text?
No — MD5 is a one-way function, not encryption, so there is no key that turns the digest back into the input. What attackers do instead is guess: for short or common inputs a hash can be looked up in precomputed tables (rainbow tables) or brute-forced, which is exactly why MD5 (and any fast hash) is unsuitable for passwords. A hash proves you have the same input, it does not store it recoverably.