hello@example.com- Group 1
- hello
- Group 2
- example.com
Test a JavaScript regular expression against sample text. Inspect matches, indexes, capture groups, flags, and syntax errors before using the pattern in code.
JavaScript regex workspace
Matches, indexes, and capture groups are calculated in this browser. This version does not emulate Python or PCRE.
2 matches · gi
hello@example.comteam@example.orgPaste a JavaScript pattern and the text you want to inspect, or load a safe example.
Toggle supported JavaScript flags such as global, case-insensitive, multiline, dotAll, and Unicode behavior.
Check match text, indexes, groups, counts, and parser errors before copying the pattern into code.
The first version uses the browser's JavaScript RegExp engine. Python, PCRE, PHP, and other flavors can differ, so a pattern that works in one engine may not work here.
g searches for multiple matches, i ignores letter case, and m changes how line anchors work. The tester only exposes flags supported by the JavaScript engine used in the page.
Yes. When a pattern contains capturing parentheses, the result lists the full match and the captured values for each match.
The JavaScript parser rejects invalid syntax such as an unclosed character class, missing parenthesis, or unsupported flag. The error message appears beside the input.
The tester evaluates the pattern and test string in this browser and does not require an account. Verify network behavior independently when working with sensitive text.
Not as a separate engine in this first version. Use JavaScript-compatible syntax or test the pattern in the target language's own tool before shipping it.
A focused workspace for checking whether a pattern matches the text you expect before you reuse it in code.
The pattern and sample text remain separate so you can change either side without losing the other value.
Toggle the JavaScript flags supported by the workspace and rerun the same test to compare behavior.
Inspect full matches, indexes, and captured groups instead of relying only on a pass/fail label.
A useful tester distinguishes a valid pattern with no matches from a pattern that the JavaScript parser cannot read.
No match means the pattern parsed successfully but found nothing. An invalid-pattern message means the JavaScript RegExp constructor rejected the syntax.
Regex engines differ in flags, escapes, lookbehind, named groups, and replacement syntax. Test in the engine that will run your code.
Large text and pathological patterns can consume browser time. Keep examples practical and stop processing if the page becomes unresponsive.
Use small examples to validate the workflow, then adapt the pattern to your own data and test cases.
Examples are useful starting points, not complete validation guarantees for every email address or URL standard.
Use parentheses when you need a specific part of a match, then confirm the group values in the result table.
Copy the pattern or test text only after checking flags and the target language's regex flavor.
Continue with another browser-based tool.
Paste JSON or open a file to format, validate, beautify, or minify it. Choose indentation, review parser errors, and copy or download the result in your browser with no login.
Open toolCompare two text versions with word- or line-level additions and removals. Import local files, review the changes, and copy or download a TXT report without signing in.
Open toolEncode or decode URL components, full URLs, and query parameters with UTF-8 percent encoding. Copy the result online without registration or login.
Open toolConvert text to uppercase, lowercase, Title Case, sentence case, camelCase, snake_case, and more. Paste text, choose a format, then copy or download the result with no login.
Open tool