Skip to content
TabShedKitsMy desk

Send a Markdown Draft to a Colleague Who Uses Word

Updated 5 min readBy

Convert Markdown to a .docx with real heading styles, lists and tables so a reviewer can comment and track changes in Word. What to check before you send it.

Markdown to WordMarkdown to an editable DOCX file
Open Markdown to Word
On this page
  1. What "built properly" means
  2. Step by step
  3. Choosing the style for a reviewer
  4. The table of contents prompt
  5. A pre-send checklist
  6. Receiving the edits back
  7. Style choices you can make after conversion
  8. Several files
  9. Things that do not convert
  10. When a PDF is better
  11. Privacy
  12. FAQ

Your draft lives in Markdown. Your editor, lawyer or manager lives in Word and wants to track changes and leave comments. Sending the .md file works only for people who know what they are looking at, and a PDF cannot be edited. The practical bridge is a Word document that was built properly: real headings, real lists, real tables. The Markdown to Word tool produces that in your browser, without uploading your text.

What "built properly" means

A .docx made by pasting text into Word and bolding the headings looks right but behaves wrongly. A reviewer cannot navigate by heading, a table of contents will not build, and styles cannot be changed in one go. This tool maps the Markdown structure to Word's own structure:

  • Headings use Word's heading styles, so the Navigation Pane and a table of contents work.
  • Bullet and numbered lists are real Word lists.
  • Tables are real Word tables.
  • Fenced code blocks with a language keep their syntax colours, in a monospaced font on a light background.
  • Links and pictures are carried across.

The result opens in Word, LibreOffice, Pages and Google Docs.

Step by step

  1. Type or paste your Markdown, or drop one or more .md files.
  2. Pick page size, margins, a Clean, Serif or GitHub style, text size, page numbers and whether to add a table of contents.
  3. Download the .docx.
  4. Open it in Word, check the first page and the headings, then send it, or use Send to phone to move the file to your phone first.

Choosing the style for a reviewer

Reviewers read on screen and write in the margins, so choose the style that stays out of their way. Serif reads like a manuscript and suits long text, Clean is neutral for business documents and GitHub keeps the familiar technical look. Medium text size and standard margins leave room for comments. Avoid very small text: comments balloons make it harder to read.

The table of contents prompt

If you add a table of contents, Word asks to update fields when the file is opened; clicking Yes makes Word fill in page numbers. If you do not need a contents list for a short document, leave it out and the file opens without any prompt. Tell your colleague about the prompt beforehand, since an unexpected dialog in a file from someone else looks suspicious.

A pre-send checklist

  1. Open the Navigation Pane. Every heading from your Markdown should appear. A missing heading means the pound signs lacked a space after them, such as #Title instead of # Title.
  2. Check the tables. Tables with a header separator row convert as tables. Cells with very long text may need a wider column in Word.
  3. Check the links. Relative links to other files in your repository will not work in a Word document; replace them with full addresses.
  4. Look at the code blocks. Colours should be preserved; a block without a language name is shown in plain monospaced text.
  5. Scroll to the end. Make sure the last section is complete and nothing was cut off, especially after a long table or code block.

Receiving the edits back

Here is the honest limit of this approach: conversion goes one way. Once your colleague has edited the Word file, you cannot turn it back into your original Markdown without losing formatting details. Two workable patterns exist. The first is to treat the Word file as the master after sending it, and to stop editing the Markdown. The second is to ask for comments only, not direct edits, and apply the changes to your Markdown yourself, using the comments as a to-do list. If your colleague must rewrite whole paragraphs, the first pattern is safer. If they only mark issues, the second keeps your source of truth intact.

When you need to compare their edited version with what you sent, convert both to PDF and use Compare PDF, or paste the text of both into the Text Diff Checker.

Style choices you can make after conversion

Because the headings are real Word styles, you can change the look of the whole document in a few clicks after the conversion: redefine "Heading 1" once and every top-level heading changes. This is the main practical advantage over a pasted text with manual bolding. If your organisation has a house template, apply it after conversion and the headings, lists and tables should adopt the template's styles rather than keeping their own formatting. Do that before sending the file for review, not after, because a restyle can reflow pages and move comments.

Keep a note of which version the reviewer got. A simple habit is to put the date in the file name when you send it and to ask for the reply with the same name plus the reviewer's initials. When several people review the same draft, that is what stops you from merging edits into the wrong copy.

Several files

Drop several .md files and download a ZIP with one .docx for each. This is handy for a set of chapters; if the reviewer wants a single file, merge the chapters into one Markdown file first.

Things that do not convert

  • Mermaid diagrams and formulas, which are not rendered and appear as code.
  • Tracked changes or comments from any previous Word file, because the source is Markdown and has none.
  • Anything the standard GitHub-flavoured syntax does not define. If you rely on an extension from your own editor, check how it appears in the preview before you send the file.

When a PDF is better

If you only need the reader to read, not edit, a PDF is more reliable because the layout is fixed; use Markdown to PDF. If your source is HTML, use HTML to Word.

Privacy

The DOCX file is made in your browser and your text never leaves your device. That is the main reason to use it for drafts that are not public yet, such as a proposal or a policy draft.

FAQ

Will Word see real headings?

Yes. They use Word heading styles, so navigation and contents work.

Can I convert several files?

Yes, you get a ZIP with one .docx each.

Do code blocks keep colours?

Yes, when the block has a language name.

Is there a watermark or limit?

No watermark, no sign-up.