We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Automatically identify and extract all valid email addresses from any text, with optional result counting.
Enter text to start extraction
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
Paste text and the extractor scans for substrings matching its ASCII pattern: letters, digits, periods, underscores, and hyphens before @; letters, digits, periods, and hyphens in the domain; then a dot and a 2-to-6-letter suffix. Results appear as a newline-separated list with a count.
This is a text matcher, not a full parser for every valid Internet email address. RFC 5322 allows broader forms, including quoted local parts and domain literals. The page neither recognizes every standards-valid form nor checks if a mailbox exists or accepts mail. A match means only that characters fit this pattern.
Duplicate removal starts enabled. It keeps the first exact match and preserves result order. Comparison is case-sensitive, so Sales@example.com and sales@example.com remain separate. Turn duplicate removal off to retain repeated matches. With removal enabled, the count is distinct matching strings; with it off, the count is occurrences.
The output is a plain list for copying. It does not group by domain, normalize capitalization, identify a person, or export a spreadsheet.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Copy text from a note, message, log, or spreadsheet cell into the input. The page takes pasted text only; it does not upload documents or perform OCR.
Leave removal on to make a list of distinct exact strings. Turn it off if every appearance in the source is important.
Review order, capitalization, and nearby source context, then copy the newline-separated list.
Before importing or contacting anyone, use the checks your organization requires and confirm each address against its original context.
Paste alex@example.com; alex@example.com; Alex@example.com. With removal on, the repeated lowercase string appears once and the capitalized string remains separate. With removal off, the lowercase one appears twice. A plus-tag form such as name+tag@example.com is outside the local-part character set, so inspect any returned substring against its source.
Use cases
See how the tool fits into real work and everyday tasks.
Extract common-form strings from a short ticket excerpt, then confirm which person or issue each belongs to before updating a record.
Keep repeated matches while checking a test log, and manually remove example or placeholder addresses.
Combine text and deduplicate exact matches. Different capitalization and aliases remain separate for a human review rule.
Q&A
Find concise answers to common questions and confusing cases.
No. The tool does not query DNS, contact a mail server, or send a verification message. A match could be a typo, inactive mailbox, or placeholder.
The matcher excludes + before the at-sign, so it may miss the whole string or return a substring after the plus. Compare it with the original text.
No. It accepts typed or pasted text. Copy selectable document text first; scanned images need OCR in another workflow and should be checked for errors.
Notes
Review scope, result limitations, and important precautions before use.
A pattern match is not proof of deliverability, ownership, or consent to receive a message. Do not use results as contact authorization. When text includes customer, employee, or other personal information, paste only what is needed and follow the privacy and communication rules that apply to your organization.
Related
Discover related tools, collections, and available API capabilities.