What goes wrong
| In the CSV | Excel shows | Why |
|---|---|---|
| 02134 | 2134 | It reads a ZIP code as a number and drops the zero. |
| 4111111111111111 | 4.11111E+15 | Excel keeps 15 significant digits. The 16th becomes 0, for good. |
| 3-5 | 5-Mar | It looks like a date, so it becomes one. |
| José | José | The file is UTF-8 but Excel opened it with an older Windows encoding. |
If you then press Save, the CSV is rewritten with Excel's version. The zeros and digits are gone from the file itself.
Fix 1: convert the CSV to .xlsx first
The quickest way. The CSV to Excel converter reads the file as text, so nothing is guessed. Values with leading zeros and numbers longer than 15 digits stay as text. Plain numbers become real numbers you can sum. Accents come through because the file's encoding is detected. Open the .xlsx and everything is as it was in the CSV.
Fix 2: import instead of opening
In Excel for Microsoft 365, Windows or Mac:
- Start with a blank workbook. Go to Data › From Text/CSV and pick the file.
- Check File Origin says 65001: Unicode (UTF-8). If the preview shows “José”, change it.
- Click Transform Data. Select the ZIP, ID or phone columns, then Data Type › Text. Choose Replace current if asked.
- Click Close & Load.
Fix 3: turn off the conversions
Recent versions of Excel for Microsoft 365 have File › Options › Data › Automatic data conversion (on a Mac, Excel › Preferences › Edit). Uncheck “Remove leading zeros”, “Convert digits to scientific notation” and the date option. It applies to every CSV you open after that. Older versions don't have the setting.
When you make CSVs for others
If you send CSVs that people will open in Excel, add a UTF-8 marker (a byte order mark) at the start of the file. Excel then reads accents correctly on a double-click. FileMixer adds it by default to every CSV it saves; uncheck Add a UTF-8 marker for systems that reject it.
For the leading zeros, the safest thing to send is an .xlsx with those columns stored as text. That's what FileMixer's converter produces.