Excel to CSV: What Actually Breaks, and Why Your Exports Keep Getting Rejected
"Excel to CSV" is one of the most searched conversions there is, which is odd for something that sounds like it should need no explanation: File → Save As → CSV. It needs explaining because that menu option quietly does several things wrong, and every one of them is invisible until the CSV is opened somewhere else and the data is wrong.
Here is what actually breaks, and what a conversion has to get right instead.
A workbook is not a sheet, and CSV only holds one
CSV is a flat, single-table format. A .xlsx file is a container that can hold dozens of sheets — Excel's Save As dialog converts whichever sheet is currently active and silently drops the rest. If your workbook has a "Summary" tab and a "Raw Data" tab, and Raw Data was open when you saved, you get Raw Data. The Summary tab isn't in an error message anywhere; it's just gone.
The fix isn't a setting — it's converting each sheet you need separately, one CSV per tab. Any tool that promises to export "the workbook" to one CSV is either picking one sheet for you or flattening tabs together in a way nothing downstream expects.
Formulas leave, values stay — which is usually right, but check it
A cell showing ₹45,200 might actually contain =SUM(B2:B14). CSV has no concept of a formula, so a conversion has exactly one option: write out the computed value, 45200. That's almost always what you want — the person receiving the CSV needs the number, not your formula — but it means a CSV export is a snapshot. If the source sheet changes after you export, the CSV does not follow it. Re-export after the last edit, not before.
The date that becomes a different date
Excel stores a date as a serial number and only displays it as 03/04/2026 because the cell is formatted to. When that cell is written to CSV, what lands in the text file is whatever the display format says — and display format is set by locale. A sheet built on a US machine writes 03/04/2026 (4 March); a sheet built on an Indian or UK machine, with the same underlying date, may write the same string to mean 3 April. The CSV itself is just text: 03/04/2026 carries no locale, so the program that opens it next guesses, and it guesses using its own regional settings, not yours.
This is invisible in the file. It only shows up when a date column comes out one month or one day off after a round trip, and by then nobody remembers which machine did the export. If a CSV is going somewhere date-sensitive — a payroll import, a booking system — check the actual column values against the source sheet after converting, not just that a date-shaped string is present.
Encoding, not corruption
A CSV that shows names like ’ or garbled accented characters wasn't corrupted — it was saved in one text encoding and opened assuming another. Excel's own Save As CSV has historically defaulted to a Windows codepage rather than UTF-8, which is fine until the file contains a rupee sign, an umlaut, or any character outside plain ASCII, and fine until it's opened on a different system that assumes UTF-8. The visible symptom (garbled text) looks like data loss; the actual cause is a mismatched encoding declaration, and the original characters are usually still recoverable if you know which encoding produced the file.
What converting in the browser avoids
The Excel to CSV tool reads the workbook and exports one sheet to CSV at a time, entirely in your browser — nothing is uploaded anywhere. It writes formula cells as their computed values, the same "value, not formula" behavior described above, because that's the only thing a CSV can hold. It does not fix a locale-ambiguous date for you (nothing can, without knowing which locale produced it) — but it does mean you're converting the exact sheet you opened, not whichever tab happened to be active, and you're not sending a spreadsheet that might contain names, salaries, or account numbers to a server to find out.
If the next step is the reverse — turning a CSV back into a workbook — the CSV to Excel tool is built for the matching failure mode: it explains why leading zeros disappear on the way back in, and how to stop it.
Frequently asked questions
Why did only one sheet convert when my workbook has five?
CSV has no concept of multiple sheets, so a conversion can only ever produce one table at a time. Convert each sheet separately, once per tab you need.
My formulas turned into plain numbers. Is that a bug?
No — that's the only thing CSV can store. A formula like =SUM(B2:B14) is written as its result, 45200, because a CSV cell holds text, not a calculation. If the source data changes later, re-export; the CSV won't update itself.
A date column looks shifted by a month after I open the CSV somewhere else. What happened?
The date was almost certainly written using one region's date order (day-month vs month-day) and read back using a different one. The CSV file itself doesn't record which order was used — check the actual values against the source workbook rather than trusting the shape of the string.
The CSV shows strange characters where accented letters should be. Is the data lost?
Usually not — it's an encoding mismatch between how the file was saved and how it's being read, not data loss. Re-saving or re-opening with the encoding set to UTF-8 on both ends usually recovers it.
The Excel to CSV tool runs in your browser — your workbook is never uploaded to any server.