Part of Text tools: See all Text tools.
What is Extract URLs?
Extract URLs scans a block of text and pulls out every URL it finds — HTTP, HTTPS, FTP, and other protocols. It detects full URLs even when embedded in paragraphs, HTML, JSON, or messy unformatted text.
How to use Extract URLs
- Paste any text containing URLs — emails, HTML source, documents, logs, or raw data.
- Click 'Extract URLs' to scan the entire text for valid URLs.
- View the deduplicated list of extracted URLs.
- Copy all URLs or download them as a list for further processing.
Why use this tool?
Manually picking out URLs from a long email thread, HTML page, or log file is time-consuming and error-prone. This URL extractor finds every link in your text automatically, producing a clean list you can audit, visit, or import into a tool.
FAQ
- What URL formats does it detect?
- It detects URLs starting with http://, https://, ftp://, and other standard protocols. URLs with query strings, fragments, and paths are fully captured.
- Does it remove duplicate URLs?
- Yes, duplicate URLs are automatically removed so you get a unique list of links.
- Can it extract URLs from HTML source code?
- Yes, it extracts URLs from href attributes, src attributes, and any other place a URL appears in the HTML text.
- Does it validate whether the URLs are live?
- No, the tool extracts URLs from text but does not check whether they are reachable. It focuses on finding and listing them.
- Is my pasted text kept private?
- Yes, all processing happens in your browser. Your text is never sent to any server.
Extract URLs — In-Depth Guide
URL extraction automatically pulls all hyperlinks from a block of text, HTML source code, document content, or any other text input for organized review and analysis. SEO specialists and digital marketers extract URLs from competitor pages to thoroughly analyze backlink profiles, content linking strategies, and overall site structure. Marketing teams pull links from draft email campaigns and newsletters to carefully verify that all destination URLs are correct and properly tagged with tracking parameters before sending.
Academic researchers and students extract URLs from published papers, journal articles, and reference lists to efficiently build comprehensive, organized link collections for further study, citation management, and analysis. Rather than manually clicking through and individually copying each link one at a time from lengthy documents, automated bulk extraction saves considerable time and effort while reducing the chance of missed links. Review all extracted URLs for duplicates and broken links before adding them to your research database.
Web developers and site migration specialists extract URLs from HTML source code during website migrations, platform transitions, or domain changes to systematically verify that all internal links correctly point to the proper new destination addresses. Missing or broken links after a site migration negatively impact both user experience and search engine rankings and can take months to recover from. Building a complete URL inventory from the source code makes comprehensive migration testing systematic and thorough.
Content auditors, compliance officers, and editorial teams extract all URLs from a document, webpage, or email template to methodically check for outdated references, expired domains, affiliate link compliance issues, or potential policy violations. Having a clean, consolidated, and deduplicated list of every URL contained in the source content makes it straightforward to verify each destination individually and systematically without having to read through the entire source text manually searching for embedded links.
Why scraping links by hand fails
Links and email addresses hide in the worst places. They sit mid-sentence inside a support ticket, wrapped in angle brackets in a raw email header, repeated on every line of a scraped HTML dump, or buried in a multi-megabyte log. Hunting them by eye is slow and incomplete. You miss the third copy that differs by one query parameter. You copy a URL and accidentally keep the trailing period from the sentence that followed it. You open the page later and wonder why half the addresses bounce. Automatic extraction turns that messy paste into a clean, one-per-line list you can audit, sort, or feed into the next step.
This page is a small browser tool for that job. Paste any text into the box, click Extract URLs & Emails, and read the matches in the output. The scan runs entirely in your tab with two regular expressions: one for http:// and https:// links, one for email-shaped strings. Matches are deduplicated. Trailing sentence punctuation is stripped from URLs. Nothing is uploaded. There is no /api/extract-urls endpoint; a request to that path returns 404. Your paste never leaves the browser.
What the Extract button actually does
When you click the button, the page reads the textarea, runs a URL regex and an email regex against the full string, cleans each URL match, builds a unique set of URLs, builds a unique set of emails, then joins both lists with newlines — URLs first, emails second. Empty input produces an empty output. Order inside each group follows first appearance in the pasted text. That is the whole behaviour. There is no crawl, no HEAD request to check whether a link resolves, and no attempt to fetch pages or follow redirects.
The URL pattern is deliberately narrow: it only matches strings that begin with http:// or https://, then continues until it hits whitespace or a character that is illegal in that part of a URL (angle brackets, quotes, braces, pipes, and similar). Bare hostnames such as www.example.com without a scheme are not extracted. Schemes such as ftp://, mailto:, file://, or custom app deep links are also skipped. If your paste only contains scheme-less web addresses, this tool will return nothing for the URL half — paste a version that includes http or https, or add the scheme yourself before extracting.
Trailing punctuation on URLs
Prose loves to end a sentence with a link: see https://example.com/docs. The period belongs to the sentence, not the path. Without cleanup, a naive match keeps the dot and you get a broken address. After matching, this tool strips a run of trailing . , ; : ! ? and closing ) from each URL. That covers the common “link at end of sentence” and “link inside parentheses” cases without inventing a full HTML parser.
It will not fix every boundary. A URL that legitimately ends with a closing parenthesis as part of the path (rare, but legal in some systems) may lose that character. A match that runs into neighbouring markup without a clear separator may look truncated. Always glance at the output before you treat it as authoritative, especially when the source is messy HTML pasted as text rather than clean prose.
Email addresses
Emails are found with a straightforward pattern: local-part characters, an @, a domain with dots, and a final label of at least two letters. That catches the addresses people actually paste into tickets and docs. It is not a full RFC 5322 parser. Exotic quoted local-parts, comments inside addresses, and internationalised domains outside the ASCII patterns the regex expects can be missed or partially matched.
Emails are deduplicated separately from URLs, then appended after the URL list. Case is preserved as found; the uniqueness check is case-sensitive on the raw match string, so You@Example.com and you@example.com would both appear if both spellings exist in the input.
Deduplication and output shape
Real documents repeat the same link constantly — navigation chrome in scraped HTML, a tracking URL pasted through an email thread, a docs link in every log line. Returning every raw occurrence produces noise. This tool keeps the first occurrence of each exact URL string and each exact email string. Near-duplicates that differ by a trailing slash, a query parameter, or http versus https stay distinct, because they are different strings. That is intentional: collapsing them would hide real differences you might need to audit.
The output is plain text: one match per line, URLs block first, emails block second, no labels and no counts. Copy the box into a spreadsheet, a checklist, or another browser tool. If you only wanted URLs, delete the email lines. If you only wanted emails, ignore the URL block. There is no separate “emails only” mode because the single combined list is enough for the common jobs and keeps the UI honest and small.
What this tool does not do
Be clear about the limits. It does not crawl websites or follow links. It does not validate that a URL returns HTTP 200 or that an email inbox exists. It does not parse HTML into a DOM and walk every href and src — if you paste rendered page text, you get the visible links that still carry their schemes; if you paste raw HTML source, you get whatever http(s) strings appear in attributes and text, which is often richer. It does not extract bare domains, IP addresses without a scheme, or non-http schemes. It is regex-based, so exotic or deliberately obfuscated URLs (spaces inserted to dodge filters, HTML entities breaking the scheme, links split across lines) can be missed.
Those limits are features for privacy and speed as much as they are constraints. A crawl-and-validate service would need to send your text (or your target URLs) to a server and wait on the network. This page finishes instantly in the tab and never creates a server-side copy of what you pasted.
Common jobs this page is built for
Logs and error dumps. Paste a chunk of application or CDN logs and pull every request URL the noise buried. Email threads and tickets. Extract the links and addresses people mentioned without clicking anything suspicious. Scraped HTML saved as text. Turn a saved page source or a content-export dump into a link list for a broken-link review. Docs and changelogs. Harvest citation and download links from a long markdown or plain-text document. Marketing or CRM exports. Pull tracking URLs and contact emails out of a messy CSV cell or pasted report when the column split failed.
Privacy: everything stays in the browser
Paste buffers often contain production URLs with tokens in the query string, internal hostnames, or customer email addresses. Sending that material to a remote “extractor API” creates an unnecessary copy. This tool does not do that. The regexes run in page JavaScript. There is no upload field, no server conversion step, and no account. Close the tab and the input is gone with it. The page is free and needs no signup. Claims on this page match the buttons you see: one Extract control, URLs then emails, one match per line, http(s) only, trailing punctuation stripped, duplicates removed.
Related developer tools on this site
URL lists often sit next to other text transforms. Use URL Encode / Decode when a pulled link still has percent-encoding you need to read, or when you must re-encode a value before rebuilding a query string. Use Base64 Encode / Decode when a parameter inside an extracted URL turns out to be opaque Base64 rather than plain text. Use the Hash Generator when you need a checksum of a URL string for dedupe outside this page. Use the JSON Formatter when the paste is a JSON blob and you want to inspect structure before or after pulling links from it. Those pages are on the same indexed keep-list cluster and keep your text in the browser.
Paste the full source, extract once, skim for odd boundaries, then move on. When a document is full of links you cannot afford to miss by eye, a single local pass is faster — and safer — than copying them one at a time.
Also try
Related tools that work well with this one: