Markdown Headings to Word Heading Styles (and a Table of Contents)
Convert # through ###### Markdown headings into real Word Heading 1–6 styles, then use Word's References tab to generate an automatic, clickable table of contents from them.
Direct answer
Each Markdown heading level maps to the matching native Word style: # becomes Heading 1, ## becomes Heading 2, down through ###### as Heading 6. Because they are real Word styles — not just big bold text — Word's outline view, navigation pane, and automatic table of contents all work: after you download the .docx, insert a TOC in Word via References > Table of Contents and it builds itself from your Markdown structure.
Open Markdown to Word converterWhen to use this
- A long document needs a clickable table of contents in Word.
- You want the Word navigation pane and outline view to reflect your Markdown structure.
- A corporate template restyles Heading 1–3, and you need your headings to pick those styles up.
Steps
- Structure the Markdown with # for the title, ## for sections, and ### for subsections.
- Paste it into the input box and click Download .docx.
- Open the file in Word and confirm the navigation pane (View > Navigation Pane) lists your headings.
- Place the cursor where the TOC belongs, then choose References > Table of Contents > Automatic Table.
- After any edits, right-click the TOC and choose Update Field to refresh page numbers and entries.
Example conversion
# Incident Review: Payments Outage ## Summary 42 minutes of failed card charges on Aug 9. ## Timeline ### Detection Alert fired at 14:02 UTC. ### Mitigation Traffic shifted to the standby region at 14:19 UTC. ## Action Items Owners assigned in the tracker.
Word document (.docx) — opened in Word:
Incident Review: Payments Outage [Heading 1]
Summary [Heading 2]
Timeline [Heading 2]
Detection [Heading 3]
Mitigation [Heading 3]
Action Items [Heading 2]
The navigation pane shows this exact outline, and
References > Table of Contents generates:
Summary ............................ 1
Timeline ........................... 1
Detection ...................... 1
Mitigation ..................... 2
Action Items ....................... 2Common mistakes
- The table of contents itself is not generated during conversion — you insert it in Word afterward with References > Table of Contents; it takes one click because the heading styles are already in place.
- Bold text on its own line (**Section**) is not a heading; it converts as bold body text and will not appear in the TOC or navigation pane. Use # syntax for anything structural.
- Skipping levels (jumping from # to ###) converts fine but produces an uneven TOC hierarchy; keep levels sequential for a clean outline.
FAQ
- Do Markdown headings become real Word heading styles?
- Yes. # through ###### map to Word's native Heading 1 through Heading 6 styles. They respond to style changes, appear in the navigation pane, and feed Word's automatic table of contents.
- Can the converter insert the table of contents for me?
- No — the TOC is added in Word after export. Because the headings are real Word styles, References > Table of Contents > Automatic Table builds it in one click, and Update Field refreshes it after edits.
- Will my corporate template restyle the headings?
- Yes. Applying a template or changing the Heading 1–6 style definitions in Word restyles every converted heading at once, exactly as it would for a document written in Word.
- Why doesn't my bold 'heading' show in the navigation pane?
- Bold text is character formatting, not a heading style. Only # syntax headings convert to Heading styles, so rewrite structural lines as Markdown headings before converting.
- How deep can the heading hierarchy go?
- Six levels — Markdown's # through ###### map to Word's Heading 1 through Heading 6. Word's automatic TOC shows levels 1–3 by default; add deeper levels via Custom Table of Contents.
Related Markdown guides
Related Markdown to Word guides
How to Convert Markdown to a Word Document
Turn Markdown into an editable Microsoft Word (.docx) file — headings, bold, lists, and tables become native Word styles you can restyle in Word, Google Docs, or Pages.
Turn a README into a Word Document
Convert a README.md into an editable Word (.docx) document you can send to managers, clients, or auditors who expect Word instead of a GitHub page.
Convert Markdown to Word With Real Tables
Convert Markdown that contains GFM pipe tables into a Word document where each table is a native, editable Word table with a shaded header row.
Convert Markdown to DOCX Without Pandoc
Convert Markdown to a Word .docx in the browser with nothing to install — a no-setup alternative to pandoc for one-off conversions (with an honest note on when pandoc still wins).
Turn ChatGPT or Claude Output Into a Word Document
Convert Markdown answers from ChatGPT, Claude, or Gemini into a clean, editable Word (.docx) document — headings, lists, and tables intact, no stray hashes or asterisks.
Convert Markdown Meeting Notes to Word
Turn meeting notes, status updates, or standup summaries written in Markdown into a clean Word (.docx) document you can circulate to non-technical stakeholders.
Paste Markdown Into Word vs Google Docs: What Actually Works
Word does not interpret pasted Markdown at all, and Google Docs only partially does. Convert the Markdown to a .docx first — both apps open it with headings, lists, and tables already formatted.
Convert a Markdown Resume to a Word Document
Turn a resume written in Markdown into an editable Word (.docx) file for recruiters and application portals that require Word format — headings, bullet points, and skills tables intact.
Export Obsidian Notes to a Word Document
Turn an Obsidian note into an editable Word (.docx) file — with the fixes for the Obsidian-specific syntax (wikilinks, embeds, frontmatter) that standard Markdown converters don't understand.
Turn an AI Report Draft Into a Client-Ready Word Document
A workflow for assembling ChatGPT- or Claude-drafted report sections into one polished, editable .docx you can put in front of a client — conversion, cleanup, and the review pass before it ships.
Desk gear for long writing sessions
A few things that help if you write docs, tickets, and specs on a laptop all day.
Anker 5-in-1 USB-C Hub
One cable turns a laptop into a desk setup. Drives a 4K display, charges at up to 85W, and adds three data ports.
- 4K HDMI output
- 85W max power delivery
- 1x USB-C + 2x USB-A, 5Gbps each
- MacBook Pro, MacBook Air, Dell
Dell 27" S2725QC 4K
The monitor I write and review documents on. 163 PPI keeps small text sharp, and USB-C carries video and power on one cable.
- 3840x2160 IPS, 163 PPI
- 120Hz, 4ms, FreeSync Premium
- 99% sRGB
- USB-C, HDMI, DisplayPort
Apple MacBook Neo 13" (A18 Pro)
The cheapest way into an Apple-silicon machine that runs local models. Fanless, and the Liquid Retina panel holds small text at a full day of reading.
- A18 Pro chip, built for Apple Intelligence
- 8GB unified memory, 256GB SSD
- 13-inch Liquid Retina display
- 1080p FaceTime HD camera
Amazon affiliate links. We earn a commission on qualifying purchases at no extra cost to you.