Enter text below to generate its MD5 checksum. Everything runs in your browser — your text is never sent to our server.
Computed locally in your browser — your text is never sent to our server.
Computed entirely in your browser — nothing you enter here is sent to our server.
Hashing…
About MD5 — and Its Limits
MD5 produces a 32-character hexadecimal checksum for any input. It’s still commonly used for one legitimate purpose: verifying that a downloaded file matches a checksum the publisher listed, or that two copies of a file are identical. It is not in the Web Crypto API that every modern browser provides (unlike SHA-256/SHA-512) — browsers dropped it because MD5 is cryptographically broken. This tool includes a small, dedicated JavaScript implementation for the checksum use case only.
Do not use MD5 for password storage, digital signatures, or anything where resistance to a deliberate attack matters — collisions (two different inputs producing the same hash) are practical to construct. Use SHA-256 or SHA-512 for anything security-sensitive.
FAQ
Is my text uploaded anywhere?
No. The checksum is computed entirely in your browser. Your text is never sent to our server.
Why shouldn’t I use MD5 for passwords?
MD5 is fast to compute, which is exactly the wrong property for password hashing — it makes brute-force attacks cheap. It’s also vulnerable to collision attacks. Use a purpose-built password hashing algorithm (like bcrypt or Argon2) in any real system, never MD5 or a general-purpose hash function.
What should I use MD5 for, then?
Non-security checksums: confirming a downloaded file wasn’t corrupted, or that two files are byte-for-byte identical, when a publisher has listed an MD5 value to check against.