How is this different from a normal find and replace?

A normal editor replaces one term at a time. This tool stacks many rules and runs them in sequence on one click, so you can clean up a whole document — rename a product, normalise whitespace, strip boilerplate — in a single pass. Each rule keeps its own mode and flags, and the live match counts tell you exactly what each rule did.

Does the order of the rules matter?

Yes. Rules apply top to bottom, and each one operates on the output of the rule before it. That means an early rule can create or remove text that a later rule then matches. If a replacement is not landing as expected, reorder the rules with the arrows so the more specific rule runs before the broader one.

What is the difference between literal and regex mode?

Literal mode treats your find text as plain characters, so dots, brackets and slashes match themselves with no escaping needed. Regex mode interprets the find field as a JavaScript regular expression, unlocking character classes, quantifiers, anchors and capture groups. In regex mode you can reference captured groups in the replacement with $1, $2 and so on.

How do the case, whole-word and multiline flags work?

Case insensitive ignores upper and lower case when matching. Whole word wraps your pattern in word boundaries so cat does not match category. Multiline makes the ^ and $ anchors match at every line break instead of only the start and end of the text, and dotall lets the dot match newline characters too. The multiline and dotall flags only appear in regex mode.

Is my text uploaded anywhere?

No. Every replacement is computed locally in your browser using the built-in regular-expression engine. Your text, your rules and your files never touch a server, which makes the tool safe for confidential drafts, source code, logs and customer data.

Can I save and reuse a set of rules?

Yes. Your rules and the current text are auto-saved in this browser, so they are still there when you come back. You can also export the full rule set to a JSON file and import it later or on another machine, which is handy for a cleanup recipe you run often.

What happens if my regex has a syntax error?

The rule that fails is flagged with a red border and the exact engine error message, and that single rule is skipped so the rest of your rules still run. Fix the pattern and the result updates instantly — nothing is destroyed and the input text is never altered.

Bulk Find and Replace

Bulk find and replace lets you stack many find/replace rules and apply them to a block of text in a single pass. Instead of opening your editor’s replace box over and over, you build a list of rules — each one either literal text or a regular expression — and the tool runs them top to bottom, showing a live preview and a match count for every rule. It is built for the moments when one search-and-replace is not enough: renaming a product across a document, cleaning messy exported data, normalising whitespace and quotes, stripping tracking parameters from a list of URLs, or reshaping log lines before you paste them somewhere else.

How it works

You paste text into the input box (or load a .txt, .md, .csv or .log file), then add rules. For each rule you type what to find and what to replace it with, pick literal or regex mode, and toggle the flags you need: case-insensitive, whole-word, multiline and dotall. Literal mode escapes your search text for you, so punctuation matches itself with no fiddling. Regex mode hands the pattern straight to the browser’s regular-expression engine, so capture groups, character classes and anchors all work — and you can reference groups in the replacement with $1, $2 and friends.

The rules apply in order, each one operating on the result of the previous rule, so you can do multi-stage clean-ups: collapse whitespace first, then fix capitalisation, then swap terms. Every rule reports how many times it matched the running text, which makes it obvious when a rule is doing nothing or matching far more than you intended. A rule with a broken regex is flagged in red with the engine’s error message and quietly skipped, so one mistake never blocks the rest. When the result looks right, copy it, download it as a text file, or hit Apply to feed it back into the input for another round. Rules and text auto-save in your browser, and you can export the whole rule set to JSON to reuse later.

Example

Say you paste a support template that still says ACME Corp and has doubled spaces from a bad export. Add three rules: replace ACME Corp with Gera Systems (literal), replace ACME with Gera (literal), then a regex rule \s{2,} → a single space to crush the runs of whitespace. Run them and the document is renamed and tidied in one click. The whitespace rule reports something like 4 matches, confirming it actually fired. Need to also strip a tracking suffix from every URL? Add a regex rule \?utm_[^\s]+ replacing with an empty string, and it joins the chain — no extra passes, no manual editing.

Everything happens locally in your browser. No text, files or rules are ever uploaded, so the tool is safe to use on confidential drafts, customer exports and source code.