John.Doe+newsletter@gmail.comjohndoe@gmail.comgmailALICE@HOTMAIL.COMalice@hotmail.comchangedbob+spam@GMAIL.COMbob@gmail.comgmailtest@outlook.comtest@outlook.comunchangeduser@subdomain.YAHOO.CO.UKuser@subdomain.yahoo.co.ukchangedAbout Email Normalizer
john.doe+news@gmail.com, JohnDoe@Gmail.com, and johndoe@googlemail.com may all be the same inbox. This tool normalizes emails locally in your browser: it lowercases them, strips plus-tags, and for Gmail removes dots and folds googlemail.com into gmail.com, revealing the truly unique deduplicated addresses. It supports batch paste and shows total, unique, and changed counts, ideal for cleaning user lists while keeping every email on your device. The key insight is that this mirrors Gmail's actual behavior rather than arbitrary character cleanup: Gmail ignores dots in the local part when routing and treats googlemail and gmail accounts as the same, so removing dots is a faithful normalization. The tool applies the dot rule only to Gmail since other providers keep dots. Because normalization is a one-way transformation, keep a backup of the original list, and for attribution or marketing analysis retain the plus-tag so you do not lose source-channel information. The cleaned list exports directly for dedup statistics and pre-send cleaning. Whether an address is case-sensitive depends on the provider implementation, so treating all as equivalent is unsafe. The standard allows the local part to be case-sensitive in principle, most mainstream providers treat it as insensitive in practice, and some systems compare as written. Normalisation suits internal deduplication and search, not for deciding two addresses belong to one person. Dot and plus rules apply only to some providers, and generalising them goes wrong. One provider ignores dots in the local part, another treats everything after a plus as a tag to ignore, which makes several addresses of one user point to a mailbox. Applying the same rules to a domain that does not support them merges genuinely different people and causes missed or misdelivered mail. International addresses involve non-Latin characters handled differently from Latin ones. Both the local part and the domain may contain them and need encoding before delivery, while the original spelling should be restored for display. Normalisation must therefore be two paths — canonical for storage, original for display — rather than showing the canonical form. When normalisation is used for deduplication, weigh the cost of a wrong merge. Merging two different people means one stops receiving what they should, while failing to merge only sends one extra copy. For high-value notices such as invoices or verification codes, act conservatively: keep two records rather than merging on an equivalence rule that may not hold. A display name and an address must be handled apart or parsing fails. The form usually pairs a name with an address in angle brackets, and the name itself may contain commas, dots or even address-like fragments, so splitting on delimiters cuts in the wrong place. Split on the brackets first to separate the structure, then process each part. Finally, the result should be explainable and traceable. Since different rules change outcomes, be able to say which rule made two addresses equivalent after processing. Recording the basis for each equivalence decision helps investigate delivery failures and assess the impact when a rule changes, rather than treating the outcome as a black box.
How It Works Internally
Normalisation handles two different things: the domain is lowercased and trimmed, which the specification allows since it is case-insensitive, while the local part is left alone because it is case-sensitive by specification even though mainstream providers ignore case. Lowercasing the local part can make an address nonexistent on self-hosted mail. Some services define equivalent forms such as plus aliases, which normalisation must not expand on its own.
User.Name+tag@Example.COM User.Name+tag@example.com (local part and alias kept, only the domain normalised)Measured on This Page
| Gmail rules | John.Doe+newsletter@gmail.com -> johndoe@gmail.com (dots removed, alias stripped, lowercased) |
|---|---|
| googlemail mapping | test@googlemail.com -> test@gmail.com (two domains, one mailbox) |
| Non-Gmail keeps dots | first.last@mycompany.com -> unchanged (dots are valid characters at most providers) |
| Non-Gmail strips plus | a+b@outlook.com -> a@outlook.com (a semantic risk, see the note) |
| Malformed input | no-at-sign is returned unchanged and badged as unchanged — no crash, no silent drop |
| Google, last 90 days | 3 clicks / 26 impressions / average position 36.1 |
Under RFC 5321 the plus sign is a legal local-part character, so removing it yields a different address. Gmail treats + as a subaddress and Outlook supports it too, which makes stripping safe for those two; a self-hosted domain can assign a and a+b to two different people, and then a+b@yourcompany.com normalising to a@yourcompany.com files the mail under someone else. Before deduplicating a list this way, confirm every domain in it supports subaddressing.
How to Use
- Open "Email Normalizer"
- Paste one email address per line
- Tick lowercase, plus-tag, or dot rules
- Compare the original and normalized rows
- Click "Copy all" to export the column
Use Cases
- Dedupe lists — Fold case and plus-tag variants in a marketing list to count truly unique recipients.
- Abuse detection — Spot multiple alias accounts registered with plus-tags or Gmail dots on one inbox.
- Data cleaning — Unify email format before CRM import to avoid duplicate customer records.
- Login matching — Normalize the entered email before a database lookup to improve account matching.
- Batch review — Paste many emails at once to see which were rewritten and which are duplicates.
- Import validation — Normalize email columns before bulk CSV import to catch duplicates early.
- Analytics grouping — Fold plus-tag and dot variants to get a unique count of real users per campaign.
FAQ
Why are Gmail dots removed?
Gmail ignores dots in the local part when routing, so j.smith@gmail.com and jsmith@gmail.com reach the same inbox; normalization drops the dots.
What is a plus-tag and does removing it affect delivery?
A plus tag like +news is used to categorize sources; mail still reaches the base address, and removing it only helps identify the same inbox.
Does dot removal apply to non-Gmail addresses?
No. The dot rule is specific to Gmail/googlemail; other providers keep dots in the local part, so the tool applies it only to Gmail.
Is normalization lossless or reversible?
It is a one-way transformation: stripping plus-tags and Gmail dots cannot be reversed, so keep the original list as a backup for attribution.
Can I send mail to the normalized address?
Normalized results are safest for dedup and matching; for actual sending, prefer the original address the user provided to fit each provider.
How do I hide part of an email instead?
This tool unifies format, not masking. To obscure part of an email, use our String Obfuscator.
Email bounces after normalisation. Why?
The local part of an address is case-sensitive by specification; mainstream providers usually ignore case, but self-hosted systems may match exactly, so lowercasing the local part can produce an address that does not exist. Lowercase and trim the domain only, and leave the local part untouched unless you have confirmed the destination treats it case-insensitively.
Does Gmail ignore dots (a.b@gmail.com = ab@gmail.com)?
Gmail ignores dots in the local part, but most providers do not. Normalise by each provider's rule — applying Gmail's behaviour to all addresses creates false merges.