How to Use Regex — Regular Expressions Tutorial

Q: What does the dot (.) metacharacter mean in regex?

In regex, a dot (.) matches any single character except a newline by default. For example, the pattern 'c.t' matches 'cat', 'cut', 'cot', and even 'c5t'. If you want to match a literal dot — as in a file extension or domain name — you must escape it with a backslash: \. so 'file\.txt' matches only 'file.txt' and not 'fileXtxt'.

Q: What is the difference between + and * quantifiers?

The asterisk (*) means 'zero or more occurrences' of the preceding element. The plus sign (+) means 'one or more occurrences'. For example, 'go*gle' would match 'ggle', 'gogle', 'google', and 'gooooogle'. But 'go+gle' would only match 'gogle', 'google', and longer versions — not 'ggle', because + requires at least one occurrence of 'o'. Use + when the element must appear at least once, and * when it is optional.

Q: What are regex flags and how do I use them?

Flags (also called modifiers) change how a regex engine interprets the pattern. The most common are: g (global) — find all matches in a string instead of stopping after the first; i (case insensitive) — treat uppercase and lowercase as identical, so 'hello' matches 'Hello', 'HELLO', etc.; m (multiline) — make ^ and $ match the start and end of each line rather than the entire string. In JavaScript, flags appear after the closing slash: /pattern/gi means global and case-insensitive.

Q: How do I write a regex to validate an email address?

A practical email validation regex for most use cases is: ^[a-zA-Z0-9._%+\-]+@[a-zA-Z0-9.\-]+\.[a-zA-Z]{2,}$. Breaking it down: ^ anchors to start of string; [a-zA-Z0-9._%+\-]+ matches the local part (letters, digits, dots, underscores, percent, plus, hyphen, one or more); @ matches the literal at-sign; [a-zA-Z0-9.\-]+ matches the domain name; \. matches a literal dot; [a-zA-Z]{2,} matches the TLD (two or more letters); $ anchors to end. Note that no regex can fully validate email per the RFC spec, but this catches the vast majority of invalid formats.

Use our free tool — no sign-up required.

Regex Tester & Validator — Free Online Tool

What is a regular expression?

A regular expression is a sequence of characters that defines a search pattern. You write the pattern, and a regex engine scans through text to find strings that match it. The pattern can be as simple as a literal word — error matches the word "error" anywhere in a string — or as complex as a full email or URL validator spanning dozens of characters. Regex engines are built into virtually every modern programming language (JavaScript, Python, Java, PHP, Go, Ruby) and many text editors and command-line tools like grep and sed.

The key insight is that regex patterns are composed of two kinds of characters: literals (characters that match themselves, like a, B, 7) and metacharacters (special characters with reserved meanings, like . * + ? ^ $ {} [] () and |). Learning what each metacharacter does is the foundation of reading and writing regex.

Essential metacharacters and what they do

Here is a quick reference for the most frequently used regex building blocks:

. — Matches any single character except a newline. c.t matches "cat", "cut", "c5t".
* — Zero or more of the preceding element. go*gle matches "ggle", "gogle", "google".
+ — One or more of the preceding element. go+gle matches "gogle" and "google" but not "ggle".
? — Zero or one of the preceding element — makes it optional. colou?r matches both "color" and "colour".
^ — Anchors the match to the start of a string (or line in multiline mode).
$ — Anchors the match to the end of a string (or line in multiline mode).
{n,m} — Matches between n and m repetitions. \d{3,5} matches 3, 4, or 5 digits.
[] — Character class. [aeiou] matches any single vowel. [0-9] matches any digit.
[^] — Negated character class. [^aeiou] matches any character that is not a vowel.
() — Capturing group. Useful for extracting parts of a match or applying quantifiers to a group of characters.
| — Alternation (OR). cat|dog matches "cat" or "dog".
\d — Shorthand for [0-9] — any digit.
\w — Shorthand for [a-zA-Z0-9_] — any word character.
\s — Any whitespace character (space, tab, newline).

How to write and test a regex — step by step

Building a regex from scratch is easiest when you follow a methodical process:

Step 1: Define what you want to match. Write down two or three sample strings that should match and two or three that should not. For example, for a US phone number you might want to match 555-867-5309 and (555) 867-5309 but not 123 or not a phone.
Step 2: Break the pattern into parts. A US phone number has an optional area code in parentheses, followed by a 3-digit exchange, a separator, and a 4-digit number. Map each part to a regex token: ($\d{3}$\s?)?\d{3}[-.\s]\d{4}.
Step 3: Test against your samples in the Regex Tester. Paste your pattern and test string into the tool. Watch which parts match and which do not. Most regex testers highlight matches in real time and show capture group contents separately — use this to diagnose issues.
Step 4: Refine and add anchors. If your pattern is for validation (the entire string must match, not just a substring), wrap it in ^ and $ anchors. Add flags as needed — the i flag for case-insensitive matching, g to find all matches rather than just the first.

Common regex patterns for everyday tasks

Email: ^[a-zA-Z0-9._%+\-]+@[a-zA-Z0-9.\-]+\.[a-zA-Z]{2,}$
URL: https?://[^\s/$.?#][^\s]*
Date (YYYY-MM-DD): ^\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12]\d|3[01])$
US phone number: ($\d{3}$\s?)?\d{3}[-.\s]\d{4}

Tips and best practices

Escape literal special characters. If you need to match a period, parenthesis, or any other metacharacter as a literal character, escape it with a backslash. \. matches a literal dot; \( matches a literal open parenthesis.
Use non-capturing groups when you do not need the match. (?:pattern) groups characters without creating a numbered capture group. This keeps your capture group indices clean and can improve performance slightly.
Avoid catastrophic backtracking. Patterns like (a+)+ applied to a long non-matching string can cause exponential time complexity. If your regex feels slow, look for nested quantifiers and simplify the structure.
Test with edge cases. Always test empty strings, strings with only whitespace, very long inputs, and Unicode characters. These edge cases expose assumptions in your pattern that could cause bugs in production.

Frequently asked questions

What does the dot (.) metacharacter mean in regex?

A dot matches any single character except a newline by default. The pattern c.t matches "cat", "cut", "cot", and even "c5t". If you want to match a literal dot — as in a file extension or domain name — you must escape it: \.. So file\.txt matches only "file.txt" and not "fileXtxt". The dot is one of the most common sources of accidental over-matching in regex, so always ask yourself whether you want any character or a literal dot.

What is the difference between + and * quantifiers?

The asterisk (*) means "zero or more occurrences" of the preceding element. The plus sign (+) means "one or more occurrences." For example, go*gle would match "ggle", "gogle", "google", and "gooooogle". But go+gle only matches "gogle", "google", and longer versions — not "ggle", because + requires at least one occurrence. Use + when the element must appear at least once, and * when it is optional.

What are regex flags and how do I use them?

Flags change how a regex engine interprets a pattern. The three most common are: g (global) — find all matches instead of stopping after the first; i (case insensitive) — treat uppercase and lowercase as identical; m (multiline) — make ^ and $ match the start and end of each line rather than the entire string. In JavaScript, flags appear after the closing slash: /pattern/gi means global and case-insensitive.

How do I write a regex to validate an email address?

A practical email regex for most use cases is: ^[a-zA-Z0-9._%+\-]+@[a-zA-Z0-9.\-]+\.[a-zA-Z]{2,}$. The local part before @ allows letters, digits, dots, underscores, percent signs, plus signs, and hyphens. After the @ comes the domain name and a dot followed by at least two letters for the TLD. Note that no single regex can perfectly validate email per the full RFC spec — use this to catch obvious formatting errors and confirm via a verification email for critical applications.

Conclusion

Regular expressions reward investment — a few hours of learning metacharacters and quantifiers unlocks a capability you will use for the rest of your career. Start with simple patterns, test them incrementally in a live tester, and build up complexity only as needed. The free Regex Tester highlights matches in real time and shows capture groups, making it the fastest way to go from an idea to a working pattern without switching between tools.

Ready to build your regex? Try our free tool — works instantly in your browser.

Regex Tester & Validator — Try it Free