TextToolboxTextToolbox
HomeText Extraction / AnalysisExtract Emails from Text

Extract Emails from Text

Extract supported ASCII email candidates with original spelling and exact domain filtering.

Built by Saurabh Kumar

Quick Answer

Find ASCII dot-atom email candidates without lowercasing their local parts. Deduplicate by exact local part and case-insensitive domain. Filter exact domains, select rows to copy and export all visible candidates as quoted CSV. Delivery is not verified.

ASCII dot-atom email candidates. Original spelling is preserved; deduplication compares local parts exactly and domains without case. Domain filtering is exact. This does not verify delivery.

Paste Your Text

Extracted Emails

Paste text to extract email addresses.

Pulling Email Addresses Out of Pasted Text

Paste any text and pull the email addresses out of it into a list you can copy. Find supported ASCII dot-atom candidates and preserve their original spelling. This is a text extractor, not complete mailbox validation, DNS checking or deliverability testing. Quoted local parts and internationalized addresses are outside this scanner's scope.

Pasting, filtering and copying

Paste text; optionally remove duplicates or set an exact domain filter. Select rows to Copy Selected, or Copy All when nothing is selected. CSV exports all visible filtered results, regardless of selection. CSV quoting preserves field boundaries but does not make spreadsheet formulas inert.

How duplicates and domains are compared

Deduplication compares the local part exactly and the domain without case, keeping the first spelling; it is not a provider-specific mailbox equivalence rule. Exact filtering compares the complete domain, so example.com does not include sub.example.com or example.com.evil.test. Unsupported address-like tokens are skipped and counted; partial ASCII suffixes are not recovered from Unicode local parts.

A sample with duplicates and skipped tokens

With input John@Example.COM John@example.com john@example.com, deduplication keeps John@Example.COM and john@example.com. The domain difference compares equal; the local-case difference stays distinct.

Supported candidates and explicit limitations
InputResult or scope
o'hara@example.comAccepted ASCII dot-atom
élise@example.comSkipped whole token, not lise@example.com
a..b@example.comSkipped malformed dot-atom

Reviewing exports and preparing lists

Review text exports

Collect supported candidates from text you are authorized to inspect.

Prepare a list

Compare duplicates and grouping before exporting the visible results.

Check a sample

Include punctuation, case and unsupported syntax before processing the full text.

What the scanner does not cover

The scanner supports common ASCII unquoted local parts up to 64 characters and dot-separated ASCII domain labels. It does not claim every valid email syntax. Punctuation at the end of a domain-like token is treated as surrounding prose. It does not decode HTML entities or obfuscation. Selection clears on text, dedupe or filter changes.

Input is limited to 1,000,000 UTF-16 code units. Empty or failed results are not exported. If Copy fails, select the text manually; text/options/selection changes clear stale feedback. Extraction runs in your browser and the pasted text is not uploaded for it; the Privacy Policy covers everything else the site collects.

Comparing the source with the result

Inspect the source and result together, especially after optional transformations. RFC 5321 distinguishes mailbox local-part case from domain case. This tool's supported subset is stated separately.

Share This Tool

Help teams extract email addresses from text for free!