MD5 Hash Generator

How to use the MD5 Hash Generator

1. Type or paste your input

   Any text, any length, including Unicode and multiple lines. The hash updates as you type.

2. Copy the 32-character result

   MD5 always outputs 128 bits, shown as 32 hexadecimal characters, regardless of how long the input was.

3. Compare against a published checksum

   When verifying a download, paste the value the publisher lists and compare character by character. Any difference at all means a different file.

4. Mind the whitespace

   A trailing space or newline changes the hash completely. If two values do not match when they should, check for invisible characters first.

What this tool does

What a hash function does

A hash function is a one-way mapping. Feed it any input and it produces a fixed-size output — for MD5, always 128 bits written as 32 hex characters. Three properties make it useful:

• Deterministic — the same input always produces the same hash, on any machine, in any language.
• Fixed length — hashing one word and hashing a gigabyte both give you 32 characters.
• Avalanche effect — change a single character and the output changes completely, with no resemblance to the previous value.

Hashing is not encryption. Encryption is reversible with the key; hashing is not reversible at all. You cannot recover "hello" from its hash — but you can confirm that a given input produces that hash, which is the whole basis of checksum verification.

MD5 is broken — what that actually means

MD5 was designed in 1991 and has been considered cryptographically broken since 2004, when practical collision attacks were demonstrated. A collision is two different inputs producing the same hash. Today, collisions can be generated on ordinary hardware in seconds.

Concretely, this means MD5 can no longer prove that a file has not been tampered with by someone who wants to tamper with it. An attacker can craft two files — a legitimate one and a malicious one — that share an MD5 hash. If you verify by MD5 alone, both pass.

What MD5 remains adequate for is detecting accidental change: a truncated download, a corrupted transfer, a disk error. Random corruption will not produce a matching hash. Deliberate corruption might.

So the rule is simple. Accidental damage: MD5 is fine. Adversarial tampering: use SHA-256.

Never use MD5 for passwords

This deserves its own section because the mistake is still common in older PHP codebases.

MD5 is extremely fast, and for password hashing speed is the enemy. A modern GPU can compute billions of MD5 hashes per second, which means a leaked table of MD5 password hashes can be brute-forced almost immediately. Add the vast public rainbow tables of precomputed MD5 hashes and most common passwords resolve instantly.

Salting helps against rainbow tables but does nothing about raw speed. md5($password . $salt) is still catastrophically weak.

For passwords, use a purpose-built slow hashing algorithm — bcrypt, scrypt or Argon2. These are deliberately expensive to compute, with a tunable cost factor you raise as hardware gets faster. In PHP, password_hash() and password_verify() handle this for you and pick a sensible default:

// Correct
$hash = password_hash($password, PASSWORD_DEFAULT);
if (password_verify($input, $hash)) { /* authenticated */ }

// Never do this
$hash = md5($password);

If you have inherited a system storing MD5 passwords, the migration path is straightforward: on each successful login, verify against the old MD5 hash, then immediately rehash the plaintext with password_hash() and update the record. Over a few weeks most active accounts convert themselves, and you can force a reset for whatever remains.

Where MD5 is still reasonable

File integrity for accidental corruption

Software mirrors have published MD5 checksums for decades. If the hash of your download matches, the file arrived intact. For security-critical downloads, prefer the SHA-256 checksum when the publisher offers one.

Cache keys and deduplication

Hashing a long query string or a set of parameters into a short fixed key is a classic use. Nothing adversarial is happening, and MD5's speed is an advantage. Detecting duplicate images or files in a library works the same way.

Gravatar and similar APIs

Gravatar identifies users by the MD5 hash of their lowercased, trimmed email address. It is a lookup key, not a security measure, and it is not going to change.

ETags and change detection

Hashing file contents to generate an HTTP ETag, or to decide whether a cached artefact needs rebuilding, is entirely appropriate.

Legacy integrations

Plenty of older payment gateways and partner APIs still specify MD5 signatures in their documentation. You have no choice there — implement what the spec says, and push for an upgrade if the vendor offers one.

Common pitfalls when hashes do not match

1. Trailing whitespace. A newline your editor added at the end of a file changes the hash completely. This is the number one cause of mismatch.
2. Character encoding. The same text in UTF-8 and ISO-8859-1 produces different bytes and therefore different hashes. Always confirm the encoding on both sides.
3. Line endings. Windows CRLF versus Unix LF. A file that passes through Git with line-ending conversion enabled will hash differently on the two platforms.
4. Case of the hex output. Some systems output uppercase, some lowercase. The value is identical; compare case-insensitively.
5. Hashing the path instead of the contents. An easy mistake when scripting — make sure you are reading the file, not hashing its name.

Privacy

The hash is computed in your browser with a JavaScript implementation of the algorithm. Your input is never transmitted, logged or stored. That is worth caring about, because the strings people paste into hash tools are frequently API keys, tokens or credentials they are trying to verify — exactly the things that should not travel to someone else's server.

Frequently asked questions