Overview
Converts Markdown, including a GitHub README, into a Word .docx that opens in Microsoft Word, LibreOffice and Google Docs. Headings become Word heading styles, lists use real Word numbering, tables get borders and code blocks use a shaded Consolas style. The file is assembled in your browser and never uploaded.
How It Works
Paste Markdown into the editor or drop a .md, .markdown or .txt file of up to 10 MB. The preview beside it shows exactly the content that will go into the document. Choose A4 or US Letter, a body font such as Calibri, Arial or Georgia, a body size from 9 to 16 pt and an optional author name. The document title defaults to the first heading and also names the download, so a README that starts with # My Project saves as My Project.docx. Settings and your text are kept in local storage.
Step-by-Step Usage Guide
- Paste your Markdown or drop a README.md or other .md file onto the page.
- Check the preview for headings, lists, tables and code blocks.
- Pick the page size, body font, font size and, if you want, an author name.
- Edit the document title if the first heading is not the name you want.
- Click Download to save the .docx and open it in Word, LibreOffice or Google Docs.
Technical Specifications & Standards
The converter parses Markdown into a small block model and writes the OOXML parts of a .docx directly: document.xml, styles.xml, numbering.xml, the relationship files and the core and app properties, zipped with JSZip. Headings H1 to H6 map to the built-in Heading 1 to Heading 6 styles, so the Word navigation pane and an automatic table of contents work straight away. Bullet and ordered lists, including nested ones, use numbering definitions rather than typed characters, and an ordered list that starts at 3 keeps that start value. GFM tables keep their column alignment and get a header row that repeats across pages. Links become real hyperlinks with external relationships, but only http, https, mailto and tel targets are kept. Images are embedded only when they are base64 data URLs of PNG, JPEG or GIF; their pixel size is read from the file header and wide images are scaled to the page width. Images referenced by URL are replaced by their alt text because the tool never fetches anything. Task list items show as ballot box characters.
Targeted Use Cases
- Handing a GitHub README to a colleague who edits everything in Microsoft Word.
- Turning Markdown meeting notes into a .docx for a shared drive or an email attachment.
- Drafting a report in a Markdown editor and delivering it in the Word format a client asked for.
- Converting technical documentation with code samples and tables for review with tracked changes.
- Producing an editable Word version of a changelog or runbook without installing Pandoc.
Notes & Gotchas
- Use real Markdown headings instead of bold lines so Word builds a usable navigation pane and table of contents.
- Embed screenshots as base64 data URLs when they must travel inside the document.
- Keep table cells short, because columns share the page width equally in the generated table.
- Set the author field once; it is saved and written into the document properties of every export.
Frequently Asked Questions
How do I convert a README.md to a Word document?
Drop the README.md file onto the page or paste its text, then click Download. Headings, lists, tables, code fences and links from the README are written as native Word formatting in a .docx named after the first heading.
Will lists and headings be editable in Word?
Yes. Headings use the Heading 1 to Heading 6 styles and lists use Word numbering, so you can restyle them, renumber them or generate a table of contents in Word like any hand-made document.
Why did an image turn into text in the .docx?
Only images written as base64 data URLs of PNG, JPEG or GIF can be embedded. An image linked by an http address is replaced by its alt text, because the converter does not download anything from the internet.
Is my Markdown uploaded to a server?
No. Parsing and the ZIP packaging both run in your browser tab with JavaScript. You can disconnect from the network after the page loads and the conversion still works.
Does it support raw HTML inside Markdown?
Raw HTML tags are kept as literal text rather than interpreted. If your source is mostly HTML, use the HTML to Word converter instead, which understands tags such as p, ul, table and pre.
Related tools
- Markdown to PDF Converter - Convert Markdown or a GitHub README to PDF with code highlighting, Mermaid diagrams, math, page size, margins and a table of contents.
- HTML to Word (DOCX) Converter - Turn HTML into a Word .docx with headings, lists, tables, links and code kept as real Word styles. Scripts, styles and event handlers are removed first, and nothing leaves your browser.
- Markdown to EPUB Converter - Turn Markdown into a valid EPUB 3 ebook in your browser. Each # heading becomes a chapter, with a title, author, language and optional PNG or JPEG cover, a navigation document and an NCX for older readers.
- Word to HTML / Markdown - Convert a Word .docx file to clean HTML and GitHub Markdown with headings, lists, tables and links kept, and images embedded as base64 or exported as separate files in a ZIP.
- PDF to Word (DOCX) - Convert a PDF into an editable Word .docx file in your browser, with headings detected by font size, one section per page, and an exact-layout option that places each page as an image.
- DOCX Word Counter & Document Stats - Count words, characters, paragraphs and pages in Word .docx files, see reading time, a headings outline, tables, images and comments, and batch several documents into one CSV.