Release-note TXT
- Input
- Plain UTF-8 text with a title, owner, steps, two space-aligned score rows, and accented plus Japanese characters.
- Output
- The 10 KB DOCX kept all text and Unicode, created no tables, and wrote no media folder.
TXT to DOCX gives plain text a Word container, but it does not infer all the layout that a human sees in monospaced text.
From real runs
| Element | Result | What happens |
|---|---|---|
| Text content | Kept | Plain text content became editable Word paragraphs in the generated DOCX files. |
| Unicode | Kept | The rich DOCX output preserved café, naïve, and 東京 in document.xml. |
| Line wrapping | Changed | Our document engine grouped plain lines into Word paragraphs instead of preserving fixed-width positions. |
| Space-aligned columns | Lost | Name Score and metrics columns were not converted into Word tables. |
| Numbered lines | Changed | Numbered instructions stayed as visible text but were not represented as Word numbering in the rich run. |
| Headings | Changed | The sample TXT produced one Heading2 style reference, showing that text structure is inferred heuristically. |
| Images | Lost | TXT cannot contain embedded images, so the DOCX output had no word/media files. |
Plain text content became editable Word paragraphs in the generated DOCX files.
The rich DOCX output preserved café, naïve, and 東京 in document.xml.
Our document engine grouped plain lines into Word paragraphs instead of preserving fixed-width positions.
Name Score and metrics columns were not converted into Word tables.
Numbered instructions stayed as visible text but were not represented as Word numbering in the rich run.
The sample TXT produced one Heading2 style reference, showing that text structure is inferred heuristically.
TXT cannot contain embedded images, so the DOCX output had no word/media files.
We converted our Plain text sample (440 B) with Document engine on 2026-09-11. It took 37 ms and produced a 11 KB Word DOCX file, 25× larger than the input. The engine raised no warnings.
Input · sample.txt · 440 B
13 non-empty lines, 71 words
Output · sample.docx · 11 KB
Word document: 11 paragraphs, 1 heading, 0 tables, 0 embedded images; fonts Consolas
pandoc
pandoc input.txt -t docx -o output.docxUse Markdown instead of plain TXT when you need deliberate headings, tables, links, or lists in Word.
The HTTP API and the MCP server run the exact engine this page uses (Document engine); the response carries the same warnings the web converter shows. Check support first with GET /api/v1/pairs?from=txt&to=docx.
curl -X POST https://filetypeconverters.com/api/v1/convert \
-H "Authorization: Bearer $FTC_API_KEY" \
-F "file=@input.txt" -F "from=txt" -F "to=docx" \
--output output.docxNo in the tested files. Space-aligned score and metrics columns stayed as paragraph text rather than Word table cells.
Yes for the rich sample. The generated document.xml preserved accented Latin text and Japanese characters.
Our document engine reads TXT with lightweight document heuristics in this service. A line that looks like a section label can receive a Word heading style.