Visual regex workbench

Advanced Visual Regex Builder v3.8

Build, import, explain, test and share regex visually.

Regex guide

URL Regex Pattern

URL matching can be simple or extremely strict depending on your goal. This page gives you a practical URL regex for common web addresses.

2 examples
Simple URL regex HTTPS-only URL regex
6 guides
Why use a URL regex? What is a valid URL? HTTP vs HTTPS URL validation Should a regex validate URLs completely? Common URL validation mistakes When to use URL regex validation
Open the regex builder

Simple URL regex

A practical URL regex with optional http or https protocol.

Suggested pattern

^(https?:\/\/)?([\w-]+\.)+[\w-]{2,}(\/.*)?$
Quick test
Open in Visual Builder

What it matches

  • https://example.com
  • example.org/page

Common limitations

  • Does not validate every possible URL.
  • Does not support every internationalized domain case.

HTTPS-only URL regex

A stricter URL regex that requires HTTPS.

Suggested pattern

^https:\/\/([\w-]+\.)+[\w-]{2,}(\/.*)?$
Quick test
Open in Visual Builder

What it matches

  • https://example.com
  • https://docs.example.com/path

Common limitations

  • Rejects URLs without protocol.
  • Rejects http:// URLs.

Why use a URL regex?

URL regex patterns are commonly used to validate website addresses entered by users in forms, APIs, CMS platforms and configuration files.

They help detect obvious formatting errors before a URL is stored, processed or displayed.

What is a valid URL?

A URL typically contains a protocol such as HTTP or HTTPS, a domain name and optionally a path, query parameters or fragments.

Modern URLs can also contain internationalized domain names, ports and encoded characters, making complete validation more complex than it appears.

HTTP vs HTTPS URL validation

Some applications accept any valid URL, while others require HTTPS for security reasons.

Using a dedicated HTTPS regex can help enforce secure links and prevent users from submitting insecure HTTP addresses.

Should a regex validate URLs completely?

Regex is useful for detecting obvious formatting mistakes, but complete URL validation often requires additional checks.

For example, a regex cannot confirm whether a domain actually exists or whether a web server is reachable.

Common URL validation mistakes

Many URL regex patterns are either too permissive or too restrictive.

A good balance is to accept common real-world URLs while avoiding unnecessary complexity and false negatives.

When to use URL regex validation

URL regex patterns are useful for website submissions, social media profiles, webhook configuration, API settings and link management tools.

They provide quick client-side validation before performing deeper server-side checks.

More Regex Guides

Password Regex Validate password strength, length and security policies. 4 examples Email Regex Test and understand practical email patterns you can adapt. 2 examples Phone Number Regex Validate international, French, US and E.164 phone numbers. 5 examples Username Regex Validate usernames, handles, slugs and account names. 6 examples Date Regex Validate DD/MM/YYYY, ISO dates and timestamps. 5 examples IP Address Regex Validate IPv4, private IP ranges, CIDR notation and IPv6 basics. 5 examples UUID Regex Validate UUID v4, UUID v1-v5 and UUIDs without hyphens. 4 examples Hex Color Regex Validate CSS hex colors like #fff, #ffffff and alpha colors. 6 examples Domain Name Regex Validate domains, subdomains, TLDs and lowercase domain names. 6 examples Slug Regex Validate SEO-friendly slugs and URL-safe identifiers. 5 examples Regex Cheatsheet Quickly find anchors, classes, groups and quantifiers. 5 examples Regex Tutorial Learn regular expressions step by step from the basics. 3 examples JavaScript Lookbehind Understand lookahead, lookbehind and compatibility limits. 2 examples JavaScript Regex vs PCRE Compare regex engines, flags and feature support. 2 examples