Email Extractor
Email Extractor — runs in your browser. Inputs are not stored.
Extract emails
Enter values, then press Calculate.
Input stays in the browser and is not sent to the server.
How to use
- Paste a mail body, roster, or HTML fragment into text.
- Press Extract to find common email patterns with a regex.
- Found is match count including duplicates; after dedupe is unique addresses merged in lowercase.
- The list is one address per line, all lowercase, in first-seen order.
- Reset clears the fields. No send or validation server is called.
- You can alphabetize extracted addresses with list sorter or inspect hosts with domain extractor. This is a reference list, not delivery confirmation.
Key concepts
Email extraction gathers addresses from long text, HTML, or a roster. The regex is fairly permissive on local-part and domain labels but does not validate all of RFC 5322. Quoted locals, comments, and IP-literal domains can be missed or false-positive. There is no deliverability or MX lookup—harvest for reference only.
Compare and list in lowercase, so [email protected] and [email protected] merge. If found is larger than unique, the same address appears more than once. First-seen lowercase order is kept. Personal data in the body does not leave this tab. On a newsletter or HTML source, check found vs unique first to gauge misses.
Example
Inquiry: [email protected], follow-up [email protected] → found 2, after dedupe 1, list is one line [email protected]. Values without a TLD such as hello@localhost or Hangul local parts may not match. Copy the unique list into a spreadsheet as a duplicate-free roster. Split huge logs into chunks so the browser stays responsive. Unique smaller than found means duplicates were present.
Related: Domain extractor · List sorter · Character counter
Frequently asked questions
Can I extract only email addresses from text?
Yes. Paste the body and press Extract for a unique lowercase list. Review found count and the after-dedupe count together.
Are emails that differ only in case treated as one?
Yes. Compare and list are lowercase. Even if a local part is customarily uppercase, they merge to one line.
Is the email format perfect?
It is a practical heuristic. There is no MX lookup or inbox check, and it does not validate the full RFC.
Does it find Hangul local parts?
This regex is centered on Latin letters, digits, and some symbols in the local part. Internationalized addresses can be missed—scan the original once more.
Why do found and after-dedupe differ?
If the same address appears several times, found grows while the list keeps the first lowercase line.
Does the email list go to a server?
No. Search runs only in the browser. Bodies with personal data are not uploaded or logged.
Last reviewed: 2026-09-04