Overview
Regular expressions are the power tools of text: one compact pattern can find every email address in a document, validate a form field, or reformat a thousand lines at once. They are also famously unreadable, which is why testing them live — seeing exactly what matches, as you type — turns a cryptic art into something you can learn by doing.
This tester runs real JavaScript regular expressions against your own text. Matches light up in place, the match count updates instantly, capture groups are broken out for the first match, and an invalid pattern gets a plain error message instead of silent failure.
What is a regular expression?
A regular expression (regex) is a pattern written in a tiny language for describing sets of strings. \d means “a digit”, + means “one or more”, so \d+ matches any run of digits. Brackets define choices ([A-Z] is any capital letter), parentheses capture groups, and anchors like ^ and $ pin the pattern to the start or end of the text.
They shine at validation and extraction: is this a plausible email? pull all the dates out of this log. They are poor at nested structures like HTML — a classic trap — and a pattern that is too clever becomes unmaintainable. The tester helps you keep patterns as simple as the job allows, because you can watch complexity pay off (or not) in real time.
Features
- Live highlighting of every match, directly in your test text.
- Capture-group breakdown showing what each (parenthesised) group grabbed.
- Flags g, i, m, s as toggles: global, case-insensitive, multiline, dot-all.
- Plain error messages when the pattern is invalid, pointing at the problem.
- Zero-length match guard so patterns like x* cannot hang the highlighter.
- Private: patterns and test text never leave your browser.
Benefits
- Learn by seeing. Watching matches light up beats reading a tutorial.
- Debug faster. The group breakdown shows what the engine actually captured.
- No setup. Faster than opening a console or installing a tool.
- Safe to experiment. Try the scary pattern — worst case is an error message.
Who can use it
Developers validating inputs and parsing logs, data analysts cleaning spreadsheets, QA engineers writing test assertions, students learning regex for the first time, and anyone who has ever needed to find “all the X in this file”. Technical writers checking patterns before publishing them will appreciate the instant feedback.
How to use
- Type your pattern in the expression box (the default finds email addresses).
- Toggle flags: g for all matches, i to ignore case, m for multiline, s for dot-all.
- Paste or type your test text below.
- Watch matches highlight live; read the count and the capture-group breakdown.
- If the pattern is invalid, read the error, fix it, and watch the highlights return.
Frequently asked questions
Which regex flavour is this?
JavaScript's, since the tester runs in your browser. Most everyday patterns transfer directly to Python, Java and other languages, but exotic features (lookbehind limits, named groups, recursion) differ between flavours — always re-test in the language you will actually use.
Why did my pattern match nothing?
The usual suspects: a missing flag (case sensitivity bites often — try i), anchors (^ or $) that pin the pattern where the text is not, or escaping (to match a literal dot you need \., because . alone means “any character”). Toggle flags and simplify the pattern until something lights up, then build back up.
What are capture groups for?
Parentheses do two jobs: they group (so a quantifier applies to several tokens) and they capture (the matched text is saved as $1, $2, …). The breakdown panel shows exactly what each group captured in the first match, which is how you verify a pattern extracts the right pieces.
My page froze on a pattern — what happened?
Probably catastrophic backtracking: nested quantifiers like (a+)+ on a long non-matching string can take effectively forever. The highlighter caps work at 1000 matches, but a single pathological match can still stall. Simplify nested quantifiers — it is the classic regex performance trap.
Is my test data uploaded anywhere?
No. The pattern compiles and the matching runs entirely in this tab. Test data with real emails or logs stays on your machine.
Conclusion
Regex rewards the tester, not the memoriser. Write a little, watch it light up, fix what does not — and keep patterns as boring as the job allows. The clever ones are for showing off; the simple ones are for shipping.