Question 1

Which URL schemes are supported?

Accepted Answer

http://, https:// and ftp://. These cover virtually every URL you'll see in the wild; mailto, tel and javascript links are intentionally excluded.

Question 2

Will it match URLs without a protocol like example.com?

Accepted Answer

No — bare-domain references are too easy to confuse with file extensions and ordinary words. To convert bare domains into URLs, prefix them with https:// using Find & Replace first.

Question 3

How does it handle trailing punctuation?

Accepted Answer

We trim trailing ., ,, ;, :, !, ?, ), ] and } so a URL inside a sentence isn't ruined by the surrounding punctuation.

Question 4

Will it pick up URLs inside HTML or Markdown?

Accepted Answer

Yes — the regex doesn't care about the surrounding markup, so URLs inside , Markdown links or plain prose are all matched.

Question 5

Can I get only the hostnames?

Accepted Answer

Toggle 'Hostnames only' to reduce each URL to its hostname. Useful for analytics or building an allowlist.

Question 6

Are duplicates removed?

Accepted Answer

Toggle 'Deduplicate' on to keep only the first occurrence of each URL. Off by default so you can count the frequency yourself.

Question 7

Will it match query strings and fragments?

Accepted Answer

Yes — everything from the protocol up to the next whitespace is captured, including ?query=value and #fragment.

Question 8

Is my text uploaded?

Accepted Answer

No — URL extraction is a pure JavaScript regex in your browser. Nothing leaves your device.

Question 9

Will it handle URL-encoded characters?

Accepted Answer

Yes — percent-encoded characters (%20, %2F) pass through unchanged in the extracted URL. Decode them later with our URL Encoder/Decoder if you need the human-readable form.

Question 10

How big a text can I scan?

Accepted Answer

Several megabytes of text scans in well under a second. The match output renders on demand, so even tens of thousands of URLs stay responsive.