Recipe 7

Find and replace

Built-in action

Part of the Cleaning Recipes Guide · Last updated: 2026-03-31

Bulk-replace text inside selected columns with a controlled search rule.

Great for standardizing statuses, correcting recurring typos, or updating old product labels.

This page is intentionally detailed so you can understand not only which recipe to choose, but also how to prepare your CSV, what to expect during the apply flow, and what to verify after the change runs. That makes it easier to use saved recipes confidently on recurring imports instead of cleaning values by hand.

If you are comparing similar actions, start with the recipe preview below, then work through the screenshots and verification checklists further down the page. Those sections are designed to mirror the real UI you will see in Online CSV Editor.

Recipe preview
Saved recipe
Status normalization
Find and replace in Status

Standardizes repeated values with one safe action.

Example row
Changed values are reported in the apply summary
Find
pending
Replace
ready
1. Pick the action
Configure the recipe in the modal before running it on the table.
2. Review the preview
Confirm the recipe details and apply only when the rule looks correct.
3. Export clean data
Use the apply summary to verify the result before exporting the CSV.

First-time walkthrough for beginners

If this is your first time using Find and replace, follow these steps in order. The screenshots below come from the real product flow so you can compare your screen with the guide as you go.

Step 1

Open a file and find one example you want to fix

Start by loading your CSV or a sample file into the editor. Before opening the recipe tools, look for one real example that should change, such as pending. That gives you something concrete to compare after the recipe runs.

  • Check whether the issue appears in one column or across several columns.
  • If the file is large, note a few rows you can revisit after applying the recipe.
Online CSV Editor with a sample file loaded and the Recipes button visible in the toolbar.
The editor toolbar is where most guide workflows begin: load a CSV sample, open Recipes, then apply or save a cleaning flow before exporting.
Step 2

Open Recipes and start a new recipe draft

Click the Recipes button in the toolbar. Beginners can choose New recipe or Start from example, then save a reusable recipe after they confirm the action works the way they expect.

  • Use Start from example if you want to learn the recipe editor with a safe starter action already loaded.
  • Saved recipes stay browser-local unless you deliberately share the definition.
The Cleaning Recipes modal open inside Online CSV Editor, showing saved recipes and actions.
The Cleaning Recipes modal lets you create, review, save, duplicate, share, and apply repeatable recipe actions without sending CSV data to a server.
Step 3

Configure find and replace in the editor

This action is best when the same typo or old label repeats many times. A beginner should keep the replacement narrow by targeting specific columns and checking whether the match should be case-sensitive.

  • Choose the columns where the repeated text actually needs to change.
  • Enter the find text and replacement text exactly as you want them written.
  • Decide whether matching should be case-sensitive before applying the change broadly.
The recipe editor open inside Online CSV Editor with a starter recipe and action settings visible.
The recipe editor is where beginners name the recipe, choose the action, adjust settings such as columns or rule mode, and save the workflow for reuse.
Step 4

Apply the recipe and confirm the result before export

Apply the action, then compare the changed table against the expected result ready. Use the apply summary together with the example panel below to confirm the recipe did what you intended before exporting the CSV.

  • Make sure the output now matches the intended result, such as ready.
  • Read the apply summary and confirm that the changed row or cell count matches your expectation.
  • Export the CSV only after scanning a few rows near the top, middle, and bottom of the file to catch edge cases.

Quick version

  1. Add Find and replace, then choose the columns where the replacement should happen.
  2. Enter the find text, replacement text, and whether the match should be case-sensitive.
  3. Apply the recipe and inspect the changed cell count in the apply summary.

Example

Before
pending
After
ready

Use targeted columns instead of all columns when the same word might be valid elsewhere in the file.

Before you run this recipe

  • Identify the exact columns or rows that find and replace should change before you open the recipe form.
  • Keep one visible example in mind, such as pending, so you can compare the result after the recipe runs.
  • If you expect to repeat this cleanup on future imports, save the recipe with a descriptive name instead of applying it only once.

What to verify after applying

  • Make sure the output now matches the intended result, such as ready.
  • Read the apply summary and confirm that the changed row or cell count matches your expectation.
  • Export the CSV only after scanning a few rows near the top, middle, and bottom of the file to catch edge cases.

Common mistakes beginners should avoid

  • Replacing text in every column when the same word is valid somewhere else in the file.
  • Forgetting about case sensitivity and changing more rows than intended.

When this recipe is the right choice

Use Find and replace when you want a repeatable cleanup rule instead of manual editing across many rows. The strongest clue is the use case itself: Great for standardizing statuses, correcting recurring typos, or updating old product labels.

In practice, this recipe is most valuable when the same cleanup problem appears in recurring exports from CRMs, spreadsheets, analytics tools, or ecommerce platforms. Saving the recipe means you can apply the same standard every time a similar CSV arrives, which is exactly what makes the guide useful for long-term workflows rather than one-off fixes.

Use this recipe in context

Open the editor, import your file, click Recipes in the toolbar, and apply this action on its own or combine it with other saved actions. If you want the recipe to run immediately when a file opens, use the Apply recipe on import dropdown in the importer first.

For the best results, treat this page as a reusable operating note: review the example, compare it to your live CSV, run the saved action, and then return to the guide whenever you need to train a teammate or document a repeatable cleanup process.