Regex Tester Guide: Test Patterns Locally

Why test regex in the browser

Regexes appear in input validation, log parsing, and CI pipelines. When one misbehaves, the fastest way to understand it is to see the matches against real input.

Online regex tools send your pattern and test text to their servers. For logs, configs, or test fixtures containing sensitive values, that is a leak you do not need. A client-side tester runs the same JavaScript RegExp engine locally.

This page's tester uses the native RegExp engine, so what you see is what Node.js and the browser will do.

The flags that change everything

Flags alter matching semantics in ways that are easy to overlook:

g returns all matches instead of the first one. i ignores case. m makes ^ and $ match at line boundaries. s lets . match newlines. u enables Unicode-aware matching, so \p{L} and astral characters behave correctly.

• g: find every match, not just the first
• i: case-insensitive matching
• m: ^ and $ match at the start and end of each line
• s: dot matches newline characters
• u: Unicode mode for \p{...} properties and astral code points

Groups: capture what you actually need

Parentheses capture groups for later use. Numbered groups are assigned in order; named groups like (?<year>\d{4}) make the extraction readable.

Non-capturing groups (?:...) group without capturing. Use them when you only need alternation or quantifiers applied to a block, to avoid shifting group numbers.

The tester shows every group per match, named or numbered, so you can verify extraction before writing it into code.

Lookarounds and anchors

Lookahead (?=...) asserts what follows without consuming it; negative lookahead (?!...) asserts what does not follow. Lookbehind (?<=...) and negative lookbehind (?<!...) do the same for what precedes the match.

Anchors ^ and $ pin the match to the string (or line, with m). Word boundary \b matches between a word character and a non-word character.

Keep lookarounds simple. Nested lookarounds and heavy alternation inside them are where patterns become unreadable and slow.

A safe regex workflow

1. Open the Regex Tester in your browser.
2. Paste the pattern and select the flags your runtime uses.
3. Add a small sample that represents the real input, including edge cases.
4. Read the matches and groups; if the extraction is wrong, fix the pattern before touching code.
5. Copy the verified pattern into your code, and keep the same flags.

FAQ

References

This guide is based on the JavaScript language specification and common regex practice:

• MDN – Regular expressions: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_expressions
• ECMAScript Language Specification – RegExp: https://tc39.es/ecma262/#sec-regexp-regular-expression-objects
• OWASP – ReDoS (Regular Expression Denial of Service): https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS