Markdown to Word
Turn .md files into editable Word documents with real headings, lists, tables and links
Your files stay with you. Conversion happens inside the browser; no file is ever uploaded to a server.
Did this tool do the job?
Thanks, your feedback came through.
How it works
A common case: you wrote a paper or a report in Markdown (Obsidian, Typora, VS Code, GitHub or the output of an AI chat), but your professor, client or office wants a Word file. Tap or click the box to choose the .md file and press Convert to Word; "report.md" arrives in your Downloads folder as "report.docx". The conversion does not imitate the look; it builds Word's own structures. A "# Introduction" line gets the Heading 1 style, so References → Table of Contents in Word adds a table of contents in one click. Lines starting with "- " become real bullets and lines starting with "1. " use Word numbering; a list that starts at "3." counts from 3. Bold, italic and strikethrough are kept, links stay clickable, tables become bordered Word tables and their header row repeats on every page. Images are not downloaded; their alt text is written as a link to the image address instead. On this English page the paper is US Letter with 1-inch margins. The result line shows how many headings, paragraphs, list items and tables were created.
This tool is also known as markdown to docx, markdown to word, md to docx, convert md file to word, markdown to word converter.
What is Markdown (.md)?
Markdown is a plain text format where formatting is typed as marks: # at the start of a line is a heading, two asterisks around a word make it bold, a dash starts a bullet. GitHub READMEs, Obsidian and Notion notes and AI chat answers are written this way. Any text editor opens the file, but the formatting only shows in a program that interprets it; Word does not read Markdown directly, which is why a conversion is needed.
What is GFM (GitHub Flavored Markdown)?
GFM is the set of extensions GitHub added to Markdown and most editors now follow: tables drawn with vertical bars, code blocks fenced with three backticks, task lists with [ ] and [x], and strikethrough with two tildes. This tool reads Markdown with the GFM rules, so the tables and task lists in a README also reach Word as real structure rather than as symbols.
Markdown vs. Word (DOCX): what is the difference?
In Markdown you mark the formatting with symbols and the file stays plain text: it opens anywhere, works well with version control and stays small. A Word document carries the formatting visibly, along with fonts, page layout, headers, comments and tracked changes, but it needs a word processor to edit. Markdown suits writing; Word suits handing in and reviewing with others. This tool is the bridge: keep writing in Markdown and convert to Word when it is time to deliver.
What each Markdown element becomes in Word
Headings (# to ######) get Word's built-in Heading 1-6 styles; the Navigation pane lists them and a table of contents picks them up. Bullet lists use Word bullets and numbered lists use Word's automatic numbering, so numbers shift by themselves when you add an item. Nested lists keep their indent level; task list boxes [ ] and [x] become empty and checked boxes.
Tables are real Word tables: cell borders are drawn, the first row is bold as a header row and repeats when a long table breaks across pages, and the column alignment from Markdown (right, centre) is kept. Code blocks sit in a grey box in a monospaced font (Consolas) with their lines and tabs intact; inline `code` gets the same font. Block quotes (>) become indented paragraphs with a line on the left.
Links become clickable hyperlinks in Word. Only http, https and mailto addresses become links; relative paths such as "./notes.md" would be broken inside Word, so they are written as plain text.
- # Heading → Heading 1 (## → Heading 2 …)
- - item → Word bullet
- 1. item → Word numbering
- | table | → bordered Word table
- ```code``` → monospaced grey box
- [text](address) → clickable hyperlink
Honest limits: images, HTML and paper
Images are not embedded. The tool cannot reach outside your browser, so it cannot download an image from the web, and it cannot look up a local path such as "images/chart.png" on your computer. Each image is written as its alt text in square brackets, linked to the image address, and the result line says how many images were handled this way. Put the pictures back in Word with Insert → Pictures.
Raw HTML inside the Markdown (for example <div> blocks) has no Word counterpart, so its tags are removed and the text is kept as plain text.
The paper size follows the page language: US Letter with 1-inch margins on this English page. The font is Calibri 11 pt, Word's own default; every format is applied through styles, so you can change the whole look in Word's Design tab with one click.
Frequently asked questions
How do I convert a Markdown file to Word?
Choose your .md file on this page and press Convert to Word. The file is turned into a .docx inside your browser and saved to your Downloads folder. Headings, lists, tables, bold and italic text and links arrive as Word's own formats; nothing to install and no sign-up.
Can I add a table of contents in Word?
Yes. The # headings are written with Word's Heading 1-6 styles, so References → Table of Contents in Word adds one in a click, with page numbers filled in automatically.
Why are my images missing?
The tool runs inside your browser and cannot reach the internet or other files on your computer, so it cannot read the image files. Each image is replaced by its alt text, linked to the image address. Add the pictures in Word with Insert → Pictures.
Is my file uploaded to a server?
No. The Markdown file is read inside your browser and the Word document is created there too; nothing is sent over the internet.