Email Hash Generator
Turn an email address into its SHA-256, SHA-1 and MD5 hashes. Everything runs in your browser, so the address never leaves your device.
Enter an email address and press Hash Email.
How the two normal forms differ
Standard trims spaces and lowercases the address. Use it when a platform tells you to hash emails that way, which most advertising and identity partners do.
Inbox-Normalized goes further. Gmail ignores dots and anything after a plus sign, so Jane.Doe+news@googlemail.com becomes janedoe@gmail.com. Yahoo, Proton, Fastmail and mail.com addresses lose their plus tags but keep their dots. This is the form Data Legion hashes when it indexes profiles, so hashes made this way match in the Person Enrichment API.
Prefer to hash in code? The free Email Hashing API returns all three hashes for an address with any Data Legion API key and applies the same provider rules.
Common Questions
Hashed emails, normalization and privacy
A hashed email is the output of running a normalized email address through a one-way function such as SHA-256. Two systems that hash the same address the same way get the same string, so they can match records without exchanging the address itself.
Trim the address, lowercase it, then run it through SHA-256 (or SHA-1 or MD5) and keep the hex digest. Paste it above to get all three at once. In Python it is one line: hashlib.sha256(email.strip().lower().encode()).hexdigest(). In JavaScript, pass the trimmed, lowercased address to crypto.subtle.digest('SHA-256', ...) and hex-encode the bytes it returns. Gmail ignores dots and plus tags, so the Inbox-Normalized option removes those first.
Hashing is one-way, but it is pseudonymous rather than anonymous: anyone holding a list of addresses can hash them and look for matches. Treat hashed emails as personal data and share them only with partners you would trust with the plaintext.
SHA-256 is the usual default for new integrations and what most ad and identity platforms request. SHA-1 and MD5 are older and still common in existing audience files, so the tool shows all three.
A hash changes completely if one character changes, so "Jane@Example.com" and "jane@example.com" hash differently. Trimming and lowercasing first makes the same person hash the same way everywhere. Data Legion also removes Gmail dots and provider plus tags, because those variants all reach one inbox.
Yes. Send a SHA-256, SHA-1 or MD5 hash in the email_hash parameter of the Person Enrichment API and it matches the profile behind it. Use the Inbox-Normalized form so the hash lines up with how the profiles are indexed.
No. The hashes are computed by JavaScript in this page. The address is never sent to Data Legion or anyone else, and analytics events record only which hash you copied.
Match Hashed Emails to Profiles
Send a hashed email to the Person Enrichment API and get the profile behind it. Start with free trial credits.