How to Use the Regex Explainer & Tester
- Enter your regular expression in the pattern field (without the surrounding slashes) and switch the g, i and m flags as needed.
- Type or paste sample text in the test area. Matches highlight instantly, with the total match count and each capture group listed.
- Read the auto-generated explanation below: the pattern is split into tokens and each quantifier, character class, group and anchor is described in plain English. Errors in the pattern are reported with details.
What Is Regex Explainer?
A regular expression (regex or regexp) is a sequence of characters that defines a search pattern. Regex engines match the pattern against text, powering everything from form validation and "find and replace" to log analysis, input sanitization and compiler lexers.
Patterns are built from a small alphabet of constructs: literals match themselves; character classes like [a-z] and \d match sets of characters; quantifiers such as *, +, ? and {n,m} control repetition; anchors ^ and $ assert position; groups ( ) capture sub-matches and enable alternation with |; and lookarounds (?= ) and (?<= ) assert context without consuming characters.
Flags change engine behavior: g (global) finds all matches instead of just the first; i (ignoreCase) makes matching case-insensitive; m (multiline) makes ^ and $ match line boundaries; s (dotAll) makes the dot match newlines; u enables full Unicode mode.
Regex is famously dense — a pattern like ^[A-Z0-9._%+-]+@[A-Z0-9.-]+\.[A-Z]{2,}$ is a working email validator but unreadable to most people at first glance. An explainer decomposes such patterns into tokens and translates each one, which is the fastest way to learn regex or to audit a pattern you inherited. Testing against real sample text at the same time confirms the pattern matches what you intend and nothing you do not.
Common Use Cases
- Form validation patterns. Build and verify regex for emails, phone numbers, URLs or custom IDs before shipping them in frontend or backend code.
- Log and text parsing. Test extraction patterns against real log lines and check capture groups for timestamps, IPs and error codes.
- Search-and-replace scripting. Prototype find/replace regex for sed, VS Code or IDE refactoring with immediate visual feedback.
- Learning and code review. Paste an unfamiliar pattern to get an English walkthrough during code review or while learning regex.
- Debugging unexpected matches. Catastrophic backtracking, greedy quantifiers and missing anchors show up immediately when you test against edge-case strings.
Frequently Asked Questions
Does the regex tester use my browser’s regex engine?
Yes — matching uses the native JavaScript RegExp engine in your browser, so behavior matches what you will get in Node.js, React or any JavaScript application. Results appear instantly as you type.
What does the explainer actually do?
It tokenizes your pattern into literals, character classes, quantifiers, groups, anchors and assertions, then renders a plain-English description for each token in order — effectively annotating the pattern line by line.
Which flags can I toggle?
The three most common flags: g (global — find all matches), i (case-insensitive) and m (multiline — ^ and $ match at line breaks). The tool shows which flags are active in the live match engine.
Can I see capture groups?
Yes. Every match is listed with its index, matched text, and all numbered capture groups, so you can verify that parentheses extract exactly the substrings you need.
Why is my pattern marked as invalid?
The tester reports syntax errors such as unbalanced parentheses, invalid quantifiers or bad escape sequences with a description, so you can fix the pattern instead of getting a silent "no matches" result.