Convert Markdown to a Word .docx file
Turn Markdown — including AI output — into a real .docx using Word’s own heading, list and table styles. Built in your browser, no upload.
- Runs in your browser
- Files are never uploaded
- Free, no account
Why this exists
Markdown has quietly become the format everything technical is written in — READMEs, notes, documentation, and now the output of every chatbot. Word is still the format organisations run on. Getting from one to the other usually means pasting into Word and spending twenty minutes fixing headings that arrived as plain bold text and bullets that arrived as literal hyphens.
This page writes a genuine .docx instead: a zip containing
[Content_Types].xml, word/document.xml, a styles part and a
numbering part, assembled to the same OOXML structure Word itself produces.
What maps to what
| Markdown | Word |
|---|---|
# … ###### | Heading 1 to Heading 6, with real outline levels |
**bold**, *italic*, ~~strike~~ | Character formatting on the run |
`inline code` | The HTML Code character style — Consolas on a grey ground |
| Fenced code blocks | HTML Preformatted paragraphs, one per line, shaded |
- item / 1. item | List Paragraph with a real numbering definition, three levels deep |
- [x] task | A bulleted item prefixed with ☑ or ☐ |
> quote | The Quote style — indented, italic, with a left rule |
[text](url) | A real hyperlink with a relationship entry, clickable in Word |
| GFM pipe tables | A Table Grid table with a bold, repeating header row |
--- | A bottom paragraph border |
 | An italic [image: alt] placeholder — see below |
Styles, not hard formatting
This is the difference between a converter you can use at work and one you cannot. A heading written as "18 pt bold dark blue" looks identical to one written as Heading 1 — until you try to do anything with it:
- References → Table of Contents finds nothing, because a TOC is built from outline levels.
- The navigation pane is empty, so a long document has no structure to jump around in.
- Applying your organisation's template does nothing, because there are no styles to restyle.
- Accessibility checkers flag the document, and screen readers cannot skim it by heading.
- Export to PDF produces no bookmarks.
Using Word's built-in style ids means all five of those work the moment the file opens.
The AI-output workflow
The most common reason to be on this page is that a chatbot produced something useful and it needs to become a document. A sensible sequence:
- Ask for the answer in Markdown explicitly — most models will oblige and stay consistent.
- Copy the whole reply, including the heading hierarchy and any tables.
- Paste it here and set a document title, which also names the downloaded file.
- Open the .docx and apply your organisation's template. Because the headings are real styles, the whole document restyles at once.
One clear-eyed note: this conversion is entirely local, but whatever you pasted into the chatbot already went to that company. If the source material was confidential, that decision was made upstream of this page.
Images and other limits
- Images are placeholders. An
almost always points at a remote address, and this page makes no network requests of any kind. Rather than fetch it silently, we mark the position and let you insert the image yourself. - Raw HTML in the Markdown is stripped to its text. Use HTML to Word if HTML is the primary source.
- Footnotes and definition lists are not part of core GFM and come through as ordinary paragraphs.
- Nested lists are supported to three levels, which is Word's practical limit for a single numbering definition too.
Opening the result elsewhere
The file is standard OOXML, so it opens in Microsoft Word (2007 onwards), LibreOffice Writer, Google Docs, Apple Pages and anything else that reads .docx. Google Docs and LibreOffice both map Word's built-in style names onto their own equivalents, so headings stay headings there too.
Prefer a PDF? Markdown to PDF. Prefer HTML? Markdown to HTML. Coming the other way, DOCX to Markdown reverses this trip.
Questions
Is this a real .docx or a renamed HTML file?
A real one. The output is a zip containing [Content_Types].xml, the document part, a styles part and a numbering part — the same OOXML structure Word itself writes. It opens in Word, LibreOffice, Pages and Google Docs.
Which Markdown features are supported?
Headings one to six, bold, italic, strikethrough, inline code, fenced code blocks, links, ordered and unordered lists with nesting, task lists, block quotes, horizontal rules and GFM tables.
Why do headings use Word styles rather than big bold text?
Because styles are what make the navigation pane, an automatic table of contents and your organisation’s template work. Hard-coded formatting looks the same but breaks all three, and cannot be restyled later.
Are the bullets real Word lists?
Yes. A numbering definition is written into the document, so bullets and numbers renumber themselves when you edit, and demoting an item with Tab behaves normally.
Is this safe for confidential AI output?
The conversion is, entirely — the text is turned into XML and zipped by JavaScript in this tab. What you already pasted into the chatbot is a separate question, and one this page cannot help with.