What the Markdown to DOCX Converter does
This converter turns Markdown into a Word document (.docx) with real structure: # headings become Word's Heading 1-6 styles (so the navigation pane and a table of contents work), lists become numbered and bulleted lists, pipe tables become Word tables with a repeating header row, links become clickable hyperlinks, and block quotes and code keep their own styles.
Pasting rendered Markdown into Word usually gives you look-alike formatting - big bold text instead of headings, typed bullets instead of lists - which breaks outlines, accessibility and house styles. Converting the source keeps the meaning. It runs in your browser; your text is not uploaded.
How to use it
- Paste Markdown, drop a .md file, or load an example.
- Optionally set the document title (stored in the file's properties; the first heading is used otherwise) and the paper size.
- Choose Convert to DOCX. Check the outline - it is exactly what Word's navigation pane will show - and the preview.
- Read the unsupported-syntax notes, then download the DOCX and apply your own template or styles in Word if needed.
Reading the results
The outline lists every heading with its level. If a heading level jumps (a ### straight after a #), Word will show the gap too, and screen-reader users navigating by heading will notice it.
Unsupported syntax is reported rather than guessed: images become visible [Image: alt text] placeholders, raw HTML is kept as literal text, and footnotes and maths stay as their source text. Nothing is silently dropped.
Styles are standard Word styles (Heading 1-6, List Paragraph, Quote, Hyperlink, Table Grid) plus one custom Code Block style, so a corporate template applied afterwards restyles the document without manual clean-up.
Worked example: a project README
The README example has 4 headings - Tidewater (level 1) and Installation, Usage and Contributing (level 2) - so the Word outline shows one title and three sections.
Its numbered installation steps become a Word numbered list of 3 items, the contributing bullets become a bulleted list with a nested second level, and the options table becomes a 3-column Word table whose first row repeats on every page. The column alignment markers :---, :---: and ---: become left, centred and right-aligned cells.
The two fenced bash blocks use the Code Block style in Consolas, the block quote uses Word's Quote style, and the contributing-guide link is a real external hyperlink. The horizontal rule becomes a bottom border on an empty paragraph.
Limitations: what the result does not prove
- Images are not embedded, because a Markdown file only references them by path or URL; each becomes a placeholder with its alt text for you to replace in Word.
- Raw HTML, footnotes, maths, definition lists and syntax highlighting are not converted. They are listed in the notes and kept as text.
- It follows CommonMark for the common constructs, with GitHub tables, strikethrough and task lists, but it is not a full CommonMark implementation; unusual edge cases (deeply nested lazy continuation lines, for example) may be read differently from GitHub.
- Page layout is simple: one section, 2.54 cm margins, Calibri 11 pt. Apply your template in Word for anything more.
Privacy: where your data goes
Everything you paste, type or drop is processed in this browser tab. It is not uploaded, logged, stored or sent to analytics. Session recording and tag-manager scripts are switched off on this page.
Standards and sources
- CommonMark specification - checked 19 Sep 2026
- ECMA-376 Office Open XML File Formats - checked 19 Sep 2026
- GitHub Flavored Markdown specification (tables, task lists, strikethrough)
Frequently asked questions
How do I convert Markdown to a Word document?
Paste the Markdown or drop the .md file, choose Convert to DOCX and download. Headings, lists, tables, links, quotes and code are mapped to Word's own styles, so the document behaves like one written in Word rather than a formatted copy.
Will my Markdown headings work in Word's navigation pane?
Yes. Each # to ###### heading is written with Word's built-in Heading 1 to Heading 6 style and outline level, which is what the navigation pane and automatic tables of contents read. The outline shown on this page is the same list.
Are Markdown tables converted to real Word tables?
Yes. GitHub-style pipe tables become Word tables with the Table Grid style, a bold header row that repeats across pages, and the alignment given by the colons in the delimiter row. Escaped pipes (\|) inside cells are kept as characters.
What happens to images in my Markdown?
They are not embedded, because the picture files are not part of the Markdown text. Each image becomes an italic [Image: alt text] placeholder in the document so you can see where to insert it, and the notes count how many there were.
Is HTML inside the Markdown rendered?
No. Raw HTML is written into the document as literal text, and the preview on this page shows it as text too. That is deliberate: it keeps scripts and hidden markup out of both the page and the document.
Does it support task lists and strikethrough?
Yes. - [ ] and - [x] items become list items starting with an empty or ticked ballot box, and ~~text~~ becomes Word strikethrough, both following GitHub Flavored Markdown.
Last reviewed by the A2Z.Tools team against the sources listed above.
