Question 1

What is the difference between named capture groups and numbered capture groups?

Accepted Answer

Numbered capture groups use parentheses (...) and are accessed by their 1-based numerical index ($1, $2). Named capture groups use (?<name>...) syntax and assign a human-readable identifier to the match. Named groups make complex regex patterns significantly more readable, maintainable, and self-documenting.

Question 2

How do lookahead and lookbehind assertions work in regular expressions?

Accepted Answer

Lookaround assertions match characters without consuming them (zero-width assertions). Positive lookahead (?=abc) asserts that characters ahead match 'abc'. Negative lookahead (?!abc) asserts that characters ahead do not match 'abc'. Positive lookbehind (?<=abc) and negative lookbehind (?<!abc) perform the same checks behind the current position.

Question 3

What causes catastrophic backtracking and how do I avoid it?

Accepted Answer

Catastrophic backtracking occurs when nested, ambiguous quantifiers (such as (a+)+) fail to match, causing an exponential combination of backtracking paths that freezes the browser engine. Avoid nesting unanchored greedy quantifiers and use atomic grouping or specific character classes instead of dot-all wildcards.

Question 4

What do regular expression flags (g, i, m, s, u) do?

Accepted Answer

Flags modify search behavior: 'g' (global) finds all occurrences rather than stopping at the first; 'i' (ignore case) performs case-insensitive matching; 'm' (multiline) makes ^ and $ match line boundaries; 's' (dotAll) allows . to match newline characters; and 'u' (unicode) enables full UTF-16 code point processing.

Question 5

How do non-capturing groups (?:...) improve regex performance?

Accepted Answer

Non-capturing groups group tokens for quantifiers (e.g., (?:abc)+) without storing the matched substring in memory or incrementing capture group indices. This reduces execution overhead and prevents cluttering replacement backreferences ($1, $2).

Question 6

Are regex patterns evaluated securely in this workbench?

Accepted Answer

Yes. The workbench compiles and tests regular expressions directly within the client browser's JavaScript V8/JavaScriptCore engine. An execution safeguard caps match counts at 1,000 to prevent runaway memory usage, and zero data leaves your local session.

Test and explain regular expressions

Local developer utility

Frequently asked

Feedback, bugs & custom requests

Related tools