Generate an MD5 checksum of text or a file, in hex or Base64
Get the MD5 checksum of text or a file. Fine for legacy checks and cache keys, not for anything security-related.
How to use it
Paste text or open a file. Copy the MD5 from the highlighted row (hex by default). Need something stronger? SHA-256 is in the same list.
Example
MD5 of "hello"
hello
5d41402abc4b2a76b9719d911017c592
MD5 vs SHA-256
| MD5 | SHA-256 | |
|---|---|---|
Output | 128 bits, 32 hex characters | 256 bits, 64 hex characters |
Collisions | Made in seconds on a laptop since 2006 | None known |
Use it for | Spotting accidental changes, cache keys, legacy APIs | Download checks, signatures, anything an attacker could touch |
Passwords | Never | Never on its own: use bcrypt or Argon2id |
Sources: RFC 6151: MD5 security considerations, NIST FIPS 180-4 (SHA-2)
MD5 in code
import { createHash } from 'node:crypto';
createHash('md5').update('hello', 'utf8').digest('hex');
// '5d41402abc4b2a76b9719d911017c592'Where MD5 still shows up
S3 ETags and Content-MD5 headers for upload integrity. Old database columns, cache keys and deduplication. Legacy APIs that ask for an MD5 signature.
Hashing an email address
Sources: Gravatar: creating the hash, Meta: customer information parameters, Google Ads API: Customer Match normalization
Questions
- Is my text or file uploaded?
No. Everything runs in your browser, so your data stays on your device. Nothing you paste is uploaded unless you share it. SHA-1 and SHA-2 come from your browser’s Web Crypto API, the others from open-source code loaded with the page (the SHA-3, BLAKE and RIPEMD families from the audited @noble/hashes), which matters when you hash passwords or keys. - Can I use these hashes to store passwords?
No. MD5 and SHA are fast by design, which makes password guessing fast too. Store passwords with a slow, salted algorithm such as Argon2id, scrypt or bcrypt. - Is MD5 good enough to check a file?
Against accidental damage, yes: one changed byte changes the MD5. Against someone who wants to fool you, no: two different files with the same MD5 can be made on purpose. When the publisher lists a SHA-256, compare that; it is in the same list.