DOCX to Markdown — structure survives, layout does not
Meeting minutes written in Word often need to live in a repository or a wiki, where Markdown is the native format. The conversion emits headings, lists and tables, but Markdown is a reflowed format: it has no pages, no columns and no font choices, so a document that was laid out on paper arrives as a single flowing column.
Page layout, fonts, margins, headers, footers and page breaks are not reproduced: the text stream is reflowed, not re-laid-out.
Processed on your device. Files aren’t sent anywhere.
What Markdown keeps from Word
Markdown expresses roles, not appearance. Anything in the Word file that maps to a role carries over.
- Heading paragraphs become # heading lines, preserving the outline.
- Body paragraphs become paragraph blocks separated by blank lines.
- Bullet and numbered lists become list items; the original numbering style is not reproduced.
- Tables become pipe-delimited tables, with the header row separated by a rule.
- Emphasis inside a paragraph can become * or _ markers.
- Footnote handling depends on the output: Markdown can include linked notes, while plain text extracts the body.
Choosing Markdown, HTML or plain text
The same .docx can go three ways. Pick by what the destination needs to read, not by which file you already have.
| Target | Carries | Best when | Cost |
|---|---|---|---|
| TXT | body text as lines | searching, diffing, pasting into a ticket | no headings, lists or tables as structure |
| HTML | sanitized reflowed markup | publishing a page or pasting into a CMS | styling and images are stripped |
| Markdown | headings, lists, tables, emphasis | repository files, wikis, notes | lossy reflow: layout, colour and images are lost |
How the reflow changes reading
A four-column action table from the minutes becomes a pipe table. In a narrow repository viewer the long text column wraps, and the table can scroll horizontally instead of fitting. Markdown is a lossy reflow: the content is present, the arrangement is not.
The same applies to anything that relied on position. Two-column instructions become one column in document order; page breaks disappear; a caption that sat beside a figure becomes a line of text with no figure attached.
Reviewing converted Markdown
Review the file before committing it, because the losses are easiest to spot in the rendered view rather than the source.
- Convert the .docx and download the .md file.
- Preview it with your repository's renderer, not as raw text.
- Check that heading levels match the outline you want in the file's table of contents.
- Read the tables at a narrow width to see how they wrap.
- Confirm whether the notes you expected appear, since footnote handling depends on the output.
- Re-add figures manually, since images are dropped rather than copied.