MD5 Hash Generator
MD5 produces a 128-bit digest, written as 32 hex characters. Ron Rivest designed it in 1991; by 2004 researchers could produce two different inputs with the same hash, and by 2008 they had used that to forge a trusted TLS certificate. Today a laptop finds an MD5 collision in seconds.
That said, MD5 is still useful for what collisions do not affect:
- detecting accidental corruption in downloads, where nobody is trying to fool you
- deduplicating files, cache keys, ETags
- matching checksums published by older projects and package managers
The Web Crypto API deliberately omits MD5, so this page runs it in a small WebAssembly module that loads on demand. Files are hashed in chunks so size is not a limit. If you have a choice, publish SHA-256 alongside or instead.
What leaves your browser
Text is hashed in memory with the Web Crypto API; files are read in chunks with the File API and hashed in WebAssembly. There is no upload endpoint on this page. Open DevTools → Network and hash something: no request appears.
Is MD5 still safe for checksums?
For accidental corruption, yes. For verifying that a file was not tampered with by an attacker, no, because the attacker can craft a malicious file with the same MD5.
Why can't I decrypt an MD5 hash?
It was never encrypted. Sites that "decrypt MD5" are looking the hash up in a table of precomputed hashes of common inputs. That works only for weak inputs.
Are MD5 and MD5 with salt different?
Salting helps against precomputed tables but does not fix MD5's speed. For passwords use bcrypt or Argon2.
Can a hash be decrypted?
No. Hashing is not encryption; there is no key and no inverse function. The only way to find an input is to guess candidates and compare hashes, which is exactly why password hashes must be slow.
Why does the same text give a different hash on another site?
Usually a trailing newline, different line endings, or a different text encoding. Hash the exact bytes and the results agree everywhere.