You export a CSV from a UK system and double-click it in US Excel — 28/05/2026 suddenly looks like May 28, or something even stranger. The file isn't corrupt. Excel is guessing your date format based on your computer's locale.
This short guide covers why that happens, how to import CSV correctly, and how to batch-fix dates that are already wrong. For the full walkthrough with examples, see the official guide: How to Fix Excel CSV Date Import Problems.
Why Excel breaks CSV dates
A CSV is plain text. It does not store whether a value is a date or a string. When you double-click to open, Excel parses using your regional settings:
- US Excel: MM/DD/YYYY
- UK / Europe: DD/MM/YYYY
Dates like 03/04/2025 are the most dangerous — both parts are ≤ 12. US Excel may read April 3; UK Excel reads March 4. Excel won't warn you.
Other common traps:
- Dates exported as serial numbers (e.g.
44927) - Two-digit years triggering century guesses
- Re-saving as CSV destroys formats a second time
The right way: don't double-click the CSV
-
Open Excel first — don't double-click the
.csvfile - Data → Get Data from Text/CSV (older Excel: Data → From Text)
- Set date columns to Text if you need to preserve the original string
- Confirm the source region (US / UK), then convert to a single format
For team data exchange, agree on ISO 8601: YYYY-MM-DD in your schema — unambiguous, sorts correctly as text, and works in JSON APIs and databases.
| Ambiguous value | US reads as | UK reads as | Safe format (ISO) |
|---|---|---|---|
| 03/04/2025 | 2025-04-03 | 2025-03-04 | Confirm source region |
| 28/05/2026 | — | 2026-05-28 | 2026-05-28 |
| 05/28/2026 | 2026-05-28 | — | 2026-05-28 |
Already broken? Fix dates in the browser (no server upload)
I built a free tool cluster on FormatList — everything runs locally in your browser:
1. Date Format Fixer — bulk repair
- Paste a date column or upload
.csv/.txt - Ambiguous rows highlighted; optional US / UK preference
- Export ISO / US / UK or download a fixed CSV
Best for: normalizing a whole column to ISO before a database or API import.
2. Ambiguous Date Checker — check before you commit
Enter a single date like 03/04/2025 and see US vs UK interpretations side by side — no guessing.
Best for: visa forms, contracts, anything where the exact day matters.
3. UK Date to US Date — DD/MM → MM/DD
Lock DD/MM input → MM/DD output. Batch-convert UK invoices or CRM exports for US systems.
4. Fixed dates before JSON?
Normalize dates to ISO first, then use CSV to JSON. Order matters — wrong dates baked into JSON propagate through your entire pipeline.
Quick FAQ
Q: Why did my dates turn into numbers like 44927?
A: Excel stores dates as serial numbers internally. Date Format Fixer converts them back to readable dates.
Q: Fix dates first, or convert to JSON first?
A: Fix dates first. Bad dates in JSON pollute validation and reporting downstream.
Summary
| Scenario | What to do |
|---|---|
| Not imported yet | Excel "import from text"; set date column to Text or ISO |
| Team data exchange | Agree on YYYY-MM-DD
|
| Already wrong | Date Format Fixer + manual review of ambiguous rows |
| Single date unclear | Ambiguous Date Checker |
If you also work with ChatGPT output, JSON, or CSV pipelines, FormatList has JSON Repair, CSV converters, and more at formatlist.com.
Free tools, 100% browser-local. Feedback welcome on About.
Top comments (0)