ODS to XLSX resolves to our table engine, so OpenDocument sheets are parsed into table data and written as a new Excel workbook.
From real runs
| Element | Result | What happens |
|---|---|---|
| Sheet names | Kept | Pipeline and Notes both appeared as sheet names in the generated XLSX workbook.xml. |
| Text cells | Kept | Company names, owner names, and the Notes tab text were readable in the XLSX worksheet XML. |
| Numeric cells | Kept | ARR values and the 254500 total were written as numeric cells in sheet1.xml. |
| Dates | Changed | OpenDocument date values became ISO timestamp strings in the XLSX output rather than Excel date-typed cells. |
| Formulas | Lost | The rich workbook's formula was represented only by its cached value, with no formula attribute in the output XML. |
| Merged cells | Changed | The merged report title was flattened into a table header plus generated column names for the empty merged cells. |
| OpenDocument styling | Lost | ODS styles, widths, pinned panes, charts, and comments are not represented in the table engine value model. |
Pipeline and Notes both appeared as sheet names in the generated XLSX workbook.xml.
Company names, owner names, and the Notes tab text were readable in the XLSX worksheet XML.
ARR values and the 254500 total were written as numeric cells in sheet1.xml.
OpenDocument date values became ISO timestamp strings in the XLSX output rather than Excel date-typed cells.
The rich workbook's formula was represented only by its cached value, with no formula attribute in the output XML.
The merged report title was flattened into a table header plus generated column names for the empty merged cells.
ODS styles, widths, pinned panes, charts, and comments are not represented in the table engine value model.
We converted our OpenDocument Spreadsheet sample (10 KB) with Table engine on 2026-10-20. It took 3 ms and produced a 18 KB Excel XLSX file, 1.8× larger than the input. The engine raised 1 warning, listed below.
Input · sample.ods · 10 KB
OpenDocument spreadsheet: 2 sheets, 7 rows
Output · sample.xlsx · 18 KB
Workbook with 2 sheets (Pipeline, Notes); first sheet 5 rows, 25 cells, 0 formulas, header filter, fitted column widths
LibreOffice
soffice --headless --convert-to xlsx workbook.ods --outdir .LibreOffice may preserve more workbook presentation than this app's tabular-ir route, so compare if styling matters.
The HTTP API and the MCP server run the exact engine this page uses (Table engine); the response carries the same warnings the web converter shows. Check support first with GET /api/v1/pairs?from=ods&to=xlsx.
curl -X POST https://filetypeconverters.com/api/v1/convert \
-H "Authorization: Bearer $FTC_API_KEY" \
-F "file=@input.ods" -F "from=ods" -F "to=xlsx" \
-F 'options={"sheet":""}' \
--output output.xlsx| Key | Applies to | Type | Default |
|---|---|---|---|
| sheet | Reading OpenDocument Spreadsheet | string | |
| headerRowIndex | Reading OpenDocument Spreadsheet | number | 0 |
| dateHandling | Reading OpenDocument Spreadsheet | date · string | date |
| sheetName | Writing Excel XLSX | string |
/convert/ods-to-pdf when the goal is a faithful print-style snapshot instead of Excel data.No. The app route uses our table engine and writes cached values only, so formulas must be rebuilt in Excel.
Yes by default in the engine output. Our Pipeline and Notes tabs both appeared in the generated workbook.
The observed output serialized dates as ISO text. That avoids ambiguous display formatting but means date formatting may need cleanup in Excel.