Convert Markdown to DOC

How it works

The Markdown is parsed into a document tree first, not transformed line by line. That distinction matters for nested lists and for fenced code, both of which depend on context that a line-by-line pass would lose.

The tree is then emitted as a word-processing document: headings become heading styles, list items become list paragraphs at the right level, emphasis becomes character formatting, links become hyperlink fields, and fenced code becomes a monospaced block. The result is written in the legacy .doc container.

Why styles rather than formatting

A heading in the output is a Word heading style, not merely large bold text. This is invisible until someone needs a contents page, a navigation pane or a consistent restyle, at which point it is the difference between a document that cooperates and one that has to be rebuilt.

What Markdown cannot ask for

Page size, margins, headers and footers, fonts, and anything else about presentation. Markdown has no vocabulary for these, so the document takes them from the default template. If a submission has formatting requirements, apply them in the word processor after conversion rather than expecting the Markdown to carry them.

The .doc caveat

This is a format from before 2007 and it is chosen under duress. If nothing is forcing it, .docx is better in every measurable way. If a portal or an internal system is forcing it, this is the shortest route from a repository file to something it will accept.

Markdown's structure becomes Word's structure

The conversion is more useful than it sounds because Markdown is almost entirely structure. A # is a heading, a - is a list item, a fenced block is code — and each has a direct equivalent in a Word document.

So headings become real heading styles rather than bold text, which means a contents page can be generated and the whole document can be restyled at once. Lists nest properly. Links stay clickable.

That is a genuinely better result than pasting rendered Markdown into Word, which carries appearance and no structure at all. What does not come across is anything Markdown itself does not define: diagrams, footnote extensions, and front matter.