Skip to content
Docs navigationBrowse tools →

Tool docs

RegExp Tester

Test JavaScript regular expressions against sample text locally in the browser. This guide covers the tool's fast feedback loop, the flags and matching behavior that matter most, and the common traps behind broken patterns.

Tool

Overview

01

RegExp Tester

Use the RegExp Tester when you need to validate a pattern, inspect matches and capture groups, or compare how flags change the result. It mirrors the browser's RegExp engine, which makes it a practical check for frontend and Node-adjacent regex debugging.

Guide

Common usage patterns

01

Pattern testing and match inspection

  • Start with a raw pattern or one of the built-in templates.
  • Toggle flags like g, i, m, s, u, or y to see how they change the result set.
  • Paste representative sample text instead of a tiny synthetic string so you catch real failures.
  • Read the match list and capture groups together; they often explain why a 'working' pattern is still wrong.

Guide

Edge cases & common pitfalls

01

Greediness, escaping, and multiline behavior

  • Greedy and lazy quantifiers can turn the same pattern into very different matches.
  • Escaping rules differ between a regex literal, a JavaScript string, and pasted text samples.
  • Newlines, dotAll, and multiline flags are a common source of false assumptions.
  • An invalid pattern should be treated as a syntax problem first, not as a matching problem.

Internals

How it works internally

01

Browser RegExp engine with local match reporting

Birdor compiles the pattern with the browser's native RegExp engine, runs it against the current sample text, and reports matches and groups locally. That makes the feedback immediate and close to the runtime many developers actually ship.