⌘ K
md5 · 32 hex chars · js-md5 · live

Generate MD5 digests

Compute the MD5 hash of any UTF-8 text. 128-bit, 32 hex characters. Hashing uses js-md5 and runs entirely in your browser.

MD5 Hash Generator
Input
43 B
43 chars
Algorithm
MD5
128-bit
Digest
—
lower
Status
loading
js-md5
input · text
output · md5 hex
—
Quick Start

How to compute MD5

Hashes UTF-8 bytes via the js-md5 library. Output is a 32-character lowercase hex string (or uppercase if toggled).

  1. 01

    Type or paste text

    Any UTF-8 input — emoji and accents are hashed faithfully.

    Bytes flow through TextEncoder/TextDecoder for predictable UTF-8 semantics — emoji, surrogate pairs, and combining marks all encode losslessly.

    inputUTF-8TextEncoderlosslesslive
    input · raw bytestext · UTF-8
    hello
    loaded · UTF-8MIME · ready
  2. 02

    Pick the case

    Toggle between lowercase and uppercase hex output.

    Hash and signature operations call crypto.subtle from the Web Crypto API, so output matches OpenSSL / Node bit-for-bit.

    formatWeb Cryptosubtledeterministiclive
    case · optionslower · live
    5d41402a…
    options applied · livelive
  3. 03

    Live hash

    Output updates as you type. 128 bits → 32 hex chars.

    Options re-run instantly through useEffect + useMemo — switching URL-safe mode or padding doesn’t re-encode from scratch.

    livememoisedoptionsinstantreactive
    out · encoded32 hex · ready
    5d41402abc4b2a76…
    encoded · livelossless
  4. 04

    Copy or download

    One click to clipboard. Download as .txt.

    Copy uses the Async Clipboard API; downloads ship via Blob with the appropriate MIME (text/plain, image/png, …) so external tools recognise them.

    exportclipboardblobMIME-correctclient-side
    ok · copiedready · done
    Copied
    shipped · ready to shipsuccess
Pro tips

Encoding without surprises

Always UTF-8 first

Use TextEncoder / TextDecoder for bytes ↔ string conversion. btoa alone breaks on non-ASCII.

URL-safe vs standard Base64

Standard uses +, /, =; URL-safe swaps to -, _, no padding. Don’t mix them.

Hashes aren’t passwords

SHA-256 is fast; that’s good for fingerprints, bad for passwords. Use bcrypt / argon2 for credentials.

Watch padding rules

Some decoders are strict about = padding, others auto-pad. If round-trips fail at exactly 1 or 2 bytes, check padding.

Use Web Crypto for keys

Generate cryptographic keys via crypto.subtle, never Math.random. The latter is predictable.

JWT decode ≠ verify

Decoding a JWT just splits and base64-decodes. Verification needs the issuer’s public key / shared secret.

Related toolsSHA-1SHA-256SHA-512CRC32BcryptRIPEMD-160
Use Cases

When to use MD5

Non-security integrity checks and legacy fingerprints.

Legacy checksums

Verify vendor MD5 sums on downloads. Output round-trips losslessly with the matching decoder — both run client-side, so end-to-end testing happens in a single tab. Encoding flows through TextEncoder for predictable UTF-8 semantics.

RFC-compliant

Cache busters

Fingerprint static assets in a build. Web Crypto's subtle.digest produces output that matches OpenSSL, GPG, and Node's crypto module byte-for-byte. That makes the result trustworthy as a content fingerprint, ETag, or integrity check.

OpenSSL-matched

ETag values

Generate weak ETags for HTTP caching. Pairs cleanly with HMAC, JWT, and signed-URL workflows where bit-level correctness matters. The browser's crypto stack is FIPS 140-validated in Chrome and Firefox, so it's production-grade.

lossless

Test fixtures

Snapshot deterministic outputs in tests. Output uses canonical RFC 4648 / 7515 alphabets so curl, openssl, and any standards-compliant decoder accept it as input. URL-safe variants drop padding for tokens that travel in query strings.

byte-identical

Dedup keys

Group identical blobs in bulk imports. Heavy hashing runs through useMemo so large inputs don't block typing. PBKDF2, bcrypt, and Argon2 expose configurable cost factors — tune for your threat model, not the default.

spec-grade

Quick fingerprint

Compare two strings without showing them. Same input plus same options always yields identical bytes. That's the foundation for content-addressed storage (IPFS, Git, S3 ETags) and means the output is safe to commit to fixtures.

production-ready
FAQ

Frequently asked questions

No. MD5 is cryptographically broken — collisions can be constructed. Use bcrypt, Argon2, or scrypt for passwords.
MD5 produces 128 bits, which is 16 bytes — two hex characters per byte = 32 characters.
Only against accidental corruption — never against a malicious adversary. Use SHA-256 if integrity matters.
For files use the File Checksum Verifier — it streams large files efficiently.
No. MD5 is computed in your browser via js-md5 and runs locally.
Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

Sent straight to the maintainers · no account needed
47 in queue·8 shipped this month
Request queued. Thanks!