Five methods, each one with a real walkthrough — Pandoc, an online converter, Mac TextEdit, Google Docs paste, and mdclaudy. The one you should use depends on whether you have a command line, a deadline, or both.
TL;DR — the direct answer in 30 seconds
To convert markdown to Word, the five practical methods in 2026 are:
- Pandoc — free, CLI, the most powerful method. Best for developers, batch jobs, and corporate template enforcement.
- Online converters (CloudConvert, markdowntoword.io) — fastest for one-off, but inconsistent on math, Mermaid, and tables.
- Mac TextEdit — does not actually parse markdown. Useful only as a manual fallback for plain text.
- Google Docs paste— works for prose, loses structure. Honest if you’re going to edit collaboratively anyway.
- mdclaudy — browser-based, designed templates, preserves math and Mermaid. Pick this if you want the .docx to actually look like something.
For the live tool, jump to /tools/markdown-to-word. For the rationale and the working commands, keep reading.
What you actually want from a markdown-to-Word converter
Before the methods, the bar. A converter is doing its job if the resulting .docx satisfies four conditions:
- Real Word styles. H1 maps to Heading 1, H2 to Heading 2, code to a Code style — not bold-18pt and monospace-direct-format on a thousand paragraphs.
- Structural elements preserved. Tables stay tables, code stays code, footnotes stay footnotes, math becomes editable OOXML, links stay links.
- Page furniture intact. Cover page (if the template has one), header, footer, page numbers, table of contents.
- Editable in Word. The reviewer should be able to turn on Track Changes and treat it as a normal document.
Two of the five methods below clear all four bars. One clears three. Two clear one or zero. The honest comparison comes at the end.
Method 1 — Pandoc (the developer’s answer)
Pandoc is the universal document converter John MacFarlane has been maintaining since 2006. If you have a CLI and twenty minutes, it’s the most powerful method on this list. Free, open source, runs offline. The output is genuinely good — real Word styles, editable math, footnotes, the works.
Install Pandoc
On macOS: brew install pandoc. On Windows: download the installer from pandoc.org/installing.html. On Linux: apt install pandoc or equivalent. Then verify with pandoc --version — you want at least 3.0.
The basic command
pandoc input.md -o output.docx
This works. It produces a .docx with default Pandoc styling — clean, functional, looks like a 2012 thesis. For most prose-only documents you can stop here. For anything with tables, math, or a corporate template, keep going.
The full command we’d actually run
pandoc input.md \ --from=gfm+footnotes+tex_math_dollars+pipe_tables \ --to=docx \ --reference-doc=template.docx \ --filter=mermaid-filter \ --toc \ --toc-depth=2 \ -o output.docx
Walking the flags:
--from=gfm+footnotes+tex_math_dollars+pipe_tables— enables GitHub-flavored markdown, footnotes, dollar-delimited math, and pipe-style tables. Without this, math and footnotes silently disappear.--reference-doc=template.docx— points to a styled Word file whose paragraph styles, fonts, header/footer, and page margins become the styles of the output. This is how you enforce a corporate template.--filter=mermaid-filter— a community npm package (npm install -g mermaid-filter) that converts Mermaid code blocks to embedded SVG images. Without it, Mermaid blocks stay as raw text.--toc --toc-depth=2— generates a table of contents from H1 and H2 headings, inserted at the top of the document.
Building a reference.docx
The reference document is a normal Word file whose styles Pandoc copies. Generate a starter with:
pandoc --print-default-data-file reference.docx > template.docx
Open template.docxin Word, edit the styles (Heading 1 font, body typeface, page margins, header/footer), save. Every future Pandoc conversion that points to this file inherits the styles. This is the closest equivalent in the Pandoc world to mdclaudy’s template picker, with the cost being that you build the template yourself.
When to pick Pandoc
Repeated conversions in a build pipeline. Batch jobs across folders. Strict corporate template enforcement. Working offline. Documents with heavy math or BibTeX citations (Pandoc handles --citeproc with style files). Avoid it for one-off proposals where the template work outweighs the writing work.
Method 2 — Online converters (CloudConvert, markdowntoword.io)
The EMD pages — markdowntoword.io, markdowntoword.net, markdowntoword.cc, and CloudConvert— exist for one job: paste markdown, download .docx, in under thirty seconds. They’re the fast-food option. Sometimes that’s exactly what you need; sometimes you bite into it and find the math missing.
The workflow
Open the page, paste your markdown into a textarea, click Convert, download the .docx. Some require email, most don’t. CloudConvert handles file uploads (drag a .md, get a .docx).
Where they win
- Speed. Open page → paste → download in 20 seconds.
- No install. Works on any machine with a browser, including a locked-down corporate laptop.
- No account.Most don’t require signup for small files.
Where they fall short
- No styles. The output uses direct formatting (Normal paragraph with hardcoded font size and weight) instead of real Heading 1, Heading 2, Code styles. Editing it in Word is painful.
- Math gets dropped. KaTeX
$x^2$typically appears as literal$x^2$text or vanishes entirely. - Mermaid disappears. Diagrams become unrendered code blocks at best, blank lines at worst.
- No template, no design. Defaults are Calibri 11pt on one-inch margins. Looks like a draft.
- Upload required. Your text goes to a third-party server. For confidential drafts, this is a hard no.
When to pick an online converter
A non-confidential one-off where you just need the .docx to exist — a homework assignment, a draft for personal use, a quick note to send to a parent who only opens Word files. For anything that has to look designed or contains math, pick a different method.
Method 3 — Mac TextEdit (the honest non-answer)
Some readers arrive here because they searched “convert markdown to Word on Mac without installing anything” and someone on Reddit suggested TextEdit. We want to save you the click.
TextEdit does not parse markdown. Open a .md file in TextEdit and you see the raw syntax — pound signs, asterisks, brackets — exactly as written. Saving it as .docx (File → Duplicate → Save As → Word 2007 (.docx)) produces a .docx that contains the markdown source as plain text. The reader sees # Heading literally, not a heading.
The only thing TextEdit can do is be the place you write rich text manually from scratch after the conversion fails everywhere else. That’s not a method; that’s retyping.
Use the browser converter at /tools/markdown-to-word instead. Same “nothing to install” property, actually converts the markdown.
Method 4 — Google Docs paste (the collaborative shortcut)
Google Docs picked up rudimentary markdown support in 2022. If you paste markdown into a Google Doc with the right setting enabled, headings, bold, italic, lists, and links convert. Tables, code, math, and footnotes do not.
Enable markdown in Google Docs
Open Google Docs. Click Tools → Preferences. Check Automatically detect Markdown. Save. From that point, when you paste markdown text, Google Docs interprets it.
The workflow
Copy your markdown source. Paste into the Google Doc. Headings get styled, bold and italic come through, lists work. Inline links convert. Then: File → Download → Microsoft Word (.docx). The downloaded file opens in Word with the same styles.
What it loses
- Tables (pipe syntax appears as literal text).
- Fenced code blocks (lose monospace, syntax highlighting).
- Math equations entirely.
- Footnotes (markdown
[^1]stays as text). - Mermaid diagrams.
- HTML inside markdown.
When to pick Google Docs paste
Prose-heavy documents where the final review will happen collaboratively in Google Docs anyway. If you and the reviewer both live in Google Docs and the document is mostly text, this is the path of least resistance. For anything structural, pick mdclaudy or Pandoc.
Method 5 — mdclaudy (the designed-output method)
Full disclosure: this is our product. We’ll be brief about why, then move on.
mdclaudy is a markdown editor whose entire pitch is the export. Write in a typography-aware editor (or paste markdown into the browser converter), pick one of three .docx templates (Memo, Report, Proposal), and the file that comes out looks designed — cover page, real Word styles, page numbers, header rule. Math becomes editable OOXML via the MathML bridge. Mermaid renders to embedded SVG. Footnotes survive. Code blocks get a real Code style.
The workflow
For one-off conversions: open /tools/markdown-to-word, paste markdown, pick a template, download. No account required for small files.
For repeat use: sign up (free tier, 50 documents, 5 exports a month), import your .md, write or revise in the editor, export to Word. Drafts live in your library; the .md remains the source of truth, exportable back to plain markdown at any time.
Where it wins
- Designed templates instead of raw default Word.
- Real Word styles — restyle the document globally by changing Heading 1, the way Word is meant to work.
- Math, Mermaid, footnotes preserved. Every structural element survives the conversion.
- No install.Browser-based. Works on a corporate laptop where you can’t install Pandoc.
- Optional AI in the editor for continue, rewrite, ask — opt-in per action, not a chat sidebar.
Where it doesn’t
- No batch conversion today. One file at a time in the browser. (Pandoc wins on batch.)
- No custom .docx template import yet. Three built-in templates cover most cases; a strict corporate template today means Pandoc.
- Upload required. The conversion runs on our server. For threat models that rule out uploads, run Pandoc locally.
When to pick mdclaudy
Client-facing documents that need to look designed. Proposals, reports, whitepapers. Anything with math you don’t want to retype. The case where you wrote in markdown for speed and need the output to land like you cared.
Pandoc is the right answer if you have a CLI and a Tuesday. mdclaudy is the right answer if you have a deadline and a client meeting.
Decision matrix — which method, when
| Your situation | Best method | Why |
|---|---|---|
| One-off proposal, needs to look designed | mdclaudy | Templates do the design work |
| Nightly build of a manual | Pandoc | Scriptable, version-controllable |
| Strict corporate Word template | Pandoc | --reference-doc applies your template |
| Document with KaTeX math | mdclaudy or Pandoc | Both convert to editable Word math |
| Confidential, no upload allowed | Pandoc | Runs entirely on your machine |
| Quick prose-only draft, will edit in Google Docs | Google Docs paste | Path of least resistance for collab |
| Locked-down corporate laptop, no install | mdclaudy (browser) | Browser-only, no admin rights needed |
| Throwaway file, no math, no design | Online converter | Twenty seconds, done |
Common pitfalls across all five methods
Three things go wrong no matter which method you use. Worth flagging before you hit Convert:
Inconsistent table rows
Every row of a markdown table needs the same number of pipe delimiters. If row 3 has four columns and row 5 has five, the parser either drops the extra cell or breaks the table entirely. Count your pipes.
Pipes inside cells
A literal | inside a table cell must be escaped as \|. Otherwise the parser treats it as a column delimiter and your row gets sliced wrong.
Local image paths
Markdown  with a relative path works in Pandoc if you run from the right directory; in mdclaudy if the image is uploaded to your library; not at all in online paste-based converters. The portable answer: use absolute URLs to hosted images, or upload to mdclaudy first.
Related guides
- Markdown to Word: convert .md to .docx with templates — the flagship guide and live converter.
- Markdown to RTF: when you need rich text, not Word — for the legal and government use cases.
- Markdown to Word vs PDF — when you’re not sure which format to send.
- Markdown to HTML: the developer’s guide — for the format you keep on the web.
- Markdown to PDF: the complete guide — for the format you send when you don’t want it edited.
Frequently asked questions
The honest final word
The five methods aren’t equally good — they’re good at different things. Pandoc is the answer for technical depth and repeat use. mdclaudy is the answer when the output has to look like something. Online converters are the answer when you’ve got thirty seconds. Google Docs paste is the answer for collaborative prose. TextEdit, with respect to Apple, is not an answer to this question at all.
The thing every method shares: markdown stays the source of truth. Whichever path you pick, keep the .md file. The conversion is for the reader. The writing stays yours.