Word to
Markdown
Convert a Word (.docx) document to clean Markdown. Headings, bold, italic, lists, and links all carry over. Runs entirely in your browser.
Click to upload a Word (.docx) file
Migrating Word docs into a GitHub-backed docs site?
md0 CMS gives you a visual editor over your repo's markdown, so once your .docx files are converted, your team can keep editing them without touching raw syntax or Word again.
Supported elements
Preserved
- Heading styles → # through ######
- Bold, italic, links
- Bulleted and numbered lists
- Embedded images (inlined as base64)
Not preserved
- Tables (cell text only, no row/column structure)
- Comments and tracked changes
- Headers, footers, page numbers
- Text boxes and complex layout
Why convert Word to markdown
Word documents are the default format for reports, specs, and proposals, but most documentation tools, static site generators, and LLM pipelines expect plain Markdown. Converting once gives you portable text you can version in Git and edit anywhere.
Migrating a Word-based wiki to markdown
Your team's internal wiki started as a folder of Word documents, and you are moving it into a docs site or GitHub repo. Converting each file by hand would mean re-typing headings and re-applying bold and italic formatting. Upload each .docx file here instead and get Markdown that already carries the original structure.
Converting a client-delivered spec doc
A client or vendor sends over a requirements document as a .docx attachment, and your team tracks specs as Markdown files alongside the codebase. Rather than reformatting the whole document by hand, convert it here and commit the result next to your other project docs.
Prepping a document for an LLM prompt
You want to paste a Word document into an LLM as context, but raw .docx content pasted into a prompt often drags in extra whitespace and formatting artifacts. Converting to Markdown first gives the model a cleaner, more token-efficient version of the same content.
How the conversion works
Step 1: parse .docx styles
The converter reads the .docx file's internal XML and identifies each paragraph's actual style, such as Heading 1 or List Paragraph, rather than guessing from font size or visual appearance.
Step 2: map to HTML
Those styles get mapped to their semantic HTML equivalents: headings become h1 through h6, bulleted and numbered lists become ul and ol, and bold, italic, and links become their corresponding inline tags.
Step 3: convert to markdown
That intermediate HTML is then converted into Markdown, using the same engine that powers the HTML to Markdown tool, producing clean, portable text with no server round-trip.
Frequently asked questions
Does this work with Google Docs?
Only if you export the Google Doc as a .docx file first, using File → Download → Microsoft Word (.docx). The converter does not accept direct Google Docs links or .gdoc files.
What happens to images in the document?
The converter inlines images directly into the Markdown as base64 data. This keeps everything in one file with no broken links, but documents with many or large images produce a much bigger Markdown file. For production docs, re-link images to hosted URLs after conversion.
Is my file uploaded anywhere?
No. The tool converts everything in your browser and never sends your document to a server.