Convert an ODT File to PDF

Converting an .odt file to PDF is unusual among document conversions because the format's reference application is free: LibreOffice reads OpenDocument Text natively, with no import filter in the path, so its PDF export is the authoritative rendering of the file. This page covers that export in detail — tagged PDF, PDF/A archiving, and the hybrid PDF option that embeds the editable source — plus a batch command line and what to expect if you convert through Microsoft Word instead.

Published July 20, 2026 · Last updated August 5, 2026

Why there is no one-click converter on this page

Laying out an .odt takes a full word-processing engine — style inheritance, line breaking, frame anchoring — that browsers do not expose to local pages. Since the format's own engine, LibreOffice, is free and converts perfectly, the honest answer is to use it, as shown below.

Disclosure: this page contains affiliate placeholder links. If they were live, we could earn a commission at no extra cost to you.

AFFILIATE PLACEHOLDER: Recommended desktop PDF suite (placeholder link)

How to convert an ODT to PDF (step by step)

Method 1 — LibreOffice Writer's Export as PDF (authoritative)

Open the .odt in LibreOffice Writer, its native application, so no import conversion happens at all.
Choose File → Export As → Export as PDF to open the PDF Options dialog.
On the General tab keep Tagged PDF enabled for accessibility, pick JPEG compression around quality 90 for images, and tick an Archive (PDF/A) profile if the file must stay readable for decades.
Click Export, choose the file name and folder, and save the PDF.

Worth knowing in the same dialog: Hybrid PDF embeds the full .odt inside the PDF so LibreOffice users can reopen and edit it later, and the Links tab converts the table of contents and cross-references into working internal PDF links.

Method 2 — The command line for folders of files

soffice --headless --convert-to pdf --outdir ./out contract.odt
soffice --headless --convert-to pdf --outdir ./out *.odt

To force archival output in a batch, name the filter with options: soffice --headless --convert-to 'pdf:writer_pdf_Export:{"SelectPdfVersion":{"type":"long","value":"2"}}' *.odt exports PDF/A-2b. Close any open LibreOffice window first — headless mode won't start while the desktop app holds the user-profile lock.

Method 3 — Microsoft Word (when it's all you have)

Open the .odt in Word, which converts it through its OpenDocument import filter.
Review the layout — inherited styles, text frames, and list numbering are the usual drift points — then File → Export → Create PDF/XPS.

Treat this as a fallback: the PDF reflects Word's interpretation of the file, not the layout its author saw in LibreOffice.

How it works

OpenDocument Text is an open standard (OASIS ODF, ISO/IEC 26300) — a ZIP archive whose content.xml holds the document body and styles.xml the named styles, with images under a Pictures/ directory and metadata in meta.xml. Like .docx, an .odt stores no pages: pagination is computed at layout time from styles, font metrics, and page-master definitions. The decisive difference is governance of the rendering. OOXML's de facto reference renderer is proprietary Word; ODF's reference renderers are the open-source suites themselves, so the format's authoritative layout engine is the same free program you export the PDF from. Conversion fidelity is therefore not a gamble — it is exact by construction when you export from Writer.

Writer's PDF export is also unusually rich because both sides are open. With Tagged PDF enabled it writes a logical structure tree (headings, paragraphs, tables, alternative text) alongside the drawn content, which screen readers and reflow views consume. Heading structure becomes PDF outline bookmarks; cross-references and TOC entries become internal GoTo links. The PDF/A profiles disable anything the ISO 19005 archival standard forbids — encryption, external references, non-embedded fonts — and transparency is flattened where the chosen profile requires it.

Where fidelity does break is any path through a foreign engine. Word's ODF filter maps OpenDocument's style-inheritance model onto Word's own, and constructs without a clean equivalent — frame-anchored objects, some list-numbering schemes — get approximated before layout even begins. If a PDF must match what the author saw, export from the suite the file was written in.

Worked example: a 56-page consulting contract

Test file: services-agreement.odt, 214 KB — 56 pages, 142 numbered clauses with three levels of list numbering, 38 cross-references of the form "see Clause 12.3", a generated table of contents, and two signature-block frames anchored to the last page. Writer's Export as PDF with Tagged PDF and default JPEG settings produced services-agreement.pdf, 342 KB, 56 pages in under two seconds: all 38 cross-references and every TOC line were live internal links, and the heading structure appeared as a two-level bookmark tree. Re-exporting as PDF/A-2b grew the file to 458 KB from full font embedding. A hybrid export (PDF + embedded source) came to 561 KB and reopened in Writer byte-identical to the original .odt. The same file exported from Word 2021's ODF filter produced 57 pages — clause numbering restarted at one point and pushed a signature frame over the page boundary — which is exactly the class of drift the native route avoids.

Frequently asked questions

What is the most accurate way to convert an ODT to PDF?

Export from LibreOffice (or Apache OpenOffice) itself, because ODT is their native format and no import filter runs, so the PDF matches the on-screen layout exactly. Third-party converters and Word all pass the file through an import step that can shift spacing and styles.

Can Microsoft Word convert an ODT file to PDF?

Word opens .odt files and can save them as PDF, but its OpenDocument support diverges on inherited paragraph styles, text frames and numbering, so layout can shift before the PDF is even made. Use LibreOffice for a faithful conversion and keep Word for files that must be edited in Word anyway.

What is a hybrid PDF and should I export one?

A hybrid PDF is a normal PDF with the complete .odt source embedded inside it, enabled by ticking Hybrid PDF in LibreOffice's export dialog. Anyone can read it as an ordinary PDF, while LibreOffice users can reopen it and edit the original document, at the cost of a larger file.

How do I batch-convert many ODT files to PDF?

Run soffice --headless --convert-to pdf --outdir ./out *.odt in the folder; LibreOffice converts every file without opening a window. Close any running LibreOffice instance first, since headless mode will not start while the desktop application holds the profile lock.

Should I pick PDF/A when exporting an ODT?

Choose PDF/A when the document must remain readable long-term, for instance legal filings and records, because it embeds all fonts and bans external dependencies, encryption and JavaScript. For everyday sharing, a regular tagged PDF is smaller and supports transparency without workarounds.

Does the exported PDF keep footnotes, cross-references and the table of contents?

Yes, they are rendered exactly as laid out, and with Tagged PDF enabled the export also writes real internal links for the table of contents and cross-references, plus PDF bookmarks from the heading structure. Fields are frozen at their values at export time.