url regex

URL regex

The idea here is to validate URLs in a practical and visual way without opening the full builder library.

Test text

Matches2

https://junyo.dev http://example.com/path?ok=1 ftp://legacy.example

Explanation

Match 'h', then 't', then 't', then 'p', then 's', then optional, then ':', then literal '/', then literal '/', then one char from [\w.-], then one or more times, then group (?:\/[\w./?%&=-]*), then optional

hliteral 'h'
tliteral 't'
tliteral 't'
pliteral 'p'
sliteral 's'
?optional
:literal ':'
\/escaped '/'
\/escaped '/'
[\w.-]character class — any single char in the set
+one or more times
(?:\/[\w./?%&=-]*)non-capturing group
?optional

Everything runs locally in your browser. Nothing is sent to a server.

Continue in the tool

Open full tool

More pages for this tool

Scope of this regex

The pattern focuses on HTTP/HTTPS URLs for quick visual validation.
As with email, the intent is pragmatic: good coverage without becoming an unreadable monster.

URL examples

Simple HTTPS

Input: https://junyo.dev
Expected output: match

Most common case.

FTP out of scope

Input: ftp://legacy.example
Expected output: sem match

Shows the preset is focused on web URLs.

Full tool FAQ

Does the tool test regex patterns with flags and examples?

Yes. The idea is to let you build the expression, apply flags and inspect matches in real time, which is especially useful for debugging, learning and fine-tuning patterns.

What is regex?

What is regex used for in practice?

What are regex flags?

Can regex validate any complex format?

Why do some regex patterns become too slow?

Is there such a thing as a perfect email regex?

What is the most common mistake when learning regex?

Frequently asked questions

Does this regex cover every possible URL?

No. It covers the most common HTTP/HTTPS web scenarios well.

Can I use other flags?

Yes. The flags field remains available for testing.