Compute the MD5 hash of text
MD5 is known to have collision vulnerabilities and isn't recommended for security-sensitive uses like password storage — it's best suited for general purposes like file verification and deduplication. All computation happens locally in your browser; nothing is uploaded.
MD5 is a hash algorithm that condenses data of any length into a 128-bit digest, usually written as a 32-character hexadecimal string. This tool has two modes. In 'Text' mode you type some text and get its MD5 immediately. In 'File' mode you pick any file and get the MD5 of its entire contents. Typical uses are checking that a download wasn't corrupted or swapped, and creating a quick fingerprint for de-duplication. One thing should be clear up front: MD5 has well-known collision weaknesses, so it must not be used to store passwords or sign anything security-sensitive, and the page itself carries the same warning. Hashing is also one-way, so this tool can compute an MD5 but cannot turn one back into the original text.
The MD5 of 'hello' is 5d41402abc4b2a76b9719d911017c592. Capitalise the first letter to get 'Hello' and the digest is completely different: 8b1a9953c4611296a827abf8c47804d7. Changing one character changes the whole result. Non-English text works as well: the MD5 of the Chinese text 你好 is 7eca689f0d3389d9dea66ae112e5cfd7. All three values were cross-checked against Node.js's built-in MD5 and matched the algorithm used on this page.
No. MD5 is extremely fast to compute, practical collision attacks exist, and large lookup tables make common passwords easy to reverse. Passwords should be stored with a deliberately slow, salted algorithm such as bcrypt, scrypt or Argon2.
Strictly speaking, no. A hash is one-way and the original information is discarded. Websites that offer 'MD5 decryption' are really looking your hash up in a table of precomputed common strings. This tool only goes forward: it computes hashes and does no lookups.
First make sure you used the right mode. To verify a download you need 'File' mode with the file itself, not text mode with the file name pasted in. Then check that the download is complete and is the version the checksum belongs to. For text, look for stray trailing spaces or newlines and for CRLF versus LF line endings. Invisible characters change the digest.
Usually it is the character encoding or the line endings. This tool encodes text as UTF-8. If the other tool uses a different encoding for Chinese, such as GBK, the bytes and therefore the digest differ. Plain English letters and digits have the same bytes in common encodings, so those rarely disagree.
In non-adversarial settings, yes: detecting accidental corruption during a transfer, generating a short fingerprint for de-duplication, or matching a checksum that an older system still publishes as MD5. Whenever you need to guard against someone deliberately tampering with data, use SHA-256 or something newer.
The MD5 is computed locally by JavaScript in your browser. Neither text nor files are uploaded or stored, and the code makes no network requests. A selected file is only read into memory for the calculation and is released when you close or reload the page.