|
Developer Utilities 100% Client-Side · 0 Bytes Sent to Server Instant In-Memory Execution

URL Extractor

Extract all hyperlinks and web addresses from HTML code, server logs, and documents. Automatically deduplicates links and formats them as a clean list.

Step-by-Step Instructions

1

Paste Raw Text or Source Code

Paste text, markdown, HTML source, server logs, or sitemaps into the input editor.

2

Select Protocol & Domain Filters

Choose to extract HTTP, HTTPS, FTP, or relative URL paths, and filter by specific domain names.

3

Configure Extraction Scope

Remove duplicate URLs, strip query strings/UTM parameters, or sort URLs alphabetically.

4

Copy or Download URL List

Copy clean URLs as a line-by-line list, hyperlinked HTML, or export as a .txt / .csv file.

Key Features & Capabilities

  • RFC 3986 compliant URL extraction regex capturing `http://`, `https://`, `ftp://`, and `www.` web addresses
  • Automatic URL parameter stripper (removes tracking parameters like `?utm_source=...` and `fbclid`)
  • Domain and top-level domain (TLD) grouping and frequency analysis
  • Anchor tag (`<a href="...">`) and image source (`<img src="...">`) HTML extraction

Frequently Asked Questions

How does the URL extractor handle URLs embedded in HTML links and markdown?

The extractor parses standard web links, HTML `<a href="...">` attributes, markdown `[link](url)` syntax, and bare plaintext URLs, extracting the clean destination web addresses while discarding surrounding code syntax.

Can this tool strip tracking parameters (UTM tags, fbclid, gclid) from extracted URLs?

Yes. You can enable the 'Strip Query Parameters' filter to automatically clean tracking tokens (`utm_source`, `utm_medium`, `utm_campaign`, `gclid`, `fbclid`, `ref`), returning canonical root URLs.

How does the tool handle relative URLs (e.g., /about or /blog/post)?

By default, the tool extracts absolute URLs (`https://...`). You can enable relative URL extraction and provide a base domain (e.g., `https://example.com`) to automatically convert relative paths (`/contact`) into fully qualified absolute URLs (`https://example.com/contact`).

Is URL extraction executed client-side?

Yes. All pattern matching and URL parsing runs entirely in your local browser's memory without sending content to any server.

Discover complementary online tools in the same workflow.