http · https · ftp · group by domain

Extract URLs from any text

Pull every URL from prose, HTML, or markdown. Filter by protocol, group by domain, dedupe or sort.

URL Extractor Workspace
Input size
162 B
3 lines
URLs found
5
deduped
Protocol
all
filter
Order
source
sort
Protocol
input · any text
output · URLs
https://example.com
http://blog.example.org
ftp://files.example.net/data.zip
www.acme.co.uk
https://api.example.com/v1?query=1
Quick Start

How to extract URLs

Regex-based extraction handling http/https/ftp and bare www. URLs. Trailing punctuation (periods, commas, parens) is stripped automatically.

  1. 01

    Paste text

    Email body, HTML, Markdown — anything.

    Tokenisation is Unicode-aware via \p{L}\p{N} property classes — so accented letters, ideographs, and emoji code points all count correctly.

    anyUTF-8Unicodecode pointslive
    input · textraw · UTF-8
    Visit https://example.com
    loaded · UTF-8UTF-8 · ready
  2. 02

    Filter protocol

    Pick a single protocol or all. Default 'all' includes bare www. patterns.

    httphttpsftp
    protocolhttps
    https://example.com
    filtered
  3. 03

    Sort or group

    'By domain' groups all URLs from the same host together — useful for site-wide link inventory.

    Output preserves the original line endings (\n vs \r\n) and trailing whitespace is reported separately so you can spot diff-only changes.

    sortgroupline endingswhitespacediff-clean
    order · counteddomain · ready
    example.com first
    counted · livecounted
  4. 04

    Copy or download

    Text or CSV with header.

    Copy writes via the Async Clipboard API; downloads ship as text/plain; charset=utf-8 — nothing leaves your tab.

    copycsvclipboardtext/plainblob
    export · copiedready · done
    ✓ Copied
    shipped · ready to shipsuccess
Pro tips

Text-processing fundamentals worth knowing

Tokenise with Unicode classes

Use \p{L}\p{N} with the u flag so accents, ideographs, and emoji count properly.

Normalise line endings

Convert \r\n to \n before diffing or hashing — Windows-vs-Unix endings produce phantom changes.

Mind invisible characters

Zero-width joiners, BOMs, and non-breaking spaces look identical to ASCII space. Strip them before comparison or storage.

Stream don’t slurp

For multi-megabyte text, iterate line-by-line rather than loading everything to memory — keeps the tab responsive.

Choose collation deliberately

Default JS sort is code-point order, not human alphabetical. Use Intl.Collator for locale-aware sorting.

Re-run after normalisation

NFC vs NFD changes byte length but not visible glyphs. String.prototype.normalize() before counts and comparisons.

Use Cases

When to extract URLs

Anywhere link inventory matters.

Audit page links

Find all outbound URLs from copied page source. Tokenisation uses Unicode property classes (\p{L}, \p{N}) with the u flag so accents, ideographs, and emoji code points all count correctly. Surrogate-pair-aware counts mean 🚀 weighs 1, not 2.

Unicode-correct

Markdown link review

Confirm all URLs in a doc before publishing. Result updates as you type — paste and watch totals settle in milliseconds even on multi-megabyte inputs. Heavy work runs through a memoised reducer so the editor never janks.

diff-clean

Log scraping

Pull URLs from log lines for tracing. Output normalises line endings to LF for clean diffs across platforms. Windows-vs-Unix CRLF mismatches disappear, which keeps git blame honest and review comments focused on real changes.

instant counts

Bookmark imports

Extract URLs from a notes export for browser import. Code-point counts are stable across NFC/NFD normalisation. Pair with the Reading Time Calculator to layer scan-time on top of raw counts, useful for editorial budgets and SEO meta-description limits.

platform-aware

RSS lists

Build OPML imports from a feed list copy. All processing runs client-side — paste sensitive or pre-publish copy without it leaving the tab. The clipboard API writes UTF-8 text/plain so it survives transit to any editor or CMS.

code-point-accurate

Security review

Spot suspicious URLs in copied email content. Same input plus same options always produces identical output, so the tool is safe to embed in CI scripts or doc-generation pipelines without race conditions.

lossless
FAQ

Frequently asked questions

http://, https://, ftp://, and bare www.domain — plus query strings and fragments.
No — '.', ',', ')', ']' etc. at the end of URLs are stripped automatically.
No — pattern matches anything that looks URL-shaped.
No. All processing runs locally.
Not auto-decoded — pattern matches literal http/https/ftp.
Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

Sent straight to the maintainers · no account needed
47 in queue·8 shipped this month
Request queued. Thanks!