Warning: MD5 is cryptographically broken. Collisions can be produced in seconds on ordinary hardware, so MD5 must never be used to hash passwords, sign data, or verify that a file has not been tampered with by an attacker. Use it only for legacy checksums, cache keys, deduplication and similar non-security work.
MD5 turns any input into a fixed 128-bit value, written as 32 hexadecimal characters. This generator encodes your text as UTF-8 first, so accented letters, non-Latin scripts and emoji all produce the same hash you would get from a command line tool or a server-side library. The result updates as you type, and the classic test vector still holds: the text abc hashes to 900150983cd24fb0d6963f7d28e17f72.
A second hash is shown for the same text with leading and trailing whitespace removed. That catches the single most common reason two people compare MD5 values and get different answers: a stray newline or space picked up when pasting. Everything runs in your browser with a JavaScript implementation of RFC 1321, because the Web Crypto API deliberately does not offer MD5.
How to use the MD5 Generator
- Paste or type your text into the input box.
- Read the 32-character hash below, which updates on every keystroke.
- Tick uppercase output if the system you are matching expects capital letters.
- Keep the trimmed hash visible to check whether stray whitespace is causing a mismatch, then press Copy.
Frequently asked questions
Is MD5 safe for passwords?
No. MD5 is fast and broken, and password databases hashed with it are cracked in bulk. Use a purpose-built password hash such as Argon2id, scrypt or bcrypt. MD5 is acceptable only for non-security work like checksums against accidental corruption, cache keys and deduplication.
Can an MD5 hash be reversed?
Not directly, because hashing discards information. In practice short or common inputs are recovered instantly from precomputed rainbow tables and public lookup databases. Treat any MD5 of a short string as effectively public, and never assume it hides the original value.
Why do I get a different hash than another tool?
Almost always whitespace or encoding. A trailing newline changes the hash completely, which is why the trimmed result is shown alongside. Character encoding matters too: this tool uses UTF-8, so a tool working in Latin-1 will differ on any non-ASCII character.
What is an MD5 collision?
Two different inputs producing the same hash. For MD5 these can be constructed in seconds on a laptop, and chosen-prefix collisions allow two meaningful files to share one hash. That is why MD5 cannot prove a file was not deliberately altered, though it still catches random transmission errors.