DevTools Logo

Email Normalizer

Email Normalizer

Normalize email lists with provider-aware rules — lowercase, Gmail dots, +aliases, googlemail → gmail — and export the clean column in one click.

One address per line — blank lines are skipped.

Try a sample:

Ann@Example.com → ann@example.com

Only gmail/googlemail — dots are ignored there

jane+news@… → jane@… on every provider

Examples

Gmail full collapse

Input
John.Doe+Promo@GoogleMail.com
Output
johndoe@gmail.com

Four rules fire in order: googlemail mapping, alias strip, dot removal, lowercase — one canonical mailbox remains.

Yahoo dots survive

Input
first.last@yahoo.com
Output
first.last@yahoo.com

Dots are only ignored at Gmail; other providers keep them meaningful, so the address passes through with no rules applied.

Duplicate merge

Input
john.doe@gmail.com + johndoe@gmail.com
Output
2 rows → 1 unique mailbox

The unique counter flags the collapse so deduplication in the downstream tool becomes a formality.

About this tool

The same human can appear in a mailing-list export as john.doe@gmail.com, johndoe@gmail.com and john+promo@googlemail.com — three rows, one inbox. Gmail ignores dots in the local part, treats +anything as a delivery tag, and routes googlemail.com to the same servers as gmail.com. The Email Normalizer applies those provider facts mechanically: every address is lowercased, dots are removed from Gmail local parts, aliases are stripped, and the googlemail domain is mapped onto gmail.com, so a messy paste becomes a column of canonical mailboxes.

Provider awareness is the point. Dots are only insignificant at Gmail — first.last@yahoo.com is a different mailbox from firstlast@yahoo.com, so the tool never removes dots from other providers, no matter how convenient that would look. Alias stripping is offered for everyone because subaddressing (the +tag convention) is broadly supported, but it stays optional: some lists deliberately keep tags to trace where a leaked address came from. The three toggles — lowercase, Gmail dots, alias — map one to one onto the rules the before → after table reports per row.

The output is built for audit, not just for copy. Each row shows the original, the normalized address, and the exact rules applied, so you can spot surprises — for example, an address that changed more than you expected. A separate list collects lines that fail a fast syntax pre-check (no @, no dotted domain, stray spaces) with a pointer to the Email Validator for a full per-character diagnosis; the normalizer refuses to guess about malformed input. A unique counter summarizes how many rows collapsed into distinct mailboxes after the rules merged duplicates.

Everything happens on your device: the list is never uploaded, no lookup service is called, and the paste persists only in your browser's local storage between visits. The normalized column copies in one click for re-import into your CRM, newsletter tool or spreadsheet. When the cleaned list feeds outreach, the Email Signature Generator keeps the sending identity consistent, and if you need to check a single suspect address before it goes out, the Email Validator gives it the full syntax-and-domain treatment.

What this tool does not do

  • Normalization is rule-based, not delivery-tested: only the Email Validator or an actual send proves an address exists.
  • Only gmail/googlemail carry a provider rule table today; other dot-ignoring providers (rare) are treated conservatively as dot-significant.
  • The tool never sends mail, verifies MX records, or contacts any third-party service — it rewrites text on your device.

How to use this tool

  1. Paste your addresses

    Drop one address per line into the input — blank lines are skipped and the paste persists locally for your next visit.

  2. Tune the three rules

    Keep or switch off lowercase, Gmail dot removal and +alias stripping; non-Gmail dots are always preserved by design.

  3. Read the before → after table

    Each row names the rule applied; the unique counter shows how many rows collapsed into distinct mailboxes.

  4. Export and route the leftovers

    Copy the normalized column in one click, and send any pre-check failures to the Email Validator for full diagnosis.

Use cases

Merging duplicate contacts

Collapse the dot-and-alias variants of one Gmail mailbox before importing a list into a CRM, so one customer gets one record.

Cleaning newsletter exports

Normalize an unsubscribe or bounce list so re-imports match the canonical addresses your sending platform already stores.

Auditing sign-up data

See which signups are the same Gmail person under three spellings, and route malformed rows to full validation instead of guessing.

The provider rule table

RuleWhat it does
Lowercaseann@example.com from Ann@Example.com — domains are case-insensitive, local parts are conventionally lowercase
Gmail dotsjohndoe from john.doe — only for gmail.com and googlemail.com, where dots are ignored
+alias removaljane from jane+newsletter — the subaddress tag is stripped on every provider when enabled
googlemail → gmailDomain canonicalized to gmail.com; delivery is identical
Other providersDots kept meaningful: first.last@yahoo.com is never merged with firstlast@yahoo.com

The syntax pre-check is intentionally fast, not RFC-complete — invalid lines are listed, never normalized.

Common mistakes

Mistake:Removing dots on every provider.

Fix:Dot insignificance is a Gmail invariant only — first.last@yahoo.com and firstlast@yahoo.com are different mailboxes. The tool keeps non-Gmail dots by design.

Mistake:Treating a +tag as disposable forever.

Fix:Tags trace where an address leaked from. Keep alias stripping off when provenance matters, and only strip it for deduplication passes.

Mistake:Assuming the pre-check is a validator.

Fix:The normalizer only rejects obvious syntax breaks to keep invalid lines out of the table — run survivors through the Email Validator for quoted local parts, IP domains and full RFC rules.

Frequently asked questions

Why do Gmail addresses normalize at all?

Gmail ignores dots in the local part of an address, treats everything after a + as a delivery tag, and delivers googlemail.com to the same mailboxes as gmail.com. So john.doe@gmail.com, johndoe@gmail.com and john+promo@googlemail.com are one inbox wearing three costumes. Normalizing collapses those variants into a single canonical form — which matters whenever two records describing the same person should merge into one row instead of three.

Are dots really safe to remove from every email address?

No — and this tool never does it. Dot insignificance is a Gmail-specific invariant. At Yahoo, Outlook, Proton or a company mail server, first.last@yahoo.com and firstlast@yahoo.com are different mailboxes, and removing a dot would silently redirect your mail to whoever owns the other one. The normalizer only removes dots when it has detected a gmail.com or googlemail.com domain; every other provider keeps its dots untouched.

What is the +alias (subaddress) convention?

Many providers deliver jane+newsletter@example.com to jane@example.com's inbox, keeping the tag visible in the received message. People use tags to trace who leaked their address or to filter signups automatically. The alias rule here strips everything from the first + in the local part so deduplication can see the base mailbox — switch it off when provenance matters more than merging.

Is the syntax check a full email validator?

It is deliberately a fast pre-check, not an RFC 5322 audit: one @, no whitespace, and a dotted domain. Anything that fails goes to a separate invalid list instead of being half-normalized, and the note points you to the Email Validator for quoted local parts, IP-literal domains and per-character diagnosis. The split keeps the normalizer's output trustworthy — every row it emits is at least syntactically plausible.

Does the tool check whether an address actually exists?

No — no MX lookup, no SMTP probe, no third-party verification service. Normalization is a pure text rewrite based on provider rules, and it runs entirely in your browser: the list is never uploaded. Existence checks require sending mail or DNS queries, which is exactly what the validator-side tools handle; this tool's job is making equivalent addresses look equivalent.

Can I deduplicate a whole mailing list with it?

Yes — paste the list one address per line, keep all three rules on, and read the unique counter: it tells you how many normalized rows are distinct mailboxes. The copy button exports the normalized column for direct re-import into your spreadsheet, CRM or newsletter platform. Rows beyond the two-hundred rendered in the table still export — the cap only keeps the page responsive.

References & standards