Skip to content
Sealpaste

Delete all recent work?

This removes the 0 items saved in this browser. Your settings stay.

Stop saving recent work?

New work won't be saved in this browser. The 0 items already saved can stay or go.

MD5 Hash Generator

Text

Type or paste text, or

HashesUTF-8
Ready
Runs in your browser. Nothing you paste is uploaded unless you share it.

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

  1. Paste text or open a file.
  2. Copy the MD5 from the highlighted row (hex by default).
  3. Need something stronger? SHA-256 is in the same list.

Example

MD5 of "hello"

Input
hello
Result
5d41402abc4b2a76b9719d911017c592

MD5 vs SHA-256

Both turn any input into a fixed-size fingerprint, and both are fast. The difference is safety: two different inputs with the same MD5 can be made on purpose, so an MD5 proves nothing against someone who wants to fool you. No such pair is known for SHA-256.

MD5SHA-256
Output128 bits, 32 hex characters256 bits, 64 hex characters
CollisionsMade in seconds on a laptop since 2006None known
Use it forSpotting accidental changes, cache keys, legacy APIsDownload checks, signatures, anything an attacker could touch
PasswordsNeverNever on its own: use bcrypt or Argon2id

Sources: RFC 6151: MD5 security considerations, NIST FIPS 180-4 (SHA-2)

MD5 in code

The digest of "hello" is the same in every language when the text goes in as UTF-8 with no trailing newline; echo adds one, printf does not.

import { createHash } from 'node:crypto';

createHash('md5').update('hello', 'utf8').digest('hex');
// '5d41402abc4b2a76b9719d911017c592'

Where MD5 still shows up

MD5 collisions can be produced on a laptop, so it must not protect anything. It still appears in:

  • 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

Gravatar, ad platforms and analytics tools match people by a hash of their email address, and the same address only gives the same hash when it is written the same way. Turn on Normalize email: spaces at both ends are cut and the address is lowercased before hashing, so “ Ada@Example.com” and “ada@example.com” give one hash.

Gravatar documents SHA-256 of the normalized address; older Gravatar links used MD5, the same way. Meta’s Conversions API and Google’s Customer Match take SHA-256, in the SHA-256 row of the same list. Google also asks to drop the dots before @ in gmail.com and googlemail.com addresses; do that by hand before pasting.

A hashed address is not anonymous: anyone with a list of addresses can hash them and compare. Treat it as personal data.

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.

Related tools