ODT to PDF

Convert ODT to PDF

An OpenDocument Text file describes a document rather than a finished page. It names the typefaces it would like, the styles it applies and the margins it prefers, then leaves it to whichever program opens it to work out where line 14 ends and page 3 begins. That arrangement is perfectly fine while the file stays on the machine that wrote it. Send it somewhere else and the arithmetic gets redone with different ingredients.

Why the same .odt looks different on someone else’s machine

The font table inside an .odt is a list of names, not a set of font files. If your document asks for Liberation Serif and the recipient’s computer has never heard of it, their office suite quietly picks the nearest thing it owns. A stand-in face is almost never the same width, so lines rewrap, paragraphs grow or shrink, and the document repaginates. The table that sat neatly at the foot of page two now straddles a break; the image you positioned beside a paragraph drifts two paragraphs down. Change the default paper size from A4 to Letter as well and the damage compounds.

PDF ends that negotiation, because it stores the glyph outlines themselves rather than a request for them. This converter runs your file through LibreOffice Writer in headless mode: the document is laid out exactly once, every typeface it used is subset and embedded — bar the handful of core faces every PDF reader already ships with — and the result is written as fixed pages. From then on the document is the same object everywhere, on a phone, in a print shop’s workflow, or on a ten-year-old office PC.

What the PDF carries over from Writer

Freezing a layout is not the same as flattening it into a picture. The text stays text, so the PDF can be searched, selected, copied and read aloud by assistive software. Paragraphs styled with real heading styles are written out as the document outline, which is why a long report converted this way arrives with a usable bookmark panel at no extra effort. Hyperlinks remain live, images keep their full resolution, and a table of contents still points at the right pages.

Two behaviours surprise people. Margin comments are omitted, because the export treats them as editorial scaffolding rather than part of the document. Fields — page counts, document dates, cross-references — are resolved to the values they held at the moment of conversion and then stop moving. For most people that permanence is the entire point of asking for a PDF in the first place.

Choosing between PDF and an editable format

Reach for PDF when the writing is finished and the next thing that happens to the file is that someone reads, signs, files or prints it. Reach for something else when the document still has a life ahead of it:

• A colleague has to keep editing in Microsoft Word → ODT to DOCX preserves the styles as editable styles.
• The PDF came out heavier than the mail server will take, usually because of photographs → run it through Compress PDF.
• You are assembling a pack from several chapters or contributors → Merge PDF joins the converted files in order.

Why this one cannot run in your browser

Reproducing Writer’s typesetting — hyphenation, widow and orphan control, frame anchoring, footnote placement, style inheritance across a hundred pages — means running the office engine that defined those rules. No browser contains one. Your document is therefore sent to a machine that does: the transfer is encrypted, each conversion is given its own throwaway workspace and its own LibreOffice profile so requests never see one another, and the workspace is destroyed along with your original the moment the PDF has been handed back.