Delete columns
Part of the Cleaning Recipes Guide · Last updated: 2026-03-31
Remove unused or sensitive columns from the final exported CSV.
Useful for stripping internal notes, helper fields, or legacy IDs before sharing a file.
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.
Drops columns that should not leave the working file.
First-time walkthrough for beginners
If this is your first time using Delete columns, 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.
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 Internal Notes, Legacy ID. 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.
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.
Configure delete columns in the editor
Deleting columns is powerful because it removes data from the working table before export. A beginner should always verify that the removed fields are truly optional before saving the recipe for recurring use.
- Choose only the columns you are certain should not appear in the exported CSV.
- Compare the selected columns against the destination import requirements before applying.
- If the file is important, keep an untouched copy or duplicate export until you trust the recipe.
Apply the recipe and confirm the result before export
Apply the action, then compare the changed table against the expected result Columns removed. 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 Columns removed.
- 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
- Add Delete columns and select the columns to remove by name.
- Double-check that none of those columns are required by the next import target.
- Apply the recipe and confirm the summary shows the expected number of removed columns.
Example
This action is good for publishing a clean customer-facing export without internal-only fields.
Before you run this recipe
- Identify the exact columns or rows that delete columns should change before you open the recipe form.
- Keep one visible example in mind, such as Internal Notes, Legacy ID, 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 Columns removed.
- 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
- Removing a field that looks optional but is still required by the next import target.
- Applying the recipe to a file variant that contains a similarly named but still useful column.
When this recipe is the right choice
Use Delete columns when you want a repeatable cleanup rule instead of manual editing across many rows. The strongest clue is the use case itself: Useful for stripping internal notes, helper fields, or legacy IDs before sharing a file.
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.