How to convert Markdown to Word without losing structure

Keep the headings, cells and notes useful. Let the word processor handle the pages.

Convert the structure before you adjust the layout

Use a DOCX converter, Google Docs import or Pandoc to turn Markdown markers into document structures. Then check the result in your word processor.

A heading should be a Word heading style. A table should contain cells. A bold-looking screenshot inside DOCX will not give you either.

Use a browser converter for a document you can review

Paste the Markdown source or open the MD file, choose the output style and inspect a real DOCX export. A preview alone cannot establish compatibility.

1. Start with the source. A chat app’s Copy button may preserve Markdown better than copying selected rendered text.
2. Check heading levels, nested lists and table columns in the preview.
3. Read export warnings. Supply local images if the converter does not fetch linked pictures.
4. Save DOCX, open it in your word processor and check the final layout.

The floi converter offers three document styles, local picture matching and review notes. It keeps file conversion in your browser. Other tools may suit different extensions.

MarkdownWord’s web app gives explicit fallback warnings. CloudConvert offers a server conversion workflow. MarkLiveEdit renders Mermaid previews, which floi keeps as code. These observations come from desktop tests on 3 November 2026, rather than a comparative output-quality benchmark.

Import Markdown into Google Docs

Google Docs supports Markdown import and Paste from Markdown. You do not need to pretend that pasted hash marks are a finished document.

Google’s Markdown instructions describe the available import and clipboard commands. After importing, use File → Download → Microsoft Word (.docx).

If Paste from Markdown is missing, check Tools → Preferences for Markdown support. Review tables and equations in the exported file. This is a cloud workflow, so use it for material you are comfortable storing there.

Use Pandoc from the command line

Pandoc is the stronger choice when you need repeatable conversions or your own Word style reference. It runs locally once installed.

Convert a single file with this command:

pandoc input.md -o output.docx

For a contents list and a local image directory, make those choices explicit:

pandoc input.md --toc --resource-path=.:images -o output.docx

The resource-path separator is a semicolon on Windows. The Pandoc manual explains image lookup, Markdown extensions, mathematics and reference documents.

Use your organisation’s Word styles

A reference DOCX supplies styles and document properties. It does not copy that document’s written content into the result.

pandoc input.md --reference-doc=house-style.docx -o output.docx

Prepare the reference document’s heading, paragraph and table styles in Word. This offers more control than floi’s three built-in looks.

Call Pandoc from Python

Use subprocess with a list of arguments. The Pandoc executable must be installed separately.

import subprocess

subprocess.run(
    ["pandoc", "input.md", "-o", "output.docx"],
    check=True,
)

Keep file paths separate from shell syntax. Review conversion warnings and stop the script when a command fails.

A working fixture for checking the result

Use a small document that exercises your actual needs before converting a long report. This fixture checks structure, rather than promising identical typography.

# Project North

## Delivery

1. First milestone
   - Nested action
2. Second milestone

| Item | Cost |
| :--- | ---: |
| Design | £125.50 |
| Build | £800.00 |

A note needs context.[^one]

[^one]: This is the supporting footnote.

$$
x = \frac{-b + \sqrt{b^2-4ac}}{2a}
$$

The reproducible floi checks use original synthetic text with emphasis, code, task marks, local images and unsupported syntax. DOCX structure was checked in XML and representative pages were visually reviewed in LibreOffice 25.2.

The browser run used Chrome 156 on an Apple M1 Max Mac, on 3 November 2026. The A4 examples cover all three document styles. A separate Letter export includes contents, page numbers and a locally attached picture.

The checks are dated November 2026. They do not establish identical output across all Word versions, Google Docs, Pages or mobile browsers. Font substitution and page layout still need a check in your destination application.

Fix the common problems before sending

Tables show their pipes

Confirm that you imported Markdown instead of ordinary text. A pipe table needs a header separator row such as | --- | ---: |.

Keep one cell per column in every row. Escape a literal pipe as \|. Very wide tables may need smaller text or a different page layout in Word.

Footnotes or equations remain as source

The converter may not support that extension. Check its output format and warnings rather than relying on the browser preview.

The floi converter supports common TeX fractions, roots, powers, indices and symbols. It keeps unsupported expressions whole. It does not implement matrix environments, automatic equation numbers or a complete LaTeX document.

Pictures are missing

A relative picture path only has meaning when the converter can read the corresponding local file. A Markdown file does not contain those image bytes.

In floi, attach the picture with its unique file name. In Pandoc, set the resource path. A remote URL may fail because of access controls, network restrictions or an expired link.

The page breaks moved

Word lays out the document using its available fonts and paper settings. Markdown has no fixed page geometry to preserve.

Check margins, headings stranded near page bottoms and tables split across pages. Add a deliberate page break only where the document needs one.

Check the file that the next person will open

Open the saved DOCX and test its structures before sharing. A successful save means a file exists, not that every feature matches your intent.

• Use the Navigation Pane to check headings and reading order.
• Edit a table cell, continue a numbered list and inspect each footnote.
• Check equation signs, image descriptions and clickable links.
• Review the first and last page, then any page with a wide table or picture.

For a fixed final copy, export PDF from your word processor after that review. Keep DOCX for the person who needs to keep editing.