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.
Direct answer
Open the note in Obsidian's source mode, copy the raw Markdown, paste it here, and click Download .docx — headings, lists, tables, and standard links convert to native Word formatting. Strip the Obsidian-specific parts first: [[wikilinks]] and ![[embeds]] are not standard Markdown, so they come through as literal text, and YAML frontmatter at the top converts as plain paragraphs. Remove or rewrite those three things and the rest of the note converts cleanly.
Open Markdown to Word converterWhen to use this
- A note or draft that lives in your Obsidian vault has to go out as a Word document.
- You copied a note into Word and got literal [[bracket]] links and frontmatter text.
- You want a share-ready .docx without installing an Obsidian export plugin or pandoc.
Steps
- Open the note and switch to source mode (or copy from the editor) to get the raw Markdown.
- Delete the YAML frontmatter block (the --- ... --- section at the top) — it's metadata, not content.
- Rewrite [[wikilinks]] as plain text or standard [text](url) links, and replace ![[embedded notes]] by pasting in the embedded content.
- Paste the cleaned Markdown into the input box and check the preview.
- Click Download .docx and open the result in Word.
Example conversion
# Migration Research Notes for the platform decision. Related: see the vendor comparison. ## Findings - Current setup costs ~$2,100/month - The managed option removes two on-call rotations > Decision due before the Sep 9 cutover. ## Costs | Option | Monthly | Migration effort | | --- | --- | --- | | Stay | $2,100 | None | | Managed | $1,400 | ~3 weeks |
Word document (.docx) — opened in Word it reads: Migration Research [Heading 1] Notes for the platform decision. Related: see the vendor comparison. Findings [Heading 2] • Current setup costs ~$2,100/month • The managed option removes two on-call rotations │ Decision due before the Sep 9 cutover. ← blockquote with left border Costs [Heading 2] ┌─────────┬─────────┬──────────────────┐ │ Option │ Monthly │ Migration effort │ ← shaded header row ├─────────┼─────────┼──────────────────┤ │ Stay │ $2,100 │ None │ │ Managed │ $1,400 │ ~3 weeks │ └─────────┴─────────┴──────────────────┘
Common mistakes
- [[Wikilinks]] and ![[embeds]] are Obsidian-only syntax, not standard Markdown — they convert as literal bracketed text, so rewrite or remove them first.
- YAML frontmatter (--- tags: ... ---) is not document content; delete it before converting or it appears as stray paragraphs at the top of the Word file.
- Vault images (![[screenshot.png]]) can't be resolved by any paste-based converter — re-insert pictures in Word after exporting.
FAQ
- How do I export an Obsidian note to Word?
- Copy the note's raw Markdown, remove the frontmatter and rewrite any wikilinks, then paste it into the converter and click Download .docx. Headings, lists, tables, and standard links become native Word formatting.
- Why do my [[links]] show up as brackets in the output?
- Wikilinks are Obsidian's own syntax, not part of standard Markdown, so converters pass them through as literal text. Rewrite them as plain text or standard [text](url) links before converting.
- What happens to the frontmatter at the top of my note?
- The YAML block converts as ordinary paragraphs, which looks like stray metadata in Word. Delete it before pasting — it's for Obsidian, not for the document's readers.
- Do Obsidian callouts and blockquotes convert?
- Blockquotes convert to Word paragraphs with a left border. An Obsidian callout (> [!note]) converts as a blockquote whose first line shows the literal [!note] marker — delete that line or reword it after export.
- Is there a way to keep my note private during conversion?
- The conversion runs entirely in your browser, so vault content never gets uploaded — safe for personal or work notes.
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.
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.
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.
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.