Convert your Markdown to a downloadable Word document
This is a sample document that demonstrates Markdown to Word conversion.
Code is preserved as monospace text in the Word document.
Converting Markdown to Word makes it easy to share documents with non-technical users.
The usual way to get Markdown into Word is to render it somewhere, select all, and paste. That carries the web page’s fonts and colours across, headings become manually-sized bold text, and a reviewer’s first job is undoing your formatting.
Exporting instead gives you a document that behaves like one a colleague wrote. Headings use Word’s built-in Heading 1–6 styles, so the navigation pane fills in, Insert → Table of Contents finds every section, and dropping your organisation’s template over the file restyles the whole thing in one click. Tables are real Word tables, so reviewers can add a row without fighting the layout, and Track Changes works normally throughout.
Working with the file format rather than the Word workflow — .docx internals, scripting the conversion, or comparing against pandoc? The Markdown to DOCX converter covers the same export from that angle.
| Markdown | In the Word document |
|---|---|
| Headings (# to ######) | Word built-in Heading 1–6 styles |
| Bold and italic | Bold and italic character formatting |
| Links | Clickable Word hyperlinks |
| Tables | Real, editable Word tables |
| Fenced code blocks | Courier New with a shaded background |
| Blockquotes | Indented quotation paragraphs |
| Ordered and unordered lists | Numbered and bulleted lists |
| Task lists (- [x]) | Text prefixed with [x] or [ ] |
| Images | Left as  text — not embedded |
Images are the one thing that does not carry over. The conversion never fetches remote files — that is what keeps your document private — so an image stays in the text as  and needs inserting in Word afterwards. If you need images rendered in the exported file, the Markdown to PDF exporter renders them through the browser instead.
Yes. Markdown heading levels map to Word built-in Heading 1 through Heading 6 styles rather than just larger bold text. That means the Word navigation pane works, Insert > Table of Contents picks up your sections, and applying a company template restyles the whole document in a single click.
Pasting from a rendered preview brings the web page styling with it: fonts and colours are baked in as direct formatting, and headings arrive as manually enlarged bold text rather than heading styles. Word then has no document outline to work from, so the navigation pane and automatic table of contents stay empty. Exporting produces a properly styled document instead.
They run the same conversion and produce the same file. This page frames it around the Word workflow — styles, templates, reviewers, and Track Changes. The Markdown to DOCX page covers the same export from the file-format side, for people searching by extension or comparing against tools like pandoc.
Yes. Pipe tables become real Word table objects with a header row, so you can edit cells, resize columns, and apply Word table styles. They are not pasted in as images or as plain text.
Images are not downloaded and embedded — the image stays in the document as its literal  Markdown text. The conversion runs entirely in your browser and does not fetch remote files, which is what keeps your document private. Insert images in Word after exporting if you need them in the final file.
Task list items come through as list items prefixed with [x] or [ ] rather than as Word checkbox content controls. The state of every item is preserved and readable, but the boxes are not clickable in Word.
No. The .docx is generated locally in your browser and saved straight to your device. Nothing is uploaded, stored, or logged, so internal reports and unreleased drafts stay on your machine.