How to convert Markdown to Word

Write in Markdown, hand over a .docx, because that is what most people expect to receive.

Markdown is a pleasant way to write and an awkward thing to send to someone who expects a document. This produces a genuine .docx with the structure carried over.

Step-by-step

1. Paste your Markdown, or load a .md file.
2. Convert.
3. Download the .docx.

What carries across

• Headings become real Word heading styles, so a table of contents can be generated and the navigation pane works.
• Lists, ordered and unordered, including nesting.
• Bold, italic and inline code.
• Block quotes and code blocks.
• Links, as real hyperlinks.

Real heading styles matter

A heading that is merely large bold text looks like a heading and is not one. Word cannot build a table of contents from it, the navigation pane ignores it, and screen readers read it as ordinary text. Producing actual Heading 1 and Heading 2 styles is what makes the output a usable document rather than something that resembles one.

Styling afterwards

The .docx uses Word's built-in styles, so changing the look is a matter of changing the style — modify Heading 1 once and every heading follows. That is far better than the alternative, where each heading is independently formatted and consistency is your problem.

What Markdown cannot say

Markdown was designed for text that becomes web pages, and a few things a Word document routinely needs have no representation in it at all. There is no page break, no page size, no header or footer, no figure caption bound to its figure, and no cross-reference — nothing that lets "see section 3" update itself when section 3 moves.

None of that is a reason to avoid the workflow, but it does decide where the boundary sits. Write the content in Markdown, where the structure is easy to see and easy to diff, and treat the document furniture as something applied once, in Word, at the end. Trying to encode pagination in the source is where the approach stops paying.

The round trip is not lossless

Going Markdown to Word is a clean widening: everything in the source has somewhere to go. Coming back the other way is not, and the things that vanish are the collaborative ones — tracked changes, comments, and any style that was applied directly rather than through a named style.

So a document that has been through review in Word should not be converted back to Markdown and then forward again; the review is in the parts that do not survive. Where a document genuinely has to live in both worlds, pick one as the source of truth and treat the other as an export. Editing in both and converting in both directions loses somebody's work eventually, and it is rarely obvious which pass dropped it.

Frequently asked questions

Are headings real Word headings?

Yes. They use Word's built-in heading styles, so the navigation pane and automatic tables of contents both work.

Do tables convert?

Markdown tables become Word tables. Very wide ones may need column widths adjusting afterwards.

Is the file uploaded?

No. The .docx is assembled in your browser and downloaded directly.