MD5 Hash Why a Cryptographically Broken Algorithm Still Appears Everywhere — from File Downloads to Database Indexing

In 2004, Chinese researchers Xiaoyun Wang and Hongbo Yu demonstrated a practical collision attack on MD5. They could create two different files with the same MD5 hash — a cryptographic death sentence. The security community declared MD5 broken. Every security guideline since 2005 has said: "Do not use MD5. Use SHA-256." Yet in 2026, MD5 is still everywhere. File download pages still list MD5 checksums. Database systems still use MD5 for indexing. Content delivery networks still use MD5 for cache keys. A MD5 hash generator is still one of the most-used developer tools.

Why does a broken algorithm refuse to die? The answer reveals the difference between cryptographic security and practical utility — and why MD5 is still perfectly fine for most of the things people actually use it for. Here is what MD5 can still do, what it cannot do, and when to use SHA-256 instead.

What MD5 Cannot Do (and Why It Was Declared Dead)

MD5 is broken for collision resistance — the property that prevents an attacker from creating two different inputs with the same hash. A collision attack on MD5 takes seconds on modern hardware. This means: a malicious actor can create a fake software update with the same MD5 hash as the legitimate update, a forged digital certificate with the same MD5 hash as a trusted certificate, and two different documents with the same MD5-based digital signature. In all of these cases, the attacker exploits the collision to make a malicious file appear legitimate.

Do not use MD5 for: digital signatures, SSL/TLS certificates, password hashing (use bcrypt, scrypt, or Argon2), and any security context where an attacker might try to create a collision. In these cases, MD5 is not just weak — it is actively dangerous.

What MD5 Can Still Do (and Why It Survives)

MD5 is still perfectly fine for non-adversarial use cases — situations where no one is trying to attack the hash. These include: file integrity checksums (detecting accidental corruption during download, not deliberate tampering), database indexing (MD5 produces a fixed-size hash of variable-length data, which is useful for creating compact index keys), cache keys (CDNs and caching systems use MD5 to generate unique keys from URLs or content), and deduplication (identifying duplicate files by comparing their MD5 hashes).

In all of these cases, the threat model is accidental collision, not deliberate attack. The probability of two random files having the same MD5 hash by accident is 1 in 2¹²⁸ — astronomically small. The collision attacks that broke MD5 require the attacker to deliberately craft both files. In a non-adversarial context, MD5 is still perfectly reliable.

MD5 survives because it is: fast (MD5 is faster than SHA-256, which matters for high-throughput systems), compact (128-bit output vs 256-bit for SHA-256 — smaller cache keys and index entries), and universally supported (every programming language and platform has an MD5 implementation).

When to Use MD5 vs SHA-256

Use MD5 for: file integrity checksums (detecting accidental corruption), database indexing and cache keys, deduplication of non-security-critical data, and any non-adversarial hashing where speed and compactness matter. Use SHA-256 for: digital signatures, certificate validation, password hashing (with a proper salt), and any security context where an attacker might try to create a collision. The hash generator supports both algorithms. Use the right one for your threat model.

MD5 is cryptographically broken and practically immortal. It will outlive every security guideline that says not to use it. Not because the guidelines are wrong — they are right about the security risks. But because most of the things people use MD5 for are not security risks. The algorithm is broken for the thing it was designed for and perfectly fine for the things people actually use it for. That is why it refuses to die.

Generate hashes at MD5 generator and hash generator — know the difference between what MD5 cannot do and what it still does perfectly well.