Rich ODT to Word
- Input
- OpenDocument file with migration headings, numbered steps, a table, a block quote, one footnote, and one embedded PNG.
- Output
- The 9.1 KB DOCX kept heading styles, table markup, footnotes.xml, and word/media/image1.png.
ODT to DOCX turns OpenDocument Writer content into OOXML so Word users can edit the document without opening an ODT.
From real runs
| Element | Result | What happens |
|---|---|---|
| Paragraph text | Kept | ODT body text became editable Word paragraphs with the observed prose intact. |
| Headings | Kept | Heading styles from the rich ODT appeared as Heading1 and Heading2 references in document.xml. |
| Tables | Kept | OpenDocument tables became Word table markup with the metric labels and numbers preserved. |
| Footnotes | Kept | The DOCX included word/footnotes.xml and retained the reviewer footnote text from the ODT. |
| Images | Kept | The rich ODT image moved into word/media/image1.png and remained referenced as a drawing. |
| List definitions | Changed | The converted DOCX had fresh Word numbering definitions rather than the original OpenDocument list model. |
| Package metadata | Changed | Our office engine rewrote the file as Microsoft OOXML with new relationships and application metadata. |
ODT body text became editable Word paragraphs with the observed prose intact.
Heading styles from the rich ODT appeared as Heading1 and Heading2 references in document.xml.
OpenDocument tables became Word table markup with the metric labels and numbers preserved.
The DOCX included word/footnotes.xml and retained the reviewer footnote text from the ODT.
The rich ODT image moved into word/media/image1.png and remained referenced as a drawing.
The converted DOCX had fresh Word numbering definitions rather than the original OpenDocument list model.
Our office engine rewrote the file as Microsoft OOXML with new relationships and application metadata.
We converted our OpenDocument Text sample (8 KB) with Office engine on 2026-09-11. It took 459 ms and produced a 8 KB Word DOCX file, about the same size as the input. The engine raised no warnings.
Input · sample.odt · 8 KB
OpenDocument text: 15 paragraphs, 3 headings, 1 table, 0 pictures
Output · sample.docx · 8 KB
Word document: 18 paragraphs, 3 headings, 1 table, 0 embedded images; fonts Times New Roman, Courier New, StarSymbol
LibreOffice
soffice --headless --convert-to docx --outdir out input.odtWord may reflow the converted file differently from LibreOffice, especially around lists, tables, and fonts.
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=docx.
curl -X POST https://filetypeconverters.com/api/v1/convert \
-H "Authorization: Bearer $FTC_API_KEY" \
-F "file=@input.odt" -F "from=odt" -F "to=docx" \
--output output.docxYes in the tested rich document. Our office engine wrote a Word footnotes.xml part containing the original note text.
Not always. The content remains editable, but our office engine creates new Word numbering definitions that Word may lay out differently.
They can be. The rich test moved its PNG into word/media and kept a drawing reference in the Word document body.