This tool hashes the input text as UTF-8 and returns a 128-bit MD5 digest as 32 hexadecimal characters. Use it for checksums, test fixtures or legacy systems that still expect MD5. If results differ, first compare the actual input, including letter case, spaces, encoding and line endings. The examples below let you check abc, a trailing LF newline and the Chinese text 中文 separately.
MD5 is deterministic and one-way, but it is not collision resistant enough for security workflows. Do not use it for passwords, signatures, or tamper protection; choose a modern hash or password hashing scheme instead.
Common questions and answers about this topic.
MD5 is a 128-bit hash function that produces a 32-character hexadecimal string. It is commonly used for checksums and data integrity verification.
MD5 is no longer considered secure for password hashing or cryptographic purposes. Use SHA-256 for non-password integrity checks and a password hashing algorithm such as bcrypt, scrypt, or Argon2 for password storage.
No, hash functions are one-way. You cannot derive the original input from the hash.
No, MD5 hashing is computed entirely in your browser. Your input text is processed locally with JavaScript and never transmitted to any server.
Example hashes are grouped in blocks of 8 characters for readability; remove the spaces before comparing. The text abc with no trailing newline produces 90015098 3cd24fb0 d6963f7d 28e17f72. The same text followed by one LF newline produces 0bee89b0 7a248e27 c83fc3d5 951213c1. Newlines are part of the input bytes. Other tools may use CRLF instead of LF; check the actual text, spaces, letter case and line endings before comparing.
This tool uses UTF-8. Enter the two characters 中文 without quotes, spaces or a trailing newline; the MD5 result is a7bac223 9fcdcb3a 067903d8 077c4a07. The hash is grouped in blocks of 8 characters for readability; remove the spaces before comparing. An external system using Big5, GBK or another encoding hashes different bytes, so matching visible characters alone is not enough.
A file checksum hashes the file's raw bytes; this tool hashes text as UTF-8. They match only if those byte sequences are identical. A byte-order mark (BOM), another encoding, or different line endings can change the result. Pasting decoded text does not preserve arbitrary binary file bytes; use a tool that reads the original file bytes when you need its file checksum.