How to Convert XLS to CSV

An XLS is an Excel spreadsheet: a rich workbook that can hold multiple sheets, formulas, formatting, colors, and charts. A CSV is the opposite in spirit, a plain text file where each row is a line and each value is separated by a comma. Converting XLS to CSV is how you strip a spreadsheet down to nothing but its raw data.

That plainness is exactly the point. Almost every database, programming language, and data tool reads CSV effortlessly, so it is the universal handoff format when you need to move the numbers and text out of Excel and into something else. The trade is that everything except the values is left behind.

Because the conversion deliberately discards everything but the data, the whole skill of doing it well is knowing what you are giving up and making sure the raw values survive cleanly. This guide walks through exactly what a spreadsheet loses on the way to CSV, why the two formats are built so differently, the small set of rules that keep your columns from breaking, and the encoding and delimiter details that cause most real-world headaches. Get those right and CSV becomes what it is meant to be: a frictionless bridge from Excel into anything else.

What survives and what is lost

This conversion is lossy in a structural sense, not a numerical one. The cell values come through intact, but the spreadsheet machinery around them does not, because CSV has no way to store it. Knowing this in advance prevents nasty surprises when you open the result.

A rich workbook versus a line of text

To understand what is lost, it helps to see how far apart these two formats sit. An XLS is a structured binary workbook. Under the hood it uses Microsoft's Compound File Binary container holding a stream encoded in BIFF, the Binary Interchange File Format, whose typed records store not just cell values but formulas, number formats, fonts, colors, merged ranges, defined names, and charts.^[1] A cell in XLS knows its data type, its display format, and how it relates to a formula elsewhere; the file is a small relational world.^[2]

A CSV is the opposite: a plain text file where each line is a row and commas separate the fields, standardized in RFC 4180.^[3] It has no notion of data types, no styling, no second sheet, and no formulas. A number and a piece of text look identical on the line; there is only text separated by delimiters and line breaks. That radical simplicity is exactly why almost every database, programming language, and analytics tool reads CSV effortlessly, but it is also why the conversion is fundamentally one of subtraction.

How the conversion flattens a sheet

The conversion itself is straightforward once you know the two formats. The converter reads the chosen worksheet out of the XLS, and for each cell it takes the displayed value, not the machinery behind it. A cell containing a formula contributes its last calculated result; a cell formatted as currency or a date contributes the text that was showing on screen; a styled, colored, bordered cell contributes only its bare value. It then walks the sheet row by row, joining each row's values with commas and ending each row with a line break, and writes the whole thing out as text.^[4]

Everything structural is dropped at this stage because CSV has nowhere to put it: formulas collapse to values, formatting vanishes, and any sheet other than the one being exported is simply ignored. This is why the operation is lossy in a structural sense even though not a single number is altered. The data is faithful; the spreadsheet around it is gone.

The CSV rules that prevent broken columns

CSV looks trivial but has a small, important rulebook that keeps columns from breaking, and a good converter follows it automatically. The RFC 4180 conventions handle the awkward cases where the data itself contains the very characters used as separators.

These rules are why a converted CSV sometimes shows quotation marks around certain fields when you open it in a text editor. That is not an error; it is the format protecting your columns. Trouble only appears when a file ignores the rules, which is why exporting from a tool that respects RFC 4180 matters.

Why CSV is barely a format at all

Part of what makes CSV both universal and occasionally frustrating is that it is less a strict specification than a shared convention. Comma-separated values predate almost every other format still in daily use; the idea of separating fields with commas and rows with line breaks goes back to the earliest days of computing, long before anyone wrote it down formally. For decades there was no single authoritative definition, which is why subtle variations, different delimiters, different quoting, different line endings, still circulate today.

The closest thing to a canonical description arrived in 2005 as RFC 4180, which set out the common conventions: fields separated by commas, records separated by line breaks, and double quotes used to wrap fields that contain commas, quotes, or newlines.^[3] It is documented as an informational memo rather than a rigid mandate, and it explicitly acknowledges that many tools deviate from it.^[4] That looseness is the source of both CSV's strength and its quirks: because the format asks almost nothing of a program, virtually everything can read it, but because it guarantees almost nothing, the same file can be interpreted slightly differently by two tools. Knowing this frames the practical advice throughout this guide: always open the result once and confirm it imported the way you expect.

Convert XLS to CSV, step by step

1. Open the converter and add your XLS

   Open the FileFormer document converter and drop your XLS in. It converts on your device, so the spreadsheet is never uploaded.

2. Choose CSV as the output

   Select CSV. The cell values from your sheet are written out as comma-separated lines of text.

3. Pick the right sheet

   A CSV holds a single sheet. If your workbook has more than one, make sure the sheet you need is the one being exported.

4. Convert and download

   Export the CSV and open it in a text editor or the target program to confirm the columns line up as expected.

Details worth checking

CSV looks simple but has a few edges that trip people up. Open the result once before you rely on it. Cells that themselves contain commas get wrapped in quotation marks so the columns stay correct, which is normal. Dates and long numbers can shift appearance because CSV stores text, not Excel's cell types, so a value formatted as a date in Excel becomes whatever text was showing.

Encoding, delimiters, and regional quirks

Two invisible details cause most of the real-world friction with CSV: character encoding and the choice of delimiter. Because CSV is just text, the bytes that represent accented letters, currency symbols, or non-Latin scripts depend on the file's encoding. A CSV saved as UTF-8 preserves any character correctly; one saved in an older regional code page can turn accented names into garbled characters when opened elsewhere. When your data has anything beyond plain English letters, exporting as UTF-8 is the safe default.

The delimiter is the other trap. RFC 4180 defines the comma as the separator, but in regions where the comma is used as the decimal mark, spreadsheet software commonly writes a semicolon instead so that "3,14" is not mistaken for two fields.^[3] If your columns land in one jumbled column when the receiving program opens the file, the delimiter is almost always the cause: the file uses one separator and the importer expects another. The data is identical; only the punctuation between fields differs, and pointing the importer at the right delimiter fixes it instantly.

Where a CSV export is the right tool

CSV shines in exactly the situations where a spreadsheet's richness would only get in the way. Because it is the lowest common denominator of tabular data, it is the format almost every system agrees to speak.

The thread running through these is that the receiving system wants the values, not the presentation. When a database, a script, or another program is going to do its own formatting, calculation, and display, handing it a stripped CSV is cleaner and more reliable than a full workbook it would have to parse. This is also why CSV endures despite being one of the oldest and plainest formats in computing: its very lack of features is what makes it universally portable.

When not to convert to CSV

Do not convert to CSV if you need to keep formulas, multiple sheets, or any formatting. CSV cannot hold them, and once they are gone the only way back is to redo them in a spreadsheet. If you are simply moving to a newer Excel, converting XLS to XLSX keeps the whole workbook intact.

Reach for CSV specifically when a database, script, or data tool needs a clean feed of rows and columns. And keep the original XLS, since the CSV is a one-directional export that cannot rebuild the spreadsheet you started from. If you later need it back in Excel, converting CSV to Excel reimports the data, though not the lost formatting.

It helps to think of the CSV as a snapshot rather than a living document. It captures the values exactly as they stood at the moment of export, with formulas already resolved to numbers, and it has no way to update itself if the source changes. If the underlying data is still evolving, keep working in the XLS or an upgraded XLSX and re-export a fresh CSV whenever a downstream system needs the current figures. Treating the spreadsheet as the source of truth and the CSV as a disposable export avoids the trap of editing the flat file and then wondering why your formulas and formatting are gone for good.