XLSX is an Excel workbook with several sheets, formulas and cell formats. CSV is one table and nothing else, with no formulas and no cell formatting. LibreOffice sits between the two, and this page says exactly what happens to an XLSX file on the way to becoming a CSV one.
What runs when an XLSX file becomes CSV
LibreOffice 24.2, on a machine we rent and watch. Your XLSX file is uploaded once, LibreOffice runs once, the CSV comes back, and neither file is kept. XLSX to CSV is one of the 3649 pairs that engine was probed on with a real file, which is why it has a page here and why the pairs the probe could not prove do not.
What survives from the XLSX into the CSV
Every value, as a value. What a formula worked out lands in the CSV as the number it produced, ready for anything that reads CSV.
A CSV that anything can open. No version, no schema, no library: this is the format you reach for when the thing on the other side is a script rather than a person.
What XLSX to CSV costs you
Everything that is not the content itself: styling, headings, images, and any structure the XLSX file used to describe itself. A CSV is one flat thing, on purpose.
Formulas, replaced by what they currently work out to. Measured on this pair: the SUM in the XLSX file arrives as its answer and not as a SUM, so the CSV is a snapshot and not a model.
Every sheet but the first. LibreOffice writes one sheet into a CSV because a CSV has no way to hold two, and it takes the first one. A twelve-tab workbook comes back as one table, and the engine says so in a header rather than letting you find out later.
Where XLSX and CSV files come from
XLSX. Excel writes it, and so does nearly everything with an export to Excel button: Google Sheets, Salesforce, a bank statement download. It holds 1,048,576 rows and 16,384 columns, which is why it replaced the older binary.
CSV. Everything writes it and nothing agrees on it. There is an RFC, 4180, and it describes common practice rather than commanding it: quoting, escaping and line endings all vary by producer. A CSV is the lowest common denominator, which is both why it is everywhere and why it surprises people.
If a model is going to read the CSV
Structure is what survives from the XLSX file, and structure is what a model needs. XLSX in, CSV out, with the heading tree intact instead of flattened into one long paragraph.
XLSX to CSV, measured rather than promised
Running XLSX to CSV against the real engine with a real file, LibreOffice wrote 89 bytes of CSV in 1.1 seconds, machine otherwise idle. That is one XLSX file on one day and not an average, which is why the number is given together with the file that produced it.
The XLSX to CSV verdict was reached by reading the internal type and finding a witness word, meaning the output was read back and recognised. Which check was used matters, because they do not all prove the same thing, and a status code of 200 proves nothing whatsoever about whether the CSV file has anything inside it.
The same XLSX file, sent somewhere else
Other outputs the probe measured out of an XLSX file, so the cost of choosing CSV can be read against something. Sizes do not compare across engines, because each family was probed with its own XLSX witness file.
XLSX to PDF: 18,965 bytes in 1.1 seconds, verified by a format signature.
XLSX to HTML: 2,269 bytes in 1.1 seconds, verified by reading the internal type and finding a witness word.
Other ways into CSV, and what they measured
Among the published routes into CSV, XLSX is the first largest output of the 5 measured. The witness files differ, so this ranks the probe run and not your document.
JSON to CSV: 39 bytes in under a tenth of a second.
XLS to CSV: 89 bytes in 0.9 seconds.
ODS to CSV: 89 bytes in 1.1 seconds.
YAML to CSV: 39 bytes in under a tenth of a second.
What we will not pretend about XLSX to CSV
An XLSX file over 25 MB is refused before the upload finishes rather than after it, so you do not wait for a rejection.
An XLSX to CSV run that passes 90 seconds is killed, and the LibreOffice process is killed with it. A run left behind would sit on one of the machine's two cores until somebody noticed.
LibreOffice is serialised on purpose, one document at a time per worker, because each soffice instance takes 150 to 300 MB on a machine with 3.8 GB. Measured ceiling: 23 XLSX conversions in flight and roughly 0.9 a second sustained. Past that the queue answers 429 rather than falling over, which was tested at 32 at once.
Two thirds of the pairs you could imagine in this family do not exist, and it is worth knowing why before you go looking for one. LibreOffice converts inside whichever application opened your file: from a spreadsheet it writes spreadsheets, flat text, HTML and PDF, and it will not write a .docx no matter how it is asked. It returns nothing at all rather than something wrong. Of 113 combinations probed on this engine, 64 came back with a real file and the rest were refused outright.
This pair is one of the 64. It was proved by sending a real XLSX file through the live route and reading the CSV that came back: not its extension, its internals, plus a marker word planted in the source and found again in the output. The traits named further up this page come from a second probe that looks for each of them one by one.
The engine tells the truth about the first-sheet limit rather than hiding it: the response carries an X-Sheets-Exported header saying so. It is mentioned here because a header is easy to miss and a missing sheet is not.
One XLSX file at a time, chosen in the browser. There is nothing else to set up and nothing else on offer.
XLSX to CSV: what people ask
What actually converts my XLSX file to CSV?
LibreOffice does it, 24.2, on a machine we rent and watch. Not a browser trick and not somebody else service: the XLSX file is uploaded once, LibreOffice runs once, the CSV comes back, and neither file is kept afterwards.
How long does XLSX to CSV take?
On the file the probe used, LibreOffice took 1.1 seconds and wrote 89 bytes of CSV. That is one real measurement on one real XLSX file, not an average and not a promise about yours: a larger XLSX takes longer, and past 90 seconds the run is stopped.
What do I lose going from XLSX to CSV?
The one to know about first: Everything that is not the content itself: styling, headings, images, and any structure the XLSX file used to describe itself. A CSV is one flat thing, on purpose.
Why is my CSV so much smaller than the XLSX?
Because a CSV holds the content and nothing else. Styling, fonts, images, headings and the file structure around them are all gone by design. Formulas are gone too, replaced by the values they had worked out at the moment of conversion.
My workbook had several sheets. Where are the others?
Only the first one is in the CSV, because a CSV is one table and has no way to hold a second. LibreOffice takes the first sheet. If you need them all, convert to ODS instead, or run the conversion once per sheet from your own file.
Is XLSX to CSV free?
There is a free allowance every month, and one XLSX to CSV conversion costs half a credit against it. When the allowance runs out the tool says so and stops, rather than quietly handing you a worse CSV.