Convert date to ISO
Part of the Cleaning Recipes Guide · Last updated: 2026-03-31
Normalize dates into an import-friendly ISO format such as 2026-03-31.
Useful when source files mix formats like 03/31/2026, 31/03/2026, or spreadsheet-style date text.
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.
Normalizes one date column before re-import.
First-time walkthrough for beginners
If this is your first time using Convert date to ISO, 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 03/31/2026. 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 convert date to iso in the editor
Date cleanup is safest when you identify one reliable source format before you save the recipe. ISO output is useful because it is stable for imports and easier to sort later.
- Pick the source date column first so the recipe only touches real dates.
- Set the known input format when possible instead of relying on auto-detect for mixed files.
- Choose date-only or date-time output based on whether the receiving system expects hours and minutes too.
Apply the recipe and confirm the result before export
Apply the action, then compare the changed table against the expected result 2026-03-31. 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 2026-03-31.
- 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 the Convert date to ISO action and select the source date column.
- Choose the known source format or leave it on auto-detect if the file is consistent.
- Pick date-only or date-time output, apply the recipe, and inspect any warnings for invalid dates.
Example
If some rows are invalid, keep the warning mode on so you can fix those rows without losing the rest.
Before you run this recipe
- Identify the exact columns or rows that convert date to iso should change before you open the recipe form.
- Keep one visible example in mind, such as 03/31/2026, 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 2026-03-31.
- 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
- Assuming a mixed date column can be normalized correctly without checking a few rows first.
- Overwriting a timestamp column with date-only output when the destination system still needs time information.
When this recipe is the right choice
Use Convert date to ISO when you want a repeatable cleanup rule instead of manual editing across many rows. The strongest clue is the use case itself: Useful when source files mix formats like 03/31/2026, 31/03/2026, or spreadsheet-style date text.
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.