The CSV file the tool creates is correct, but Excel guesses how to read a CSV that you open by double-clicking, and its guesses can scramble accents, strip leading zeros and swap dates. The fix is to import the file instead of opening it.
Below are the three common symptoms and what to do.
On this page
Key takeaways
- The tool writes UTF-8 with commas. Excel does not always assume UTF-8 on double-click.
- Use Data, From Text/CSV and choose UTF-8 to see accents correctly.
- Set identifier columns, such as postcodes and product codes, to Text during import to keep leading zeros.
- Dates can be read in the wrong order. Choose the date format in the import dialog.
Symptoms at a glance
| What you see | Cause | Fix |
|---|---|---|
| é shows as é | File read in the wrong encoding | Import with UTF-8 |
| 007 becomes 7 | Excel converts to a number | Import the column as Text |
| Dates swap day and month | Regional guess | Import the column as a date with the right order |
| Everything in one column | Wrong separator for your region | Choose comma in the import dialog |
| Long numbers show as 1E+15 | Excel scientific format | Import as Text |
Garbled accents and symbols
The CSV is written as UTF-8, which handles every alphabet. When you double-click it, some versions of Excel on Windows read it as an older encoding instead, so characters like é, ü or ñ turn into two odd symbols. Import it deliberately:
- 1
Open a blank workbook in Excel.
- 2
Choose Data, then From Text/CSV, and pick the file.
- 3
Set File Origin to 65001: Unicode (UTF-8).
- 4
Check the preview, then click Load.
Google Sheets and LibreOffice read UTF-8 correctly without extra steps.
Leading zeros disappear
A value like 00123 is stored as text in the CSV. Excel sees digits and turns it into the number 123. In the import dialog, click Transform Data or Edit and set the column type to Text before loading. This applies to postcodes, phone numbers, product codes and account numbers.
Dates change
A date such as 03/04/2025 means 3 April in some countries and 4 March in others. The CSV stores it as text, and Excel reads it using your computer's regional settings. To control it, import the column as Text and convert it yourself, or choose the date format and locale in the import step. Writing dates as 2025-04-03 avoids the ambiguity completely.
Everything lands in one column
Some regional settings expect a semicolon as the separator, so a comma-separated file does not split. Use the import dialog and choose Comma as the delimiter. The related problem is covered in CSV opens in one column in Excel.
Other routes
If you need an Excel file again, CSV to Excel builds a workbook without the double-click guesswork. For the full picture of what a CSV holds, read what is kept and lost and the basics in how to convert Excel to CSV.
CSV opening problems: FAQ
Why do accents look wrong when I open my CSV in Excel?
Excel read the UTF-8 file in the wrong encoding. Import it with Data, From Text/CSV and choose UTF-8.
How do I keep leading zeros?
Import the column as Text instead of letting Excel guess.
Why did my dates change?
Excel interprets text dates with your regional day and month order. Choose the format when importing.
Is the CSV from the tool broken?
No. It is valid UTF-8 with comma separators. The problem is how it is opened.
Do Google Sheets and LibreOffice have the same issue?
They handle UTF-8 and delimiters through an import dialog and usually read the file correctly.
What date format is safest?
Year-month-day, such as 2025-04-03.
Why do long numbers show as 1E+15?
Excel uses scientific notation. Import those columns as Text.
Can I get an XLSX instead?
Yes, with CSV to Excel.
Import instead of double-click
Use the import dialog, choose UTF-8 and set identifier columns to Text. The data in the CSV was right all along.
