Why does the regex miss some URLs?

URLs can contain unusual characters (parentheses in Wikipedia URLs, commas, semicolons). A simple regex misses edge cases. For robust extraction, use a URL-aware tokenizer or iterate candidates through a URL parser and keep those that parse successfully.

How do I avoid matching email addresses?

Email addresses contain @ but no scheme. Match only URLs with an explicit scheme (http://, https://, ftp://) to exclude emails. If you need both, use separate patterns and merge results.

TASK

Extract all URLs from a block of text

Find every URL (http, https, ftp) in unstructured text and list them for validation, deduplication, or batch processing.

1

URLs embedded in prose, logs, or documents are hard to spot manually. A regex scan finds all http(s) URLs, which you can then validate, deduplicate, or process in bulk.
2

Regex Tester →
Use a URL-matching pattern (e.g. https?://[^\s<>"']+). The tool highlights all matches in the input text and lists them.
3

Regex Replace →
To transform URLs (e.g. add tracking params, rewrite domain), use regex-replace with a capture group and replacement template.
4

URL Parser →
Parse each extracted URL to decompose it into protocol, host, path, query, and fragment for structured processing.

Frequently asked questions

Why does the regex miss some URLs?: URLs can contain unusual characters (parentheses in Wikipedia URLs, commas, semicolons). A simple regex misses edge cases. For robust extraction, use a URL-aware tokenizer or iterate candidates through a URL parser and keep those that parse successfully.
How do I avoid matching email addresses?: Email addresses contain @ but no scheme. Match only URLs with an explicit scheme (http://, https://, ftp://) to exclude emails. If you need both, use separate patterns and merge results.