ODS to Excel

Convert ODS to Excel

An OpenDocument Spreadsheet is what LibreOffice Calc, Collabora and a good many export buttons hand you when nobody specified Microsoft’s format. It is a perfectly respectable file — ODF is a published ISO standard — but it lands awkwardly in an Office world, where finance systems, HR portals and BI importers frequently accept .xlsx and nothing else. This converter re-saves the workbook through LibreOffice itself, so the sheets, values, styling and formulas arrive in Excel’s own format rather than in some third party’s approximation of it.

Two ZIP archives, two unrelated schemas

Open an .ods or an .xlsx with an archive utility and both reveal much the same thing: a ZIP full of XML. That resemblance is misleading. ODF keeps the entire workbook in a single content.xml; OOXML splits it into a workbook part, one XML part per worksheet, and a shared string table alongside them. Formulas are spelled differently too — ODF stores a sum as of:=SUM([.B2:.B10]) where Excel expects SUM(B2:B10). Nothing is simply copied across. Every cell, style and reference is parsed into memory and re-emitted in the other dialect.

Formulas are where the risk sits

Values, dates, number formats and cell styling translate dependably. Functions deserve a second look. The two applications share most of the everyday function set, but Calc carries functions that were never part of Excel’s vocabulary, and those cells come out as errors on the far side.

There is a subtlety that catches people out. The converter writes both the formula and the value it last calculated, so a cell can display an entirely plausible number while the formula behind it is broken. If the workbook is going to inform a decision, click into a few cells and read the formula bar rather than trusting what the grid shows you.

What survives, and what to inspect

• Dependable. Multiple sheets and their tab names, cell values, dates, currency and number formats, borders, fills, fonts, merged cells, column widths, frozen panes and named ranges.
• Usually fine, worth a glance. Conditional formatting, data validation lists and autofilters. Straightforward rules survive; elaborate ones are sometimes simplified on the way through.
• Check every time. Charts, which are rebuilt rather than transferred, and pivot tables, whose grid normally holds while the interactive extras around them may not.
• Not carried. Basic macros stored in the .ods, and any document-level scripting attached to it.

Is converting even the right move?

Sometimes it is not. If the recipient only needs to read the numbers and must not alter them, ODS to PDF settles the layout permanently and removes every question about formula compatibility. If what you actually want is the raw data for a script, a database load or a mail merge, run the result through Excel to CSV afterwards and you are left with plain delimited text and no formatting to argue about. And if you expect the file to come back edited from a Calc user later, Excel to ODSis the return leg — though it is worth keeping the original .ods rather than round-tripping twice.

Why this cannot run in your browser

Re-expressing a whole workbook from ODF into OOXML means implementing two large office file formats and the mapping between their function sets. That is LibreOffice’s job, and LibreOffice is a compiled desktop application rather than a JavaScript library, so your file is sent to our machine instead. It travels over an encrypted connection, is converted by a headless LibreOffice process in a directory created for that one request, and that directory — your .ods and the .xlsx alike — is destroyed once the download has been handed back.