Question 1

Is MD5 still safe to use?

Accepted Answer

MD5 has been collision-broken since 2004 — researchers can produce two different inputs that hash to the same value. It is unsafe for any security purpose: password storage, digital signatures, certificate fingerprints, integrity checks against adversaries. MD5 is still safe for non-adversarial use: file integrity against accidental corruption (download verification), deduplication keys, HTTP ETags, cache keys. NIST formally deprecated MD5 in 2011 (SP 800-131A) and no modern system should use it for security. If you're choosing a hash function in 2026, use SHA-256 or BLAKE2 for general purposes, Argon2id or bcrypt for password storage.

Question 2

Why does this tool use crypto-js for MD5 instead of Web Crypto?

Accepted Answer

The Web Crypto API (crypto.subtle.digest) deliberately omits MD5 because it's broken — the W3C made a policy decision not to ship insecure algorithms in the browser's native crypto. MD5 is implemented via the crypto-js library (~25KB minified), which is open-source and well-audited. The library runs entirely in your browser — no network requests, no server-side processing. The implementation is constant-time enough for non-adversarial uses; if you need timing-safe MD5 for a security context, MD5 is the wrong choice anyway.

Question 3

What's HMAC-MD5 and is it still safe?

Accepted Answer

HMAC (Hash-based Message Authentication Code) is a construction that combines a cryptographic hash with a secret key to produce a message authenticator. HMAC-MD5 is more resistant to attacks than plain MD5 because the secret key is mixed into the hash in a way that the known MD5 collision attacks cannot exploit. RFC 6151 (2011) notes that HMAC-MD5 'is not affected by the recent collision attacks' but recommends migration to HMAC-SHA-256 for new protocols. Existing protocols still using HMAC-MD5 (notably some older TLS cipher suites) are not actively broken but are deprecated.

Question 4

How does the file hashing work?

Accepted Answer

The File tab streams the file through the MD5 algorithm in 4MB chunks. The file's bytes never leave your browser — Web Worker streaming via FileReader.readAsArrayBuffer reads chunks into memory, the crypto-js incremental hasher updates with each chunk, then finalize() produces the digest. This works for files up to your browser's memory limits (typically multiple GBs for desktop Chrome/Firefox). For very large files (>10GB), this approach may slow down — for those, native command-line tools (md5sum, openssl dgst -md5) are faster.

Question 5

What's the output difference between hex and Base64?

Accepted Answer

Both encode the same 128-bit MD5 digest, just with different alphabets. Hex uses 32 characters from [0-9a-f], one character per 4 bits, very common in command-line tools and config files. Base64 uses 22-24 characters from [A-Za-z0-9+/=], one character per 6 bits, more compact and used in HTTP headers, email signatures, ETags. They're interchangeable — pick whichever your target system expects. The trailing == in Base64 is padding; some systems strip it (base64url variant).

MD5 Hash Generator

What Is MD5?

Safe vs Unsafe MD5 Uses

Safe (non-adversarial)

Unsafe (against attackers)

Frequently Asked Questions