Word to Markdown
Extract Markdown (.md) from Word documents. Headings, bold and italic text, lists and tables become proper Markdown syntax, ready for GitHub, Obsidian or
Drop your Word file here
or click to browse files
Extract Markdown from a Word document: headings map to # levels, bold and italic text to ** and *, lists to bullets and numbering, and tables to Markdown pipe tables. The result is ready to paste into GitHub, Obsidian, Notion or a static site.
It is the standard move when documentation lives in .docx files but has to be versioned in a repository, or when a colleague sends a draft that needs to become a web page. Conversion happens locally, so unpublished documents are not uploaded.
How to convert Word to Markdown
Choose a .docx file
Convert it
Copy the Markdown or download the .md file
FAQ
What happens to images?
Images embedded in the document are extracted and written as Markdown image references. Very large documents with many pictures can take a moment to process.
Are tables supported?
Standard tables become Markdown pipe tables. Merged cells do not exist in Markdown, so those tables are flattened and should be reviewed afterwards.
Which Word formats work?
.docx is supported directly. Old .doc files should be re-saved as .docx first, and .rtf or .odt are usually better converted from their native application.
Is the heading structure preserved?
Yes, Word heading styles become the corresponding Markdown levels. If the author used manual bold text instead of heading styles, that is what you get instead.
Can I convert several documents at once?
One document per conversion. For a batch, repeat the step - the output is stable enough to script if you need volume.
Is my document uploaded?
No, the conversion happens in your browser.
At a glance
| Input | Word |
|---|---|
| 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 |
What survives a conversion
Structure usually survives, formatting often does not. Headings, paragraphs, lists, links, bold and italics convert cleanly between Markdown, HTML, Word and PDF. What tends to break is anything relying on styling rather than structure: CSS classes and custom colours disappear, complex nested tables collapse into unreadable ones, embedded HTML may be stripped for safety, and images either stay as links or get downloaded depending on the tool. Footnotes and math usually need explicit support. If the result matters, convert a sample first - a document with a table, a code block, a link and an image will reveal almost every problem you are going to hit.
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.