Convert ODS to XLS
This conversion travels in two unhelpful directions at the same time: from an open standard to a proprietary binary, and from a current format to one with a 65,536-row ceiling. It is worth doing only when a specific destination refuses everything else, and it is worth checking the row count before you rely on the result.
Use this without the search next time. Prathom Workbench puts Prathom's tools in your toolbar.
Add to Chrome — freeDrop your ODS file here, or click to browse
Up to 50 MB. Deleted automatically after 30 minutes.
What it does
- Output opens in software written before the 2007 formats
- Sheets, formulas and formatting are carried across
- Sheets over 65,536 rows or 256 columns will not fit
How to use ODS to XLS
- 1
Check the row count first
OpenDocument has no ceiling at this scale and the destination format does. Anything near 65,000 rows needs a different plan.
- 2
Upload the .ods
A LibreOffice or OpenOffice spreadsheet, or one saved as OpenDocument by Excel.
- 3
Open the result where it is going
The point of this conversion is a specific piece of old software. Test it there rather than in a modern spreadsheet application.
How it works
The ODS is unzipped, its content XML read, and the workbook model written into the legacy compound binary structure. Sheets, cells, formulas, number formats and styles all have equivalents in the destination, so this is a re-encoding rather than an export of values.
The formulas stay live, which matters because the destination is usually a system that expects to recalculate the sheet.
Why this page is blunt about it
Most format conversions trade one property for another. This one gives up two and gains only compatibility.
The first loss is openness: a documented, inspectable ZIP of XML becomes a proprietary binary that needs specific software to read.
The second is capacity: no meaningful row ceiling becomes 65,536 rows and 256 columns per sheet, with silent truncation as the usual failure.
When it is nevertheless correct
When a system will not take anything else. Laboratory instruments, industrial control software, older accounting packages and some upload forms accept .xls and nothing newer, and no amount of preferring open formats changes what they will parse.
What to do instead when you can
XLSX if the destination allows it: modern capacity, smaller files, wide support. CSV if only the data is needed, since it has no limits and everything reads it. Keep the ODS as the working copy either way and convert on the way out, so the master stays in the format that will still be readable later.
Giving up two things at once
This conversion moves from an open, documented ZIP of XML to a proprietary binary, and from the modern row ceiling down to 65,536. Both are losses, and there is one good reason to accept them: software that reads nothing else.
That software genuinely exists. Older accounting systems, laboratory equipment,
industrial tooling and a surprising amount of internal enterprise software were
built against .xls and will not take .xlsx, let alone ODS.
If that is the situation you are in, this is the right conversion. If it is not —
if the other end simply prefers Excel — .xlsx is the better target: it keeps the
row headroom and is still a documented format that ordinary tools can open.
Examples
A form for a legacy accounting package
Tiny and structural, which is the shape that downgrades safely. The accounting package accepts it, which is the only reason the conversion happened.
A dataset well past the ceiling
More than double what the format allows. Export to CSV instead, which has no limit, or split the sheet before converting.
Frequently asked questions
Why is this described as going backwards?
Because it gives up two separate things at once. OpenDocument is a published ISO standard whose files can be inspected without special software; .xls is a proprietary compound binary. Separately, OpenDocument has no practical row ceiling while .xls stops at 65,536. Neither loss buys anything except compatibility with old software, which is the only good reason to do it.
Should I convert to XLSX instead?
If the destination accepts it, yes, without hesitation. XLSX keeps the row headroom, produces much smaller files, and is what current software expects. Choose .xls only when a specific system rejects the newer format, which still describes plenty of laboratory instruments, industrial controllers and older internal tools.
Do formulas survive the downgrade?
Ordinary ones do, and they recalculate normally in the destination. The exceptions are functions that OpenDocument defines and the older Excel formula set never had, which may arrive as errors. Since the destination is by definition old software, that risk is higher here than in most conversions. Open the file where it is going and scan for error values.