Visual regex workbench

CreateRegex v4

Build, test, explain and master regex with visual tools, guides, examples and a growing regex library.

Regex guide

Regex Quantifiers

Quantifiers control how many times a token can repeat. They are essential for matching optional characters, repeated digits, variable-length words, lists, formats and many real-world patterns.

6 guides
Why quantifiers are essential Choosing the right quantifier Greedy versus lazy matching Quantifiers and performance Fixed-length versus variable-length patterns Common quantifier mistakes
8 key concepts
Zero or more with * One or more with + Optional with ? Exact repetition with {n} At least n repetitions with {n,} Between n and m repetitions with {n,m} Greedy quantifiers Lazy quantifiers
Learn more
Regex Performance Testing Regex Common Regex Mistakes Character Classes
Open the regex builder

Why quantifiers are essential

Without quantifiers, regular expressions could only match fixed sequences of characters. Quantifiers introduce repetition, making regexes flexible enough to validate real-world data.

Whether you are matching phone numbers, identifiers, dates or passwords, quantifiers define how many characters are expected and which parts of a pattern are optional.

Understanding quantifiers is one of the biggest steps towards writing concise and maintainable regular expressions.

Choosing the right quantifier

Several quantifiers may appear to solve the same problem, but choosing the most appropriate one improves readability and reduces mistakes.

For example, + clearly expresses "one or more", while {1,} achieves the same result with more visual noise.

Whenever possible, prefer the simplest quantifier that accurately describes the expected input.

Greedy versus lazy matching

Greedy quantifiers consume as much text as possible, while lazy quantifiers stop as soon as the overall pattern can succeed.

Understanding this difference is essential when working with HTML, quoted strings or nested structures.

Many unexpected regex results are caused by using a greedy quantifier where a lazy one was intended.

Quantifiers and performance

Poorly chosen quantifiers can dramatically increase backtracking and slow down pattern matching.

Nesting greedy quantifiers or applying them to very broad character classes should be avoided whenever possible.

Writing explicit patterns often produces faster and more predictable regular expressions.

Fixed-length versus variable-length patterns

Some inputs require an exact number of characters, while others allow a range of acceptable lengths.

Quantifiers such as {4} and {8,20} make these constraints explicit and easy to understand.

Using precise repetition limits generally produces more reliable validation patterns.

Common quantifier mistakes

One of the most common beginner mistakes is using .* when a much more specific expression would be safer.

Another frequent error is forgetting that * allows zero occurrences, while + requires at least one.

Choosing the correct quantifier usually makes a regex easier to understand, easier to debug and less prone to unexpected matches.

Related regex patterns

🧩 Pattern guide

Email Regex

Test and understand practical email patterns you can adapt.

16 examples

Open pattern guide →
🧩 Pattern guide

Credit Card Regex

Validate credit card number formats and understand regex limitations.

15 examples

Open pattern guide →

Continue learning

📘 Recommended guide

Regex Performance

Quantifiers can strongly affect regex performance, especially when they are nested, ambiguous or applied to large inputs.

Read the complete guide →
📘 Recommended guide

Testing Regex

Quantifier-based patterns should be tested with minimum length, maximum length, empty input and values just outside the accepted range.

Read the complete guide →
📘 Recommended guide

Common Regex Mistakes

Many regex mistakes come from using *, + or .* too broadly without considering anchors, boundaries or backtracking.

Read the complete guide →
📘 Recommended guide

Character Classes

Quantifiers almost always work together with character classes.

Learning both concepts together makes complex regexes much easier to understand.

Read the complete guide →

Zero or more with *

The * quantifier means zero or more repetitions.

It can match nothing, one occurrence or many occurrences.

ab*c
Quick test
Open in Visual Builder

One or more with +

The + quantifier means one or more repetitions.

Unlike *, it requires at least one occurrence.

ab+c
Quick test
Open in Visual Builder

Optional with ?

The ? quantifier means zero or one occurrence.

It is useful for optional characters or optional parts of a pattern.

colou?r
Quick test
Open in Visual Builder

Exact repetition with {n}

The {n} quantifier requires exactly n repetitions.

It is often used for fixed-length values such as PIN codes, years or identifiers.

\d{4}
Quick test
Open in Visual Builder

At least n repetitions with {n,}

The {n,} quantifier means at least n repetitions.

It is useful when a value must have a minimum length but no strict maximum.

\w{5,}
Quick test
Open in Visual Builder

Between n and m repetitions with {n,m}

The {n,m} quantifier matches between n and m repetitions.

It is commonly used for usernames, passwords, postal codes or bounded identifiers.

\w{3,8}
Quick test
Open in Visual Builder

Greedy quantifiers

Quantifiers are greedy by default in most regex engines.

This means they try to match as much text as possible while still allowing the whole pattern to succeed.

<.+>
Quick test
Open in Visual Builder

Lazy quantifiers

Adding ? after a quantifier usually makes it lazy.

Lazy quantifiers try to match as little text as possible while still allowing the pattern to succeed.

<.+?>
Quick test
Open in Visual Builder

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. 16 examples URL Regex Validate or extract URLs with interactive examples. 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 Credit Card Regex Validate credit card number formats and understand regex limitations. 15 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 Regex Limitations Understand what regex can and cannot validate. Guide Testing Regex Learn how to test regex patterns properly. Guide Regex Compatibility Understand regex differences between engines and languages. Guide Regex Performance Learn how to write fast and efficient regex patterns. Guide Input Validation Best Practices Build reliable and secure input validation. Guide Common Regex Mistakes Avoid the most common regex mistakes. Guide JavaScript Lookbehind Understand lookahead, lookbehind and compatibility limits. 2 examples JavaScript Regex vs PCRE Compare regex engines, flags and feature support. 2 examples Character Classes Understand regex character classes and shortcuts. 10 examples Groups Understand regex groups and captures. 9 examples Anchors Understand regex anchors and boundaries. 8 examples Alternation Understand regex alternatives and OR logic. 8 examples Lookarounds Understand lookaheads and lookbehinds. 8 examples