Almost every manuscript that ends up in Markdown started somewhere else, and that somewhere is usually Word. The conversion itself is easy. What is not obvious is that a Word file is not really a document — it is a document plus a long history of every formatting decision anyone ever made in it, including the ones they made by accident.
The one command
Pandoc is the tool. It reads the real .docx XML rather than guessing at a copy-paste, which is why it is the only route worth taking:
# Basic conversion
pandoc manuscript.docx -o manuscript.md
# Better: extract images, and use ATX headings (#) rather than underlines
pandoc manuscript.docx -o manuscript.md \
--extract-media=./images \
--markdown-headings=atx \
--wrap=noneThose three flags are worth knowing. --extract-media pulls the embedded images out into a folder and rewrites the links — without it, images either vanish or arrive as unreadable base64. --markdown-headings=atx gives you ## Chapter instead of an underline of equals signs, which is what every other tool expects. --wrap=none puts each paragraph on one long line rather than hard-wrapping at 80 characters, which makes later editing far less painful.
Why the headings come out wrong
This is the big one, and it is not Pandoc's fault. In Word there are two ways to make text look like a chapter title. You can apply the Heading 1 style, or you can select the text and make it 18pt and bold. On screen these look identical. In the file they are completely different things: the first is structure, the second is decoration.
Pandoc can only convert structure. A chapter title that was manually bolded arrives in your Markdown as **Chapter One** — a bold paragraph, not a heading. Which means it will not appear in a table of contents, will not start a new page, and will not be styled as a chapter by anything downstream. Headings are the book's structure, and a book with no real headings has no structure to convert.
The fix is in Word, before you convert. Open the navigation pane (View → Navigation Pane). Any chapter that does not appear in it was never a heading. Select it, apply Heading 1, and repeat. On a 30-chapter manuscript this is twenty minutes and it makes the conversion work.
What else needs cleaning
| What comes across | What to do |
|---|---|
| Tracked changes and comments | Accept or reject all, delete all comments, before converting |
| Smart quotes and dashes | Keep them — they are correct. Just be aware they are not ASCII |
| Manual line breaks mid-paragraph | Find and remove. They become real breaks and wreck reflow |
| Double spaces after full stops | Find and replace with one. A typewriter convention |
| Tabs and manual indents | Delete. First-line indent is a type setting, not a character |
| Empty paragraphs for spacing | Delete. Spacing is a margin, not a row of blank lines |
| Word's automatic list numbers | Check they arrived as 1. text rather than vanishing |
| Text boxes and floating images | These do not survive. Re-insert them as normal images |
| Footnotes | Pandoc converts them, but confirm your destination supports them |
The empty-paragraph row is the one people resist, because those blank lines are load-bearing in Word. They are not load-bearing in a typeset book: the space between paragraphs is a property of the paragraph style, applied consistently everywhere, which is exactly why a typeset page looks even and a word-processed one does not.
A cleanup pass you can run
After conversion, these regular expressions catch most of what is left. Run them in any editor that supports find-and-replace with regex:
Find Replace What it fixes
\ {2,} (space) Multiple spaces
\n{3,} \n\n Runs of blank lines
^\t+ (nothing) Leading tabs
\\$ (nothing) Stray hard line breaks
\*\*(.{1,60})\*\*$ ## $1 Bold-only lines that were headingsThe last one is a helper, not a rule — review each match rather than replacing blindly, because a paragraph that legitimately ends in bold text will be caught too.
Going the other way, and why you might not need to
Pandoc converts back — pandoc manuscript.md -o manuscript.docx — which is worth knowing if an editor or a competition demands a Word file. Supply a reference document to control the styling:
pandoc manuscript.md -o manuscript.docx \
--reference-doc=house-style.docxBut if the destination is a finished book rather than an editor's inbox, the round trip is unnecessary. The point of getting the manuscript into Markdown is that it is now plain text you own, readable in thirty years, versionable, and ready to be designed once and exported as many times as you like — a PDF and an EPUB from the same file, without either being converted from the other.
That is the honest argument for spending the hour. The conversion is a one-off cost; what you get is a manuscript that no longer depends on one application being able to open it. Google Docs versus Markdown makes the same case from the other direction, if you are still deciding.