Turn a Markdown design doc into a Word file people can review

Design docs · RFCs · runbooks · postmortems · technical specs

Engineers write design docs in Markdown because it lives next to the code: it diffs cleanly, goes through pull-request review, and never fights you over formatting. Then review time comes, and the audience — PMs, security reviewers, executives, customers — wants a Word document or Google Doc they can comment on.

Most converters technically produce a .docx but butcher exactly the parts a design doc depends on: the architecture comparison table loses its borders, the code samples turn into flat gray text, and the H2/H3 structure — the skeleton of the whole document — disappears from Word's navigation pane.

→ Convert your design doc now (free, no sign-up to try)

Built for the structure of engineering documents

• Real heading styles (H1–H6) — Word's outline view and Google Docs' document tab work, so reviewers can jump between sections.
• Bordered tables with shaded headers — capacity plans, API matrices, and trade-off tables stay readable.
• Syntax-highlighted code blocks — schemas, configs, and snippets look like code, not like a paste accident.
• Task lists — rollout checklists (- [x]) render as real checkboxes.
• Optional table of contents, page size (Letter/A4), and a monochrome theme for formal deliverables.

A workflow that keeps Markdown as the source of truth

1. Keep writing the doc in your repo as design.md — versioned, reviewed in PRs.
2. When it's time to circulate: paste or upload it to md→docx and export.
3. Share the .docx directly or import it into Google Docs for commenting. The Markdown stays canonical; the Word file is a build artifact.

Shipping docs continuously? The API and CLI can generate the .docx in CI, so every merged change to design.md produces a fresh reviewable document.

FAQ

Does the exported file work in Google Docs?

Yes — upload the .docx and Google Docs imports the tables, code blocks, and heading outline correctly.

Is it free?

Try a couple of exports with no sign-in, then 5 more free with a Google account. Unlimited exports are $2/month.

My doc was written by an AI assistant — does that matter?

Not at all — it's all Markdown. See Claude → Word and ChatGPT → Word.

Also see: Claude → Word · ChatGPT → Word · CLI, API & agent skill