Two regex chores in one place. Escape any text — a price, a file path, a URL — so it matches literally inside a regular expression, ready to copy or wrap in new RegExp(). Then extract data: give a pattern with capture groups and some text, and every match lands in a table with one column per group — named groups become the column headers — to copy into a spreadsheet or download as CSV. It's free and runs entirely in your browser.
| Character | Escaped |
|---|---|
| . | \. |
| * + ? | \* \+ \? |
| ( ) [ ] { } | \( \) \[ \] \{ \} |
| ^ $ | | \^ \$ \| |
| \ | \\ |
| / (optional) | \/ |
. * + ? ^ $ { } ( ) | [ ] and \. Escape / too if the pattern goes in a /…/ literal.
Not outside a character class. With the u or v flag, \- is actually a syntax error.
Write (?<name>…) in the pattern; that group's text appears under a column called name.
Yes — copy as tab-separated text and paste, or download the CSV.
No. Matching happens in your browser.
Escaping turns text into a pattern that matches it literally by putting a backslash before each regex syntax character — . * + ? ^ $ { } ( ) | [ ] and backslash itself. Only those characters are escaped: escaping a hyphen, a common habit, is a syntax error once the u or v flag is on, and the tests check that escaped text matches itself under no flag, u and v. The forward slash can be escaped too for use inside /…/ literals. Extraction runs the pattern globally over the text using the same matching engine as the site's Regex Tester, with a time budget and match cap so a catastrophic pattern can't freeze the page, and turns every match into a row: the whole match, then each capture group. When the pattern uses named groups such as (?<user>…), those names become the column headers. The table can be copied as tab-separated text, which pastes straight into a spreadsheet, or downloaded as CSV with proper quoting.