Find & Replace
Search and replace with regex, case, and whole-word options
When to use find & replace vs an editor?
Most editors have find & replace, but using one in the browser is faster when you're working with text that's currently in a form, an email draft, or a paste buffer — no need to open VS Code, paste, replace, copy back. The tool also gives you regex without learning your editor's flavour: it uses the browser's standard JavaScript regex (PCRE-like).
The match count updates as you type the search pattern, so you know how many replacements you'll trigger before clicking. The result panel shows the modified text, leaving the input untouched in case you want to iterate.
Use cases
- Bulk rename — swap a class or variable across a multi-file paste in one operation.
- Rewrite URLs — convert all `localhost:3000` references to a staging hostname before a screenshot.
- Fix line breaks — replace `\r\n` with `\n` when porting Windows-edited text into a Unix project.
- Update versions — swap `1.2.3` for `1.3.0` across a release-note draft without missing a spot.
Examples
Search: \b(\w+)@example\.com\b
Replace: [email protected]
In: [email protected], [email protected]Frequently asked questions
Does it support regex capture groups?
Yes — use `$1`, `$2`, etc. in the replacement field to reference capture groups, just like in JavaScript's `String.replace`.
What regex flavour is supported?
JavaScript regex (ECMAScript). Lookbehind is supported in modern browsers. Backreferences in patterns (e.g. `\1`) work; named groups (`(?<name>...)`) work.
Is search case-sensitive by default?
No — search is case-insensitive by default (the regex `i` flag). Enable the 'Case sensitive' option for exact-case matching.
Will an invalid regex break the tool?
No — invalid patterns show a clear error message under the search field and the replacement is skipped.
Is my text uploaded?
No. All matching and replacement happens in your browser; nothing is sent to a server.