Regex Match Lines
Run a regular expression on each line of text and see matches, non-matches, and capture groups in a table.
Filter and audit log lines with a regular expression
Log files, CSV exports, and command output are easiest to scan one line at a time. This matcher runs your pattern against every line, marks hits and misses, and lists capture groups when the pattern defines them. It is useful for triaging errors in CI logs or checking which rows match a prefix rule before bulk editing.
Flags and behavior
Enable Ignore case for case-insensitive matching. Enable Multiline anchors
when ^ and $ should apply per line instead of to the whole paste.
Each line is tested independently; global iteration across the full blob is not used.
For interactive pattern debugging, use the Regex Tester. To escape literals before you build a pattern, use Regex Escape Unescape.
Frequently Asked Questions
Why does my pattern match only the first line?
By design each line is evaluated separately. Remove the global flag mindset and anchor with ^ when you only want lines that start with a token.
Where do capture groups appear?
When your pattern uses parentheses, the Groups column lists numbered captures ($1, $2, and so on) for matching lines.
Does this use the same engine as JavaScript?
Yes. Patterns are compiled with the browser RegExp implementation, so results match Node and modern browsers for equivalent flags.