How to Export Obsidian Notes to Word on Mac (4 Methods)

Where Obsidian stores your notes

Obsidian isn't a proprietary format. Every note in your vault is a plain .md file stored in a regular folder on your Mac. You can find your vault location in Obsidian's settings under "About" or by right-clicking any note and choosing "Reveal in Finder."

Because Obsidian notes are standard files, any Markdown-to-Word converter can process them. The challenge is that Obsidian extends Markdown with its own syntax, and that extended syntax doesn't have equivalents in Word.

What converts and what doesn't

Before choosing a method, understand what will and won't survive the conversion:

Converts normally

• Headings (H1–H6)
• Bold, italic, strikethrough
• Ordered and unordered lists
• Tables
• Code blocks and inline code
• Block quotes
• Standard Markdown links and images

Does not convert

• Wikilinks ([[note name]]) — appear as raw text
• Callout blocks — the > [!note] syntax renders as a block quote or raw text
• Dataview queries — appear as code blocks
• Embedded transclusions (![[other note]]) — appear as raw text
• YAML frontmatter — usually stripped or shown as plain text
• Tags (#tag) — appear as plain text with a hash symbol

No converter handles all Obsidian-specific features because Word simply doesn't have equivalents for them. Focus on getting the standard Markdown content across cleanly.

Method 1: Pandoc from Terminal

Pandoc converts Obsidian's .md files to .docx from the command line. It handles all standard Markdown correctly and ignores or strips Obsidian-specific syntax.

pandoc "/path/to/vault/My Note.md" -o "My Note.docx"

To strip YAML frontmatter, which Obsidian uses for metadata, add the --strip-comments flag or use a Lua filter. For most notes, Pandoc handles frontmatter gracefully by default.

Tradeoffs

• Requires Homebrew and terminal knowledge
• Wikilinks appear as raw [[text]]
• No batch UI — one command per file (unless you script it)

Method 2: Obsidian Pandoc plugin

The community plugin "Pandoc Plugin" adds an export option directly inside Obsidian. You open a note, run the export command, and get a .docx file. This requires Pandoc installed on your system.

1. Install Pandoc via Homebrew: brew install pandoc
2. In Obsidian, go to Settings → Community plugins → Browse
3. Search for "Pandoc Plugin" and install it
4. Open any note, open the command palette (Cmd+P), and run "Pandoc Plugin: Export as Word Document"

Tradeoffs

• Still requires Pandoc installed via Homebrew
• Plugin may not be updated for latest Obsidian versions
• Wikilinks and callouts still don't convert
• Convenient if you're already inside Obsidian

Method 3: Online converters

Upload your .md file to a web-based converter like CloudConvert or Dillinger. No installation required.

Tradeoffs

• Your notes leave your machine — privacy concern for personal vaults
• Limited formatting support for complex tables and code blocks
• One file at a time
• Works for quick one-off exports

Method 4: MarkDrop

Navigate to your vault folder in Finder, right-click any .md file, and choose "Convert with MarkDrop." The .docx file appears in the same folder. No terminal, no plugins, no uploads.

1. Open Finder and navigate to your Obsidian vault folder
2. Right-click any .md note
3. Select "Convert with MarkDrop" from the Services menu
4. The .docx appears alongside the original file

You can also select multiple notes and convert them all at once.

Tradeoffs

• macOS only
• Free tier: 5 conversions/month, Pro for unlimited
• Wikilinks still appear as raw text (Word has no equivalent)
• Everything else converts with proper Word styles

Which method should you use?

For power users already in Terminal, Pandoc works well. If you want to stay inside Obsidian, the plugin is convenient. For the fastest workflow from Finder, MarkDrop is the simplest path. Avoid online converters if your notes contain anything private.