How to Convert Obsidian Notes to Word (DOCX)
Export Obsidian Markdown notes to Microsoft Word .docx. Covers export plugins, Pandoc, wikilinks, embeds, and keeping your formatting intact.
Obsidian is a superb place to write — fast, local, link-heavy, and built around plain Markdown files — but it is not always where your writing needs to land. Editors, clients, teachers, and collaborators often expect a Microsoft Word .docx, complete with headings, tables, images, and proper page formatting. The good news is that Obsidian's vault is just a folder of .md files, and getting from there to a clean Word document is a solved problem. This guide covers the practical Obsidian-to-Word paths: Pandoc, community plugins, online conversion, and how to handle the two features that trip up every export — wikilinks and embeds.
Why Convert Obsidian Notes to Word
Obsidian stores everything as plain Markdown on your own disk, which is excellent for longevity but poor for sharing with someone who does not live in a Markdown editor. You will want a .docx when:
- A reviewer needs to leave tracked changes and comments.
- A publisher or institution requires Word as the submission format.
- A collaborator is not technical and expects a "normal" document.
- You need pagination, headers, footers, or print-ready styling.
| Format | Best for | Limitation |
|---|---|---|
Obsidian .md | Writing, linking, search | No pagination, no native Word review tools |
Word .docx | Editing, review, submission | Loses Obsidian wikilinks and live embeds unless converted carefully |
| Final delivery, print | Hard to edit further |
The conversion goal is simple in principle — turn Markdown into Word — but Obsidian adds two complications that a generic Markdown file does not have: [[wikilinks]] between notes, and inline ![[embeds]] of other notes or images. A good Obsidian-to-Word workflow handles both.
Convert Obsidian to Word with Pandoc
Pandoc is the most powerful converter in the Markdown ecosystem, and because Obsidian's notes are plain .md files, you can point Pandoc directly at them without leaving the command line.
# Convert a single Obsidian note to Word
pandoc "Project Brief.md" -o "Project Brief.docx"
# Convert with a reference document for custom styling
pandoc "Project Brief.md" \
--reference-doc=custom-template.docx \
-o "Project Brief.docx"
A reference document (--reference-doc) is how you lock in fonts, heading sizes, margins, and line spacing so every export matches your house style. Create the template once in Word, save it as .docx, and reuse it for every note.
If you want to convert a whole folder of notes into a single Word document, list the files in dependency order and pass them all to Pandoc:
pandoc 01-intro.md 02-method.md 03-results.md \
--reference-doc=template.docx \
-o "Full Report.docx"
A local conversion workflow can read the note and attachment files you provide without uploading the source to a conversion service. Remote image URLs can still make network requests, so review those references when the export must remain offline.
The main gotcha with Pandoc and Obsidian is wikilinks. By default Pandoc does not understand [[Note Title]], so those links render as literal text. Two fixes:
- For a small export, rewrite wikilinks manually. For batch exports, use a converter or filter that explicitly resolves your vault’s link syntax and test aliases, headings, and missing targets.
- In Obsidian, flip the setting Settings → Files & Links → New link format to "Relative path to file" and turn off wikilinks for notes you plan to export.
Convert Obsidian Markdown to DOCX Online
Not everyone wants to install Pandoc or fuss with the command line. A browser-based converter is the fastest path when you need a .docx from an Obsidian note right now.
- In Obsidian, open the note you want to export.
- Select all the text and copy it (or right-click the file in the file pane and copy its contents).
- Paste it into the Markdown to Word converter.
- Download the resulting
.docx.
The browser converter does not upload the Markdown to a conversion server, but remote image references still contact their hosts. It cannot read the rest of your vault from a pasted note or a single .md upload. For confidential notes with local attachments, a local workflow that can access the vault is often a better fit.
| Workflow | Best for | Setup effort |
|---|---|---|
| Copy-paste into Markdown to Word | One-off exports, quick sharing | None |
| Markdown to PDF | Final delivery, print-ready | None |
| Pandoc with a reference doc | Repeat exports with consistent styling | Medium |
| Community plugin inside Obsidian | Batch export without leaving the vault | Low-medium |
If you need a print-ready file rather than an editable one, route the same note through the Markdown to PDF tool. And if you have a .md file from another source and just want to read it comfortably first, the online Markdown viewer will open it without installing anything.
Handle Obsidian Wikilinks When Exporting to Word
Wikilinks — [[Note Title]] — are the signature feature of an Obsidian vault, and they are the feature most likely to break during export because standard Markdown (and therefore Word) has no concept of them. Three strategies handle them cleanly.
Rewrite wikilinks to meaningful destinations. For example, change [[Setup]] into a normal Markdown link to the published setup document. A relative [Setup](Setup.md) may work inside a local folder, but it will not give a Word recipient access to your vault. For links with no shareable destination, keep readable text instead. Inspect aliases and heading references rather than applying a blind search-and-replace.
Resolve wikilinks to readable text. If the links are not meaningful outside the vault, strip the brackets and keep the title as plain text. The Word reader sees a normal sentence instead of broken syntax.
Convert blocks of links to a "References" section. Academic and long-form writers often collect source notes at the bottom of a document; exporting those as a bulleted reference list is cleaner than a tangle of dead links.
| Wikilink form | What to do in Word export |
|---|---|
[[Note]] | Rewrite to plain link or text |
[[Note|Alias]] | Keep the alias as the visible text |
[[Note#Heading]] | Link to a shareable web section or create a Word bookmark after export |
[[Note^block]] | Resolve to the block content or remove |
Keep Obsidian Embeds and Images in Word Documents
Obsidian's ![[embed]] syntax lets you pull one note into another, or drop an image into a page by referencing its filename. These also need attention before export, because Word has no equivalent of a live embed — only inserted content.
For images, the cleanest fix is to convert the embed to standard Markdown image syntax with a real path:
Obsidian form: ![[cover.png]]
Markdown form: 
For note embeds (![[Other Note]]), copy the content of the embedded note inline where the embed appears, or use a Pandoc filter that resolves the embed to the target file's body. If you skip this step, the embed will render as literal ![[Other Note]] text in Word.
A quick embed-handling checklist:
- Replace Obsidian image embeds with standard syntax and check that the chosen converter can access the image source.
- Inline any
![[Note]]content the reader actually needs to see. - For a local converter, keep attachment paths valid. The browser converter cannot read neighboring vault files from a single Markdown upload.
- Check the final
.docxopens cleanly on a machine that does not have your vault. -
Assume embeds will "just work"— they will not, without a resolver.
Keeping an exports folder with the required images helps a local conversion workflow resolve them. The resulting DOCX is self-contained only after those images have actually been embedded; inspect the exported file before sharing.
Conclusion: Choose Your Obsidian to Word Method
There is no single right way to convert Obsidian to Word — the best method depends on how often you export and how complex your vault is. For one-off exports, copy the note into the Markdown to Word converter and download a .docx in seconds, all in the browser with no uploads. For repeat exports with a fixed house style, invest an hour in Pandoc plus a reference template, add a Lua filter for wikilinks, and you get consistent, professional Word documents from your vault forever after. Whichever path you choose, handle wikilinks and embeds explicitly: they are the features that make Obsidian powerful to write in, and they are the features most likely to look broken if you ignore them on the way out.