Why Excel flips the day and month in a CSV
A CSV is plain text with no date type, so Excel reads every date using your computer’s regional (locale) settings. A machine set to US English takes the first number of 04/11/2023 as the month and gets 11 April; a UK machine reads the same characters as 4 November. Open a file from the other side of the Atlantic, hit Save, and Excel writes its reading back into the CSV — and because only the days 12 and under can flip, the file looks mostly fine while a third of its dates now mean something else. The full story, including the tell-tale half-dates-half-text column, is in the companion guide: Excel changed my CSV date format. This exact mismatch is what makes QuickBooks reject a bank CSV outright — see our QuickBooks CSV import errors guide.
Why this tool never guesses — and what it does instead
Here is the honest core of it: 04/11/2023 is a valid date under both readings, so the source order is unknowable from the value alone. Any tool that claims to auto-detect it is guessing with your data. This one refuses to:
- You state the source order. The Convert button stays disabled until you say whether the file was written day-first, month-first or year-first.
- The analyzer only pre-selects an order the data proves. A day of 13 or more can never be a month, so a value like
27/03/2023is proof of day-first. When every proof in a column points the same way, that order is pre-filled for you — and when the evidence is ambiguous or contradictory, the tool says so in words and waits for your decision. - Anything that does not parse is copied through untouched, byte for byte, and counted in the summary. Pick the wrong order and you see a big “untouched” count — not a silently mangled file.
- Values carrying a time land in the untouched count deliberately. Converting
04/11/2023 09:30would mean dropping the time, and silent data loss is the thing this site exists to undo.
How to use it
- Drop the file or paste the rows, then click Find the date columns. Every date-like column is listed with its evidence: how many values prove which order, how many are ambiguous, and how many carry a risky two-digit year.
- Confirm the source order. If the data proved it, it is already selected; if not, choose the order the file was written in — you know where the export came from, the file does not say.
- Pick the output format. ISO
YYYY-MM-DDis the safe default: the year leads, every part is fixed-width, and no locale on Earth misreads it. - Click Convert & Download. The summary reports exactly how many values were converted, already correct, or left untouched — and the preview shows the result before you trust it.
The output formats
| Format | Example | Use it when |
|---|---|---|
YYYY-MM-DD | 2023-11-04 | Always, if you can — ISO 8601 is unambiguous in every locale and sorts correctly as text. |
DD/MM/YYYY | 04/11/2023 | A system that insists on UK/EU order. |
MM/DD/YYYY | 11/04/2023 | A system that insists on US order (QuickBooks US, for example). |
DD-MMM-YYYY | 04-Nov-2023 | Human readers — the spelled month cannot be misread in either direction. |
Tick Excel-safe export and each converted date is written as ="2023-11-04", which Excel treats as text even on a double-click — so the next person to open the file cannot re-flip your work.
Two-digit years: the century is Excel’s rule, not ours
A year written with two digits, like 1/2/03, does not say which century it belongs to. Excel resolves it with a fixed rule — 00 to 29 becomes 2000 to 2029, and 30 to 99 becomes 1930 to 1999 — and this tool applies the same rule so the result matches what you already see on screen in Excel. The summary counts every value pivoted this way, because a date-of-birth or archive column from before 1930 will land in the wrong century. If the warning fires on data that old, fix the years at the source before converting.
What this tool can and cannot recover
If the file was only viewed in Excel, nothing is lost — the original characters are still on disk, and converting them to ISO here makes them permanently safe. If the file was misread and re-saved, only the days of 13 and above are provably intact; a half-flipped column shows up in the analysis as contradictory evidence, and for the ambiguous rows the honest answer is to re-export from the source. A different trap wearing the same costume: if Excel turned codes like MAR1 into 1-Mar, that damage cannot be reliably reversed by any tool — this page converts real dates between formats, it does not resurrect destroyed codes. And the way to stop all of it recurring is the safe import routine in how to open a CSV in Excel without breaking it.
Scroll back up, drop the file, state the order it was written in, and download the converted CSV in seconds — nothing leaves your machine.
Fix my dates now Read why Excel flips the day and monthFrequently asked questions
Why doesn't the tool detect the date order automatically?
Because 04/11/2023 is a valid date under both readings — 4 November and 11 April — the source order is unknowable from the value alone, so the tool never guesses. You state the order the file was written in. The analyzer only pre-selects an order the data proves, which takes a day of 13 or more: a value like 27/03/2023 can only be day-first, so it settles the whole column.
What happens to values that don't parse under the order I chose?
They are copied through untouched, byte for byte, and counted in the summary. A wrong choice therefore shows up as a large untouched count instead of silently mangling the file. Values that carry a time, like 04/11/2023 09:30, land in that count deliberately — converting them would mean dropping the time, and silent data loss is the thing this site exists to undo.
Can this tool un-flip a file Excel already re-saved?
Only partly, and we would rather say so than pretend. In a re-saved file, dates with a day of 13 or more were never touched by Excel, and a half-flipped column shows up here as contradictory evidence — some values proving day-first and some month-first — so the analyzer suggests nothing and tells you why. For the ambiguous rows there is no way to tell from the file which were flipped; the dependable fix is to re-export from the source system, ideally as ISO YYYY-MM-DD.
What does the two-digit year warning mean?
A year written with two digits, like 1/2/03, does not say which century it belongs to. Excel resolves it with a fixed rule — 00 to 29 becomes 2000 to 2029, and 30 to 99 becomes 1930 to 1999 — and this tool applies the same rule so the result matches what you already see on screen in Excel. The summary counts every value pivoted this way, because a date-of-birth or archive column from before 1930 will land in the wrong century.