MD5 Hash Generator

MD5 (Message-Digest Algorithm 5, RFC 1321, Rivest 1992) condenses any input into a fixed 128-bit value, written as 32 hexadecimal characters. This page implements the algorithm in pure JavaScript and runs it in your browser: the text you type is UTF-8 encoded and hashed locally, so nothing is uploaded and no account is required. Identical input always yields the identical digest — md5("hello") is 5d41402abc4b2a76b9719d911017c592 in every conforming implementation — which is why MD5 is still used for checksums, cache keys, ETags, and deduplication. It is not a cipher: there is no key and no reverse function, only a deterministic mapping from bytes to a 16-byte fingerprint.

Generate mode hashes a single string live as you type, or switch to Bulk Mode to hash a whole list — one string per line — in a single pass. Auto Generate is on by default; you can also press Ctrl+G (Cmd+G on macOS). The Uppercase toggle switches the hex letters to A–F for display without changing the underlying digest. Every result keeps its original input, so you can export the mapping rather than just the hashes. Copy As offers hash-only, input => hash, JSON, or CSV; Download As writes .txt, .csv, or .json with a date-stamped filename. The downloaded .csv quotes and escapes the input column so it stays spreadsheet-safe.

MD5 has no mathematical inverse, so "decrypt" is a misnomer — the Lookup / Decrypt tab recovers plaintext only by re-hashing candidates until one matches. It first checks an in-browser dictionary (a rainbow table built at runtime from common passwords plus suffix variants like 123, !, and 2024), then brute-forces every string from length 1 up to your chosen maximum over a selected character set. Unlike md5decrypt.net or md5.gromweb.com, which query billion-row server databases, this runs entirely on your machine — private, but effective only for short or common inputs.

Use MD5 for non-adversarial integrity: verifying a download against a published .md5, spotting accidental file corruption, or generating cache and dedup keys. Do not use it where an attacker benefits from a collision. MD5 has been collision-broken since Wang et al. (2004), and chosen-prefix collisions are practical — the Flame malware forged a code-signing certificate with one in 2012. So never hash passwords with MD5 (use bcrypt, scrypt, or Argon2) and never rely on it for signatures or tamper detection. When you need a secure digest, reach for SHA-256 (256-bit, 64 hex). MD5 stays fast and ubiquitous, which is exactly why it still fits the harmless jobs above.

No. MD5 (RFC 1321, Rivest 1992) is a 128-bit digest that is cryptographically broken: practical collisions were shown by Wang et al. in 2004, and a chosen-prefix collision let the Flame malware forge a code-signing certificate in 2012. Never hash passwords with MD5 — use bcrypt, scrypt, or Argon2 — and never rely on it for digital signatures or tamper detection. MD5 remains fine for non-adversarial integrity: file checksums, cache keys, ETags, and deduplication. When you need a secure hash, use SHA-256.

No. The MD5 algorithm is implemented in pure JavaScript and executes in your browser; there is no upload, fetch, or account. Your input is UTF-8 encoded locally and hashed on your machine, so pasted secrets, tokens, or file contents never leave the page. The reverse Lookup / Decrypt mode is also entirely local — it builds its dictionary and brute-forces candidates client-side rather than querying an external database.

No. MD5 is a one-way function with no mathematical inverse and no key, so it cannot be decrypted. The Lookup / Decrypt tab recovers plaintext only by re-hashing candidates until one matches: it checks an in-browser dictionary of common passwords and suffix variants, then brute-forces strings from length 1 to your chosen maximum. It only finds short or common inputs. Server tools like md5decrypt.net or md5.gromweb.com match against billion-row databases; this stays local and will not resolve long or unique strings.

An MD5 digest is 128 bits, which is 16 bytes, displayed as 32 hexadecimal characters (0-9 and a-f). Length is fixed regardless of input size — a single letter and a 10 MB file both produce 32 hex characters. For example, md5("hello") is 5d41402abc4b2a76b9719d911017c592 and md5 of an empty string is d41d8cd98f00b204e9800998ecf8427e in every conforming implementation.

Yes. Before hashing, input is UTF-8 encoded via encodeURIComponent, so multi-byte characters are hashed as their UTF-8 bytes. That means "café" and emoji produce the standard MD5 values that match other RFC 1321 implementations and command-line tools like md5sum, rather than a mangled result from raw UTF-16 code units.

Switch to Bulk Mode and enter one string per line. With Auto Generate on (the default), hashes appear as you type; you can also press Ctrl+G. Each result keeps its original input, so you can export the full mapping — Copy As CSV or JSON, or Download As a .csv/.json file. The downloaded .csv quotes and escapes the input column (with an Input, MD5 Hash, Timestamp header) so it round-trips cleanly in a spreadsheet, while Copy As CSV gives a plain input,hash line per row.

No. MD5 produces a fixed sequence of 16 bytes; the Uppercase toggle only changes whether the hexadecimal letters are shown as a-f or A-F. 5D41402ABC4B2A76B9719D911017C592 and 5d41402abc4b2a76b9719d911017c592 are the same 128-bit digest written two ways. Case matters only if a downstream system does a case-sensitive string comparison on the hex text.

Six, selectable when Brute Force is enabled: digits only (0-9, 10 chars), lowercase (a-z, 26), alphanumeric (a-z plus 0-9, 36, the default), mixed case (a-z, A-Z, 0-9, 62), with special (adds punctuation, 95), and full keyboard (all printable ASCII plus space, 96). Maximum length is 1–10, but each extra character multiplies the search space by the charset size, so lengths above 6 are flagged as exponentially slower.

MD5 produces a 128-bit digest (32 hex characters); SHA-256 produces a 256-bit digest (64 hex characters). MD5 is faster but collision-broken since 2004, so two different inputs can be crafted to share a hash. SHA-256 has no known practical collision attack and is the current default for integrity and signing. Use MD5 only for non-security checksums, deduplication, or cache keys where an attacker gains nothing from a collision.

Yes, for detecting accidental corruption. Many projects still publish an .md5 alongside a download so you can confirm the bytes transferred intact, and MD5's speed makes it convenient for large files. It is not safe against a deliberate attacker, who could craft a malicious file with a matching MD5 via a collision. For tamper-evident verification, prefer a published SHA-256 checksum instead.