Email normalizer

Email normalizer - free online tool.

Enable JavaScript to use the interactive tool. The guide below explains how it works.

Email Normalizer

1. What the tool does

The Email Normalizer is a high-performance utility designed to sanitize and standardize email addresses. It processes lists of email addresses to remove common variations that point to the same underlying inbox. This process, known as "normalization," involves converting emails to a canonical format by handling provider-specific quirks, such as sub-addressing (the + suffix) and character-specific rules (like dots in Gmail).

The tool takes a raw list of emails—often gathered from sign-up forms, databases, or marketing logs—and outputs a cleaned version where each entry is lowercase, stripped of unnecessary characters, and resolved to its simplest functional form. It uses the email-normalizer engine to apply these rules consistently across thousands of entries.

2. Why someone uses it

Email normalization is critical for data integrity, security, and marketing efficiency. Without it, a single user can appear as multiple distinct entities in a system.

Key reasons for using this tool include:

3. Step-by-step instructions

The tool is designed for bulk processing with a simple interface:

  1. Input Gathering: Collect the email addresses you need to normalize. This can be a single email or a list of thousands.
  2. Paste Emails: Enter your emails into the "Raw emails to normalize" text area. Each email should be on its own line.
  3. Real-time Processing: The tool automatically processes the list as you type or paste. You will see the results appearing in the "Normalized emails" section.
  4. Error Handling: If an entry is not a valid email format, the tool will flag it with a message: Unable to parse email: [input]. This helps you identify malformed data in your source list.
  5. Finalize:
    • Click "Copy normalized emails" to copy the entire cleaned list to your clipboard.
    • Click "Clear emails" to reset the tool for a new batch.

4. Examples

The Gmail "Dot" Trick

Gmail ignores periods in the username portion of an email.

Sub-addressing (Plus Addressing)

Many providers allow adding a + followed by any string for filtering.

Case Sensitivity

While the local part of an email can technically be case-sensitive according to RFCs, in practice, almost no modern providers treat them that way.

Mixed Batch Processing

Input:

John.Doe+test@gmail.com
JaneDoe@outlook.com
invalid-email-string
admin@MyCompany.com

Output:

johndoe@gmail.com
janedoe@outlook.com
Unable to parse email: invalid-email-string
admin@mycompany.com

5. FAQs

Q: Does it work for all email providers? A: It applies standard RFC normalization to all emails and applies specific "aggressive" normalization rules for major providers like Gmail, Outlook/Hotmail, iCloud, and Yahoo.

Q: Is the normalization reversible? A: No. Normalization is a destructive process intended to find the "root" inbox. Once you remove +tags or dots, you cannot programmatically know which ones were there originally.

Q: Does it verify if the email actually exists? A: No. This tool is a syntax and logic-based transformer. It does not perform SMTP handshakes or check MX records to see if the inbox is active.

Q: Is my data sent to your servers? A: No. All processing happens locally in your browser's JavaScript engine. Your email lists never leave your machine.

6. Common mistakes

7. Use cases

9. Technical Deep Dive: The Mechanics of Normalization

Normalization is a multi-stage process that balances RFC compliance with the practical realities of how major email providers operate. The email-normalizer library follows a specific execution pipeline for every entry.

Stage 1: Basic Sanitization

First, the tool performs a global lowercase conversion and trims all leading and trailing whitespace. It then splits the email into two parts: the local-part (before the @) and the domain (after the @).

Stage 2: Domain-Specific Logic

The tool maintains a registry of major email providers and their unique handling rules.

Stage 3: The "Sub-addressing" Parser

For domains not explicitly in the provider registry, the tool checks for common sub-addressing characters. While + is the most common, some systems use - or _. The normalizer defaults to stripping + suffixes to ensure broad compatibility without risking the corruption of standard "dashed" emails (like first-last@company.com).

Stage 4: Reassembly

Finally, the tool reassembles the normalized local-part and the domain into a canonical string. If at any point the string fails a basic regex validation (e.g., missing an @ or having invalid characters in the domain), the original string is returned with an error prefix to prevent the loss of data.

10. Security Considerations

While primarily a utility tool, email normalization has significant security implications.

Sybil Attack Mitigation

In distributed systems, a "Sybil attack" occurs when one person creates many identities. By using this tool to normalize emails before checking for existing accounts, you can effectively block users from creating 100 accounts using user+1@gmail.com through user+100@gmail.com.

Data Privacy

Normalization can be a form of "deanonymization." If you have a database of normalized emails, you can potentially link disparate data points that were intended to be separate. Always ensure that your use of normalized data complies with local regulations like GDPR or CCPA, especially regarding the storage of "identifiable" vs "canonical" data.

All tools

Guides and articles