Rich DOCX to OpenDocument
- Input
- 12 KB DOCX with styled headings, a table, a footnote, a block quote, and a small PNG.
- Output
- The 19 KB ODT kept heading text, table cells, footnote text, and Pictures/100000010000000100000001028F582B9643F048.png.
DOCX to ODT uses our office engine's office import path, so Word content is rewritten into an OpenDocument Text package.
From real runs
| Element | Result | What happens |
|---|---|---|
| Container format | Changed | The output became an ODT zip with content.xml, styles.xml, metadata, and a Pictures directory when media existed. |
| Headings | Kept | The rich document retained heading structure in content.xml after the Word-to-OpenDocument rewrite. |
| Tables | Kept | The migration table kept its headers and numeric cells as OpenDocument table markup. |
| Footnotes | Kept | The reviewer footnote text moved into content.xml and appeared near the reference in extracted text. |
| Images | Kept | The test PNG was stored under Pictures with a generated OpenDocument media filename. |
| Figure captions | Changed | Extracted text showed the alt text and caption twice around the tiny image after conversion. |
| Word-specific metadata | Changed | The ODT output kept editable content but rewrote package metadata and application-specific Word settings. |
The output became an ODT zip with content.xml, styles.xml, metadata, and a Pictures directory when media existed.
The rich document retained heading structure in content.xml after the Word-to-OpenDocument rewrite.
The migration table kept its headers and numeric cells as OpenDocument table markup.
The reviewer footnote text moved into content.xml and appeared near the reference in extracted text.
The test PNG was stored under Pictures with a generated OpenDocument media filename.
Extracted text showed the alt text and caption twice around the tiny image after conversion.
The ODT output kept editable content but rewrote package metadata and application-specific Word settings.
We converted our Word DOCX sample (11 KB) with Office engine on 2026-09-11. It took 539 ms and produced a 20 KB OpenDocument Text file, 1.8× larger than the input. The engine raised no warnings.
Input · sample.docx · 11 KB
Word document: 18 paragraphs, 3 headings, 1 table, 0 embedded images; fonts Consolas
Output · sample.odt · 20 KB
OpenDocument text: 15 paragraphs, 3 headings, 1 table, 0 pictures
LibreOffice
soffice --headless --convert-to odt --outdir out input.docxOpen the ODT in LibreOffice and check captions, styles, and pagination before sending it to OpenOffice or Writer users.
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=docx&to=odt.
curl -X POST https://filetypeconverters.com/api/v1/convert \
-H "Authorization: Bearer $FTC_API_KEY" \
-F "file=@input.docx" -F "from=docx" -F "to=odt" \
--output output.odtYes for the rich sample. Our office engine placed the image in the ODT Pictures folder and kept a body reference to it.
They are carried into the OpenDocument content rather than flattened to plain body text. Complex reference formatting can still shift when opened in another editor.
The rich run exposed both the image alternative text and the caption text. Review figures after conversion when accessibility text and visible captions differ.