ODS is an OpenDocument workbook, the native format of LibreOffice Calc. PDF is a frozen page layout with no heading structure a machine can rely on. LibreOffice sits between the two, and this page says exactly what happens to an ODS file on the way to becoming a PDF one.
What runs when an ODS file becomes PDF
LibreOffice 24.2, on a machine we rent and watch. Your ODS file is uploaded once, LibreOffice runs once, the PDF comes back, and neither file is kept. ODS to PDF 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 ODS into the PDF
The ODS page layout, exactly. LibreOffice renders your ODS file the way it would print it, so margins, columns, page breaks, headers and footers land in the PDF where the author put them.
Fonts, embedded in the PDF, so your ODS document reads the same on a machine that has never had those fonts installed.
ODS tables, drawn as they were drawn. Borders, merged cells and column widths survive into the PDF because they are painted rather than re-described.
ODS cell formatting: number formats, colours and conditional fills print into the PDF as you see them on screen.
What ODS to PDF costs you
Editability. A PDF is the end of the line: nobody downstream can change a sentence without going back to your ODS file. Sometimes that is exactly the point, and sometimes it is exactly the problem.
Structure a machine can use. PDF has no heading hierarchy, no list semantics and no table model, so everything the ODS file knew about itself stops at the print stage. A program reading the PDF sees positioned glyphs and guesses the rest.
ODS formulas. Cells print into the PDF as their current values, the workbook logic does not travel, and neither does anything outside the ODS print range, which is what decides where the PDF pages cut.
Where ODS and PDF files come from
ODS. LibreOffice Calc and OpenOffice write it natively. It is ISO/IEC 26300, which is why several public administrations ask for it by name in procurement, and why a file that arrives as ODS often arrives from one of them.
If a model is going to read the PDF
Worth knowing before the PDF goes anywhere near an assistant: this is the wrong direction for that. A PDF is a set of positioned glyphs, and a model has to reconstruct the reading order before it can begin. If a machine rather than a person is going to read this ODS file, convert it to Markdown instead and skip the reconstruction entirely.
ODS to PDF, measured rather than promised
Running ODS to PDF against the real engine with a real file, LibreOffice wrote 12,884 bytes of PDF in 1.1 seconds, machine otherwise idle. That is one ODS file on one day and not an average, which is why the number is given together with the file that produced it.
The ODS to PDF verdict was reached by a format signature, meaning at least four bytes unique to the format were found at the right offset. 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 PDF file has anything inside it.
The same ODS file, sent somewhere else
Other outputs the probe measured out of an ODS file, so the cost of choosing PDF can be read against something. Sizes do not compare across engines, because each family was probed with its own ODS witness file.
ODS to HTML: 2,066 bytes in 1.0 seconds, verified by reading the internal type and finding a witness word.
Other ways into PDF, and what they measured
Among the published routes into PDF, ODS is the number 18 largest output of the 26 measured. The witness files differ, so this ranks the probe run and not your document.
ODP to PDF: 20,929 bytes in 1.3 seconds.
RTF to PDF: 11,917 bytes in 1.1 seconds.
CSV to PDF: 12,680 bytes in 1.0 seconds.
EPUB to PDF: 61,941 bytes in 1.9 seconds.
MOBI to PDF: 62,207 bytes in 1.9 seconds.
What we will not pretend about ODS to PDF
An ODS file over 25 MB is refused before the upload finishes rather than after it, so you do not wait for a rejection.
An ODS to PDF 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 ODS 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.
One ODS file at a time, chosen in the browser. There is nothing else to set up and nothing else on offer.
ODS to PDF: what people ask
What actually converts my ODS file to PDF?
LibreOffice does it, 24.2, on a machine we rent and watch. Not a browser trick and not somebody else service: the ODS file is uploaded once, LibreOffice runs once, the PDF comes back, and neither file is kept afterwards.
How long does ODS to PDF take?
On the file the probe used, LibreOffice took 1.1 seconds and wrote 12,884 bytes of PDF. That is one real measurement on one real ODS file, not an average and not a promise about yours: a larger ODS takes longer, and past 90 seconds the run is stopped.
What do I lose going from ODS to PDF?
The one to know about first: Editability. A PDF is the end of the line: nobody downstream can change a sentence without going back to your ODS file. Sometimes that is exactly the point, and sometimes it is exactly the problem.
Is the PDF searchable afterwards?
Yes. The text in your ODS file is written into the PDF as text, not as a picture of text, so it can be searched and copied. What the PDF does not have is structure: no headings, no list model, no table model. It reads well to a person and parses badly to a program.
Is ODS to PDF free?
There is a free allowance every month, and one ODS to PDF 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 PDF.