Markdown to Word Converter

What this converter actually produces

It takes Markdown, converts it to HTML on the server, wraps that HTML in a minimal word-processing document, and downloads it as markdown-document.doc. Word opens the file and shows your headings, lists, tables and code blocks. What you get is a Word-compatible document, not a true Office Open XML .docx package: there is no Word style sheet, no page setup, no header or footer, and no document properties panel.

That distinction matters if you plan to hand the file to a publisher, a print workflow or a document management system. The file is HTML with a .doc extension and an application/msword content type, which is a long-standing compatibility trick. Word reads it, LibreOffice reads it, and Google Docs can usually import it, but it is not the same thing as a native Word file.

How the conversion runs

1. You paste Markdown into the editor and press Convert to HTML.
2. The Markdown is sent to the server and rendered with a GitHub-flavoured Markdown converter.
3. If sanitising is enabled, the resulting HTML is passed through an HTML purifier that removes scripts, event handlers and other unsafe markup.
4. The HTML returns to the page and appears in a read-only output panel.
5. Pressing Download .doc wraps that HTML in a document shell — doctype, head, a small inline stylesheet and a body — and saves the result as a .doc file in the browser.
6. If no HTML has been generated yet, the download button runs the conversion first, then saves the file.

The wrapper sets Arial as the body font, 1.6 line height and 24 pixels of padding, collapses table borders, and gives code blocks a monospace font with padding and a scrollbar. Those are the styles Word will use as a starting point.

One styling caveat

The exported stylesheet refers to CSS custom properties such as var(--tblr-border-color) and var(--tblr-primary). Those variables exist on the website but are not defined inside the downloaded file, so declarations that depend on them are invalid in Word and get ignored. In practice, table borders and the code background may not appear the way they do in the browser preview. The text, structure and hyperlinks are unaffected; the document simply looks plainer than the on-screen HTML.

How to use it

1. Paste your Markdown. The footer shows the input length and a rough word count, and the HTML panel shows its own character count and line count.
2. Leave Sanitize HTML checked unless you deliberately need raw HTML to survive.
3. Press Convert to HTML. The status card changes from “No HTML yet” to “HTML ready”.
4. Review the HTML if you like. It is read-only, so any correction has to be made in the Markdown and re-converted.
5. Press Download .doc. The status card reports that a .doc download is available once HTML exists.
6. Open the file in Word. If Word shows a format warning, allow it to open; the content is HTML, not a macro document.
7. Use Download HTML if you only need the converted markup as markdown-converted.html.

The sanitize option

With sanitising on, the purifier strips tags and attributes that could execute code, which is the safe choice for anything you did not write yourself. With sanitising off, raw HTML embedded in the Markdown is passed through unchanged; the page deliberately shows an amber warning toast in that case. Turning it off is useful when your Markdown intentionally contains HTML that the purifier removes, such as a <details> block or a custom style attribute. Only disable it for content you trust, and remember that Word will still interpret whatever survives.

What survives the trip

When this is the right tool

• Quick handoff. Someone asks for “a Word version” of a README or a spec and you need it in seconds.
• Editable drafts. The recipient can open the .doc, edit the text and save it as a real .docx from Word.
• Simple reports. Headings, paragraphs, lists and a table convert cleanly enough for review.
• HTML extraction. The intermediate HTML is useful on its own for a CMS or an email template.

It is the wrong tool when the document must follow a corporate template, carry page numbers, use defined Word styles, include a table of contents field, or survive a strict accessibility check. Those needs call for a real DOCX generator or a manual save-as from Word.

Limits

Input is capped at 200,000 characters per request, and larger Markdown is rejected rather than truncated. The conversion is server-side, so the document leaves your browser. The tool does not upload or embed local images: an image link points at its URL, and Word decides whether to fetch it. There is no batch mode, no multi-file merge, and no option to choose a page size, margin or font. The exported file always uses the same wrapper and the same name.

Privacy

Your Markdown is sent to the server to be converted. Do not paste confidential drafts, personal data or internal documents you would not submit through a web form. The page does not keep a document library or a conversion history, and the response returns only the generated HTML. Downloading the .doc happens locally in the browser from that HTML.

Common mistakes

• Expecting a .docx. The file is HTML-based with a .doc extension; save as .docx from Word if you need the real format.
• Blaming the converter for plain tables. The wrapper uses CSS variables that the exported file never defines, so some styling is dropped.
• Turning off sanitising for untrusted text. Raw HTML then passes straight through.
• Editing the HTML panel. It is read-only; change the Markdown and convert again.
• Assuming images are embedded. Remote images must be fetched by Word and can be blocked.
• Opening the file in a strict pipeline. Some systems reject HTML-based .doc files; convert to .docx first.

Frequently Asked Questions