Skip to content

OpenDocument Text to PDF converter

ODT to PDF renders the OpenDocument Text file through our office engine, using the document's saved layout as the starting point.

  • Converted with Office engine · input deleted within 24 h
  • Free: 5 conversions a day · 5 MB each
  • Higher limits →

From real runs

What you get — and what changes

  • Paragraph text Kept

    ODT body text exported to selectable PDF text in both the rich and Feedback Atlas runs.

  • Headings Kept

    Writer heading text remained visibly separated and appeared in the extracted PDF text order.

  • Tables Changed

    Table values survived, but extracted PDF text listed headers and cells in vertical groups rather than grid rows.

  • Lists Kept

    Bullets and numbered actions rendered as visible list markers in the PDF output.

  • Footnotes Changed

    The footnote printed at the bottom of the page as static text, not as an editable note object.

  • Images Kept

    The rich ODT's tiny PNG rendered with its figure text in the PDF output.

  • Pagination Changed

    The rich ODT exported to two pages, while the sample ODT exported to three pages under server fonts.

Sample conversions

Rich Writer document

Input
ODT converted from the rich DOCX, containing headings, numbered steps, a metrics table, a footnote, and an image.
Output
Our office engine produced a 24 KB, two-page PDF with selectable text. The table was readable but extracted as separated columns.

Feedback Atlas ODT

Input
Repository sample ODT with board-prep text, a metrics table, bullets, and action items.
Output
The PDF was 52 KB and three pages. Text extraction kept the table values and list markers, but pagination differed from the DOCX-derived sample.

A real OpenDocument Text → PDF run

We converted our OpenDocument Text sample (8 KB) with Office engine on 2026-09-11. It took 381 ms and produced a 51 KB PDF file, 6.3× larger than the input. The engine raised no warnings.

Input · sample.odt · 8 KB

OpenDocument text: 15 paragraphs, 3 headings, 1 table, 0 pictures

Paragraphs
15
Headings
3
Tables
1
Rows
3
Slides
0
Pictures
0
Archive parts
6

Output · sample.pdf · 51 KB

PDF 1.6, 1 page, selectable text (LiberationSans-Bold, LiberationSans-BoldItalic, LiberationSerif-Bold, LiberationSerif-Italic), 0 image objects

Version
1.6
Pages
1
Fonts
LiberationSans-Bold, LiberationSans-BoldItalic, LiberationSerif-Bold, LiberationSerif-Italic
Images
0
Text layer
yes

Options and when to change them

filter
Use only when an advanced our office engine PDF export filter string is required for a controlled Writer workflow.

Do it yourself

LibreOffice

bash
soffice --headless --convert-to pdf --outdir out input.odt

Server fonts and Writer layout settings can change page count, so compare the exported PDF before signing off.

OpenDocument Text to PDF by API or MCP

The HTTP API and the MCP server run the exact engine this page uses (Office engine); the response carries the same warnings the web converter shows. Check support first with GET /api/v1/pairs?from=odt&to=pdf.

curl
curl -X POST https://filetypeconverters.com/api/v1/convert \
  -H "Authorization: Bearer $FTC_API_KEY" \
  -F "file=@input.odt" -F "from=odt" -F "to=pdf" \
  --output output.pdf
API reference

When this is the wrong conversion

  • If you need Word editing after an OpenDocument handoff, use /convert/odt-to-docx instead.
  • If the table needs to become spreadsheet data, PDF will make the cells harder to recover.
  • If the ODT depends on local fonts, export from the same our office engine setup used to design the file.

OpenDocument Text to PDF questions

Will ODT to PDF keep my Writer table?

The table renders visually in the PDF. Text extraction from our run showed the values, but not as clean row records.

Can the page count change from the office engine?

Yes. The sample ODT became three PDF pages on the server, so font and layout differences should be checked for formal documents.

Are ODT footnotes still interactive in PDF?

No. The marker and note text are printed into the PDF page and no longer behave like Writer footnote fields.