Convert Markdown into a genuine Word document. Headings become Word's own heading styles, so they appear in the navigation pane and can be restyled; lists keep their nesting; tables get a bold header row; and bold, italic and inline code survive as real formatting. That matters because most converters produce an HTML file with a .docx extension — Word opens it, but the structure is fake, the styles are not editable, and it often warns that the file may be corrupted. This builds actual Office Open XML. The document is never uploaded.
| Markdown | Word |
|---|---|
| # Heading | Heading 1 style |
| - item | Bulleted list |
| 1. item | Numbered list |
| **bold** | Bold run |
| `code` | Consolas run |
| | table | | Table with bold header |
Yes — proper Office Open XML, built as Word writes it. Headings use Word's heading styles and appear in the navigation pane. Most online converters rename an HTML file instead, which Word opens but often flags as possibly corrupted.
No. The file is built in your browser.
Yes. Nesting depth is preserved and applied as Word indentation. Ordered lists carry a numbering definition, without which Word silently drops the numbers.
Fully. It is a normal Word document — change styles, use tracked changes, add comments.
Images referenced by URL are not embedded, and footnotes, task lists and HTML blocks are simplified. Headings, paragraphs, lists, tables, quotes, code and inline formatting all come through.
Word if the document will be edited or needs searchable text. PDF if it is final and must look identical everywhere.
This produces a genuine .docx — a ZIP of Office Open XML built with the docx library — rather than an HTML file given a Word extension, which is what most converters do. The difference is visible immediately: real headings appear in Word's navigation pane, styles are editable, and the file does not trigger the 'this file may be corrupted' warning that a renamed HTML file produces. Markdown is tokenised and flattened into a linear block list before anything Word-specific happens, because a document has no nested structure to mirror a Markdown tree — lists become individual items carrying their nesting depth, which is what Word's indentation actually needs. Keeping that flattening separate from the document construction means the mapping is covered by tests without building a document. Ordered lists need a numbering definition registered on the document; without one, Word silently drops the numbers and the list renders as unmarked paragraphs, so a definition is supplied. Inline styling survives as runs, with bold and italic nesting correctly and inline code switching to a monospaced font. Tables carry a bold header row. Everything runs in your browser.