Notes & knowledge

Markdown to Word document converter

Get Word document entities: headings, paragraphs, bullets, numbered lists, tables, code blocks, links, footnotes, and images.

Output: Word DOCX
Free: 5 conversions a day · 5 MB each
Deleted after 24 h · never used for training

Before you start

What to expect

Uploads are not used to train models, and retained files are deleted after 24 hours unless your account policy says otherwise.
Markdown semantics are preserved better than arbitrary visual styling; exact Word theme matching requires a reference template workflow.
Review wide tables, image links, and raw HTML before sending the DOCX to stakeholders.

What the output contains

A DOCX generated from Markdown structure, suitable for reviewers who need Track Changes or Word comments afterward.
Heading levels mapped to Word headings, with lists, links, and tables converted to editable Word objects.
Fenced code blocks preserved as monospace-styled text when the reference template supports it.
Corporate styles require a reference DOCX in DIY/API workflows; the default web output uses conservative styling.

A real run

Engineering design doc

Input: 4,200-word Markdown design doc with 36 headings, seven code fences, four GFM tables, two local diagrams, and 19 links.
Output: DOCX with editable headings, links, diagrams, and tables; one wide API-parameter table needed landscape formatting in Word after conversion.

Known failure modes and how they're handled

Code blocks lose the desired style: The default output keeps code readable, but exact corporate code-block styling needs a reference DOCX template.
Wide Markdown tables: Tables become editable Word tables, but very wide tables may overflow the page and need landscape layout or redesign.
Raw HTML inside Markdown: Simple inline HTML may pass through; complex HTML widgets should be simplified before Word conversion.
Images referenced by relative paths: Upload image assets with the Markdown or rewrite links to available files; private local paths cannot be fetched.

Command line

Do it yourself

pandoc --reference-doc

bash

pandoc design.md -o design.docx --reference-doc=reference.docx

Use a reference DOCX when styles matter; keep Markdown simple and standards-based.

Questions about this workflow

Can I use a corporate Word template?

The DIY/API pattern is our document engine --reference-doc. The default web workflow uses a conservative template unless advanced options are available.

Will code blocks stay monospace?

They are kept as code-like text, but exact colors and line wrapping depend on the Word style/template.