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
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.
COMMON REASONS TO CONVERT
- Migrating a Word-based knowledge base into a docs site
- Turning a client-delivered .docx spec into a README
- Feeding a Word document into an LLM as clean context
- Archiving a document as plain, diffable text
HOW THE CONVERSION WORKS
The .docx file is parsed and converted to structured HTML first (preserving headings, formatting, and lists from the document's actual styles, not guessed from appearance), then that HTML is converted to Markdown using the same converter that powers the HTML to Markdown tool.
FREQUENTLY ASKED QUESTIONS
DOES THIS WORK WITH GOOGLE DOCS?
Only if you export the Google Doc as a .docx file first (File → Download → Microsoft Word .docx). Direct Google Docs links or .gdoc files aren't supported.
WHAT HAPPENS TO IMAGES IN THE DOCUMENT?
Images are inlined directly into the Markdown as base64 data. This keeps everything in one file with no broken links, but it also means documents with many or large images will produce a much bigger Markdown file. For production docs, consider re-linking images to hosted URLs after conversion.
IS MY FILE UPLOADED ANYWHERE?
No. The entire conversion happens in your browser. Your document is never sent to a server.