Word to Markdown
Turn a document into Markdown for your docs or repo.
About Word to Markdown
Convert .docx to GitHub-flavoured Markdown, mapping headings, emphasis, links, lists, tables and code blocks. Perfect for moving legacy Word documentation into a static site or wiki.
Markdown is where documentation, notes and technical writing live, and a great deal of source material arrives as .docx from people who do not use it.
Convert to GitHub-flavoured Markdown with the structure intact.
- Processed on your deviceEverything you open or type here is handled by this page and never uploaded anywhere.
- No queue, no limitsNothing waits on a server, so the only limit is your own hardware.
- No account neededNo sign-up and no email address required.
How Word to Markdown works in your browser
Mammoth reconstructs the document’s semantic structure first, and that structure is written out as Markdown — headings become hash prefixes, emphasis becomes asterisks, lists become dashes or numbers, tables become pipe tables.
Converting to Markdown is a genuine simplification, and it is worth expecting that rather than being surprised by it. Markdown has one way to express a heading and Word has many; formatting with no Markdown equivalent — text boxes, coloured text, precise spacing, multi-level numbering schemes — is discarded rather than approximated with markup that only looks similar.
What you get back is therefore cleaner than the input and smaller than it. For text destined for a repository, a wiki or a static site, that simplification is the point rather than a cost.
When to use it
Moving documentation out of Word and into a repository where it can be reviewed in pull requests. Turning a Word-authored draft into a blog post for a static site generator. Getting a diff-able version of a document so changes between drafts can be read as text. Converting meeting notes or specifications into a wiki that expects Markdown.
Frequently asked questions
Which Markdown features are supported?
GitHub-flavoured Markdown: headings, bold and italic, links, ordered and unordered lists, tables and code blocks are all mapped from their Word equivalents.
What happens to Word features Markdown has no equivalent for?
Things like text boxes, columns and precise positioning are flattened to their text content. Markdown has no way to express them, so the words survive and the layout does not.
Is this good for moving documentation to a wiki?
That is exactly what it is for. Legacy Word documentation converts into files a static site generator or wiki can consume directly.