DOCX to Markdown Converter
Move Word documents into a docs-as-code workflow. The converter turns headings, bold and italic text, lists, tables, links and footnotes into GitHub-flavoured Markdown, and saves the images as separate files in an images folder, packed with the .md file into one ZIP. Choose the heading and bullet style that matches your project.
- Files stay on your device
- No sign-up
- Free to use
How to use DOCX to Markdown
- Drop a .docx file onto the page.
- Choose how images are stored and your preferred Markdown style.
- Click “Convert to Markdown”.
- Copy the Markdown or download it – as a ZIP when images are included.
DOCX to Markdown features
GitHub-flavoured
Tables, fenced code and standard links.
Image files
Pictures saved to images/ and linked relatively.
Table headers
The first row becomes the header row Markdown needs.
Style options
# or underlined headings, - or * bullets.
Conversion notes
Tells you what could not be expressed in Markdown.
Private
Converted in your browser.
When to use DOCX to Markdown
- Moving documentation from Word into Git repositories.
- Publishing with MkDocs, Docusaurus, Hugo or Jekyll.
- Writing in Word and publishing on GitHub or GitLab.
- Keeping notes in Obsidian or other Markdown editors.
DOCX to Markdown FAQ
Which Markdown flavour is produced?
GitHub-flavoured Markdown (GFM), the most widely supported variant. It adds tables and strikethrough to standard Markdown.
What happens to tables?
Simple tables become Markdown pipe tables, using the first row as the header. Tables with merged or nested cells cannot be expressed in Markdown and are kept as HTML, which most renderers display.
Where do the images go?
With “separate files” the ZIP contains the .md file and an images folder; the Markdown links to images/image-1.png and so on. Unzip both into your project.
Are lettered list numbers kept?
Markdown only knows numbered and bulleted lists, so a) b) c) and i. ii. lists become 1. 2. 3. lists. The order is kept.
What about images in headers and footers?
Headers and footers are page decoration and are not part of the Markdown text, so their images are not included.
Is my document uploaded?
No. The conversion runs in your browser.
Word documents in a Markdown workflow
Markdown has become the standard format for technical documentation, README files and many static websites. It is plain text, so it can be versioned in Git, reviewed line by line and edited in any editor. Many teams still receive or draft content in Word, and converting it by hand is tedious and error-prone.
The converter works in two steps. First, mammoth.js reads the .docx file and produces clean, semantic HTML from the document’s styles: headings, lists, tables, links and emphasis. Then Turndown translates that HTML into Markdown with the GitHub-flavoured extensions for tables. Along the way the tool adapts Word-specific structures: table header rows are created, paragraphs inside table cells are joined, and list markers are normalised to a single space.
Images need a decision. Data URIs keep everything in one file but make the Markdown hard to read and edit. Separate files are the usual choice for repositories and documentation sites: the ZIP contains the Markdown and an images folder, and the links are relative, so they work wherever you put both.
Some Word features have no Markdown equivalent: colours, fonts, alignment, merged table cells, text boxes and comments. The text of these elements is kept where possible, and the notes below the output tell you when something needed a fallback.
For best results, use Word’s built-in heading styles in the source document. They become the # headings that documentation tools use for navigation and tables of contents.