Coming soon — what we're building
Markdown to Word is the export path for writers who draft in Markdown but need to ship a .docx file to colleagues, clients, editors, or reviewers who live in Microsoft Word. Use cases: technical writers shipping documentation drafts to non-technical reviewers, consultants producing client-facing reports from Markdown notes, students submitting essays to professors who require DOCX, content teams handing off blog drafts to editors using Word's track-changes workflow, anyone bridging a Markdown-first authoring habit with a Word-first review audience.
Honestly: this isn't built yet
We're prioritising the inverse direction (Word → Markdown) because that's where the AI-prep demand sits. Markdown → Word is on the roadmap; if you have a strong use case, let us know — concrete demand moves it up.
OSS alternatives that work today
- Pandoc CLI — the gold standard. One command:
pandoc input.md -o output.docx. Handles headings, lists, tables, code blocks, footnotes, images. Supports customreference.docxtemplates for branded styling. Free, MIT-licensed. - marked + a DOCX library (e.g. docx) — DIY route for Node.js apps that need programmatic Markdown→DOCX inside an existing pipeline.
For the inverse direction (which we DO support)
If you have a Word document and want clean Markdown out of it, that's our existing tool: Word to Markdown. Upload .docx, get structured Markdown back ready for AI ingestion or Markdown-first authoring.