Markdown to Word
Convert Markdown (.md) into a Word document (.doc) that opens in Word, Pages or Google Docs with headings, lists, tables and links intact. Nothing is
Drop your Markdown file here
or click to browse files
Convert a Markdown (.md) file into a Word document you can open in Microsoft Word, Pages or Google Docs. Headings, bullet and numbered lists, tables, code blocks, links and emphasis are converted into real Word formatting rather than plain text, so the document is immediately editable and printable.
Typical uses: turning a README or technical note into a document for colleagues who do not use Markdown, handing a Markdown-based report to a client, or archiving notes in a format that opens anywhere. The conversion happens locally in your browser, so drafts and internal documentation are never uploaded.
How to convert Markdown to Word
Choose a .md file
Convert it
Download the Word document (.doc)
FAQ
Which Word format do I get?
A .doc file built from HTML that Word, Pages, Google Docs and LibreOffice all open natively. It keeps headings, lists, tables, links and inline code styling.
Will my images be included?
Images referenced by a public URL are included as links. Local images referenced by a relative path cannot be resolved by the browser, so those appear as alt text - upload them to Word afterwards if you need them embedded.
Is my Markdown file uploaded?
No. Parsing and file generation both happen inside your browser.
Are tables and code blocks supported?
Yes: tables become real Word tables, and fenced code blocks keep their monospace formatting. Complex nested lists may need minor adjustment after opening.
Can I convert several files at once?
The tool processes one file per conversion. For a batch, repeat the conversion or convert the files to PDF first, which supports multiple files.
Does it work for large documents?
Documents up to a few hundred kilobytes convert instantly. Very large files may take a second or two because everything runs on your device.
At a glance
| Input | Markdown |
|---|---|
| Multiple files | No |
| Where it runs | In your browser - files are never uploaded |
| Works offline | Yes — once the page has loaded |
| Price | Free, no sign-up, no watermark |
Markdown flavours are not interchangeable
Plain Markdown covers headings, emphasis, lists, links and code, and CommonMark pins down the ambiguous corners so different programs agree. GitHub Flavored Markdown (GFM) adds tables, task lists, strikethrough and autolinks - the features most people assume are standard. Other dialects add footnotes, definition lists, math and front matter, and a converter that does not recognise them will either drop the content or print the raw syntax in the output. Before converting, check which flavour your source uses and which one your destination accepts; if you are unsure, stick to CommonMark plus tables, which nearly everything supports.
Using the result in the real world
Where the converted file goes next decides which format you should produce. Pasting into a CMS or a help centre usually means HTML, because those systems store and re-render markup. Sending a contract, an invoice or anything someone will sign means PDF, because the layout is fixed and the file cannot be edited by accident. Editing later means Word, since that is what people will actually open it in. Feeding a script or a static site generator means keeping it as Markdown. Converting to the wrong target is the most common reason a document "looks wrong" afterwards - the content is intact, but the destination was never going to preserve that particular formatting.