ODT to PDF

Convert your ODT files to PDF, right here in your browser.

Free
Private
No limits
No upload

... or drop files here

Files never leave your device

Add a ODT file to convert.

Frequently asked questions

What is actually inside a ODT file?

A .odt file is a ZIP archive whose first entry has to be an uncompressed mimetype marker, followed by the XML that holds the content and its styling.

Are my files uploaded to a server?

No. Your ODT file is read and the PDF is built entirely inside your browser, so nothing ever leaves your device.

Can I convert several files at once?

Yes. Add as many ODT files as you like and download the PDFs one by one, or all together as a ZIP archive.

Will the layout look exactly like the original?

The text, headings, lists and tables carry over and are laid out onto clean A4 pages. This is a content-faithful conversion rather than a pixel-perfect copy of the original formatting.

Is there a file size or file count limit?

No. Everything runs on your own device, so the only practical limit is how much memory your browser has available.

Do I need to install anything?

No. There is nothing to install and no account to create — the converter runs in any modern browser, on desktop and mobile alike.

Why convert ODT to PDF rather than just sending the .odt?

Because the recipient may not have anything that opens it. LibreOffice and OpenOffice read ODT natively and Word's support has been decent for years, but "decent" is doing work in that sentence — an .odt opened in Word can reflow, and Google Docs will convert it on import. A PDF removes the question.

Are my heading levels preserved?

Yes, and more reliably than from most formats. ODF marks a heading with its own element rather than with a style name that a converter has to recognise, so there is nothing to guess at — the document says what is a heading and the converter renders it as one.

What happens to images in my document?

They are left out. Pictures sit as separate files inside the archive, positioned by anchoring rules, and placing them approximately right means placing them wrong. The text, headings, lists and table data all come through.

Do my lists keep their numbering?

List items each come through on their own line with a bullet, so the grouping survives, but the numbering scheme and the indent levels of a nested outline do not — a multi-level list flattens to one level.

Will the PDF look like my LibreOffice document?

It will contain the same text with the same structure, laid out cleanly on A4 — not a copy of your page design. Fonts, colours, margins and page breaks are the converter's, not yours. If you need the design preserved exactly, LibreOffice's own File → Export as PDF does that, and does it well; this is for when you want it done in a browser without installing anything.

Is my file uploaded anywhere?

No. The archive is unzipped and parsed inside the browser tab and the PDF is written there. Nothing is transmitted to any server.

ODT is the text document of the OpenDocument Format — the format LibreOffice, OpenOffice and Google Docs export to, standardised as ISO/IEC 26300 and, unusually for an office format, designed in the open before it was implemented rather than documented afterwards.

That history shows in the file. An .odt is a ZIP whose `content.xml` describes the document in terms that are almost embarrassingly readable: a heading is a `<text:h>` element, a paragraph is `<text:p>`, a list is a `<text:list>` of items. There is no ambiguity to resolve about what a given block of text is meant to be, because the format says so directly.

This converter reads that structure and lays it out on A4 with the heading levels intact. If you work in LibreOffice and need to hand someone a file they can definitely open, this is the shortest route that does not involve uploading your document to anyone.

How to convert ODT to PDF

Add your .odt files
Drop them in or choose them, as many as you like. Each becomes its own PDF named after the original.
Convert
The archive is unzipped in the page and `content.xml` is walked in document order — headings, paragraphs, lists and tables, each recognised by its own element name.
Download
Save the PDF. The .odt is unchanged and never left your device.

What the converter reads

Headings: Recognised from the document's own `<text:h>` elements rather than guessed from formatting, and rendered as headings. This is the practical advantage of ODF being explicit about structure.
Paragraphs: Carried across in order, with the text of nested inline runs — spans, links, bookmarks — flattened into the paragraph they belong to.
Lists: Each item comes through on its own line with a bullet. The item text is preserved; the numbering scheme and indent depth of nested lists are not, so a deeply nested outline flattens to a single level.
Tables: Written row by row with cells separated and set in a monospaced face so columns stay aligned. Cell content is preserved; borders, shading and merged-cell spans are not.
Images and drawings: Not included. They are stored as separate files in the archive and anchored by rules this converter does not reimplement.
Footnotes, headers and footers: Not rendered. These live outside the main body flow in `content.xml` and in `styles.xml`, and are skipped.

ODT compared with DOCX

Both are ZIP archives of XML and both describe a document as a stream of styled paragraphs, so converting either is the same shape of job. The differences that matter here are small but real.

ODF names structure directly — a heading element is a heading element. OOXML instead makes everything a paragraph and attaches a style name, so a heading is a `<w:p>` whose style happens to be called "Heading2", and a converter has to match on that name. Both work; ODF simply says out loud what OOXML implies.

In practice this means an .odt written by LibreOffice tends to convert a little more predictably than a .docx that has been through several programs, each of which renamed the styles slightly. If you have the same document in both formats, the .odt is the marginally safer input.

Documents in non-Latin scripts

The standard PDF fonts cover Latin text only. When a document needs glyphs outside that range — Cyrillic, Greek, Arabic, Hebrew, any of the Indic scripts, Chinese, Japanese, Korean — the converter draws the pages using the fonts installed on your own device instead, which cover the full range and handle right-to-left text correctly, and embeds the finished pages.

Those pages read and print correctly. The trade-off is that their text is an image, so it is not selectable or searchable in the PDF. The alternative would be shipping tens of megabytes of font to every visitor, which is not a reasonable thing to do to someone who wanted to convert one file.

About the ODT format

.odt is the word-processing format OASIS introduced in 2005. It is published as an open specification under the name ISO/IEC 26300, so a file can be read without the program that wrote it.

A .odt file is a ZIP archive whose first entry has to be an uncompressed mimetype marker, followed by the XML that holds the content and its styling.

Files like this usually come out of LibreOffice Writer, Apache OpenOffice, and Collabora Online.

What comes through

body text
heading levels
bulleted and numbered lists
table rows and columns
embedded images
reading order

What does not

the exact page design
tracked changes
comments

Worth knowing

This is the format LibreOffice and Apache OpenOffice save in by default, and the one several governments standardised on precisely because no single vendor controls it.
Heading styles are read as structure rather than as big text, so the levels in the original become real headings rather than a guess based on font size.
This conversion is content-faithful, not pixel-faithful: text, heading levels and table columns survive, the original page design does not.

Information