What it does
Your Markdown, translated properly.
Word doesn’t speak Markdown. The plugin runs your note through Compositor,
the same typesetting engine as this site, so what lands in .docx is a real Word document — not
pasted text. And unlike the Pandoc-based
plugins, it doesn’t mangle your wikilinks, callouts or embeds on the way out.
Native heading styles
# through ###### become Word’s own Heading 1–6. The navigation pane, automatic table of contents and outline view all work out of the box.
Tables that behave
Markdown tables become real Word tables with proper header rows — resizable, sortable, editable by whoever you send them to.
Smart typography
Straight quotes become curly, dashes become em dashes — everywhere except inside code, which is left exactly as you wrote it.
Obsidian-aware
Wikilinks, callouts and embedded images (including ![[wikilinks]]) survive the export — where Pandoc plugins drop or garble them — and YAML frontmatter becomes the document title and author.
Code blocks & quotes
Fenced code keeps a monospaced block style; blockquotes get Word’s quote style. Lists — nested, numbered, mixed — keep their structure.
No configuration
One command: “Export to Word”. The output uses the clean, standard Word look, so it fits any workplace without explaining anything.