MD5 Hash Generator

MD5 (Message Digest Algorithm 5) was designed by Ronald Rivest in 1991 and published as RFC 1321 in 1992. It takes input of any length and produces a 128-bit digest, conventionally written as 32 hexadecimal characters. For over a decade it was the default choice for file checksums and even, in its early years, for storing password hashes — a use that would be considered a serious mistake today.

That changed in 2004, when Xiaoyun Wang and colleagues published a practical method for constructing MD5 collisions — two different inputs that hash to the same value — using ordinary computing hardware rather than a theoretical attack requiring implausible resources. By 2008, researchers had extended the technique to a “chosen-prefix” collision and used it to forge a rogue Certificate Authority certificate that browsers would have trusted. Today, generating an MD5 collision takes seconds on a laptop. Every major standards body has deprecated MD5 for any use where someone might deliberately try to forge a match.

What survives that history is MD5’s usefulness against accidental corruption. A bit flip from a failing disk, a truncated download, or a dropped network packet still changes the MD5 output almost certainly — nobody engineered that specific accident to preserve the hash. This is why plenty of older Linux distribution mirrors, legacy build tools, and archival systems still publish MD5 checksums alongside their files: not as a security guarantee, but as a fast, universally-supported “did this arrive intact” check. If you need to confirm a download matches what a vendor published, or that two files are byte-identical without diffing them directly, MD5 is still a reasonable, lightweight tool for that specific job — it just has no place anywhere an adversary benefits from a forged match: passwords, signatures, or tamper detection.

One practical wrinkle: browsers’ built-in Web Crypto API doesn’t implement MD5 at all (it was deliberately excluded as a legacy algorithm), so client-side JavaScript needs its own implementation — which is what powers this page. Server-side runtimes like Node.js and languages like Python, by contrast, still ship MD5 support directly for exactly this kind of legacy-compatibility use.

Computing an MD5 hash programmatically

Node.js (via the built-in crypto module — browsers can’t do this, since Web Crypto omits MD5):

import { createHash } from "node:crypto";

const hash = createHash("md5").update("Hello, World!", "utf8").digest("hex");
console.log(hash);
// "65a8e27d8879283831b664bd8b7f0ad4"

Python (via the standard library’s hashlib):

import hashlib

digest = hashlib.md5("Hello, World!".encode("utf-8")).hexdigest()
print(digest)
# "65a8e27d8879283831b664bd8b7f0ad4"