Email and link extractor
Paste any text, such as an email thread, a web page or a spreadsheet export, and pull out just the email addresses, links or numbers.
This free email, URL and number extractor works in your browser. Everything runs in your browser. What you type is not sent anywhere. All inputs and calculations run locally on your device without server uploads; details on browser processing and storage are set out in the privacy policy.
What it finds
| Option | Matches |
|---|---|
| Email addresses | name@example.com, including international addresses |
| Links | Anything starting with http:// or https:// |
| Domain names | example.com, sub.example.co.in |
| Phone numbers | Numbers of 7 digits or more, with or without +country code, spaces, dots or dashes |
| Dates | 2026-10-19, 19/10/2026, 10.19.26 |
| IP addresses | IPv4 such as 192.168.1.1 |
Use it responsibly
Use extracted contact details only in ways the people concerned would expect. Sending marketing email to addresses collected from the web breaks anti-spam laws in most countries, including the CAN-SPAM Act, the GDPR and India’s DPDP Act.
Worked example: Extracting unique emails and URLs from a raw email header and chat dump
Suppose you paste a messy block of text copied from a support thread or webpage source:
Contact CC: "Dev Team" <OPS@Example.com>, billing@example.com,
or visit https://status.example.com/incidents?id=42 (backup: ops@example.com).
Docs at https://docs.example.com/guide.
- Extracted emails (with Lowercase and Remove duplicates ticked):
Notice thatops@example.com billing@example.comOPS@Example.comandops@example.comare normalized to lowercase before deduplication so you get 2 unique addresses instead of 3, and the trailing period afterops@example.com).is stripped cleanly. - Extracted URLs:
Trailing punctuation marks (like the closing parenthesishttps://status.example.com/incidents?id=42 https://docs.example.com/guide)and sentence period.) are stripped from the end of the URLs.
Limits and what this tool cannot do
- Matches literal text patterns only (does not de-obfuscate
user [at] domain [dot] com): If a web page obscures email addresses ascontact (at) example (dot) comto block scrapers, replace(at)with@and(dot)with.in Find and Replace first. - Does not verify whether an email mailbox exists (no SMTP ping): Extraction is purely lexical inside your browser; it does not look up DNS MX records or connect to mail servers.
- Relative links (
/about/,../index.html): URL extraction matches fullhttp://andhttps://web addresses, not relative file paths.
Questions
Does it find emails written as “name at domain dot com”?
No. Only addresses in their normal form are found.
Why is a number missed?
Phone numbers shorter than 7 digits are skipped, to avoid matching prices and years. Use Numbers to get every number.
Is my text uploaded?
No. Everything runs in your browser. What you type is not sent anywhere.
Why should I tick 'Lowercase' before removing duplicate emails?
Under RFC 5321, domain names are always case-insensitive and in practice almost all mail providers treat the local part (User@ vs user@) case-insensitively too. Lowercasing first ensures Alice@Company.com and alice@company.com merge into a single entry.
How does the extractor avoid including the period at the end of a sentence in a URL?
When a URL appears at the end of an English sentence (Visit https://example.com/docs.), the parser strips trailing sentence punctuation (., ,, ;, ), ]) that is not balanced inside the URL.
Can I export the extracted emails as a comma-separated list for an email client's BCC field?
Yes. Choose the comma-separated output option (or copy one-per-line into spreadsheet rows) to paste directly into Gmail or Outlook.