How to Convert Your Obsidian Vault to Word Documents on Mac

Why Convert Obsidian Notes to Word Documents?

Obsidian is a powerful Markdown-based note-taking system, but the real world often demands Word documents. Academic institutions require .docx submissions. Clients can't open .md files. Collaborators use track changes in Word, not GitHub-style diffs.

The challenge isn't whether to convert — it's how to do it without destroying your carefully formatted notes, losing image embeds, or spending hours manually copying and pasting.

When You Need Word Format

Common scenarios where Obsidian → Word conversion becomes necessary:

• Academic papers — Most journals and universities require .docx submissions with specific formatting
• Client deliverables — Proposals, reports, and documentation that clients expect to edit in Word
• Collaborative editing — Working with teams that use Word's track changes and comments
• Publishing workflows — Book manuscripts, magazine articles, or content that enters traditional publishing pipelines
• Corporate environments — Organizations with standardized Word templates and approval processes

What Gets Lost in Translation

Converting Markdown to Word isn't lossless. Here's what typically changes or breaks:

• Internal wiki-links — Obsidian's [[Note Name]] syntax doesn't translate to Word hyperlinks
• Backlinks — The graph of connections between notes is a database feature, not something Word can represent
• Embedded queries — Dataview queries, search embeds, and dynamic content won't work in static Word documents
• Custom CSS styling — Themes and snippets that change how notes look in Obsidian don't carry over
• Relative image paths — Images stored in attachments/ folders may break depending on how the conversion handles paths

Understanding these limitations upfront helps you choose the right conversion method and prepare your notes accordingly.

Understanding Your Obsidian Vault Structure

Before converting anything, you need to understand how Obsidian organizes your files — because conversion tools interpret vault structure differently.

Vault File Organization

An Obsidian vault is just a folder containing:

• Markdown files — Your actual notes, ending in .md
• Attachments folder(s) — Images, PDFs, and other embedded files (location configured in Settings → Files and links)
• Hidden .obsidian folder — Plugin configs, themes, workspace state (not needed for conversion)
• Subfolders — Whatever organizational structure you've created

Most conversion tools only see the .md files. They don't know about Obsidian's internal database of links and tags.

Links and Embeds to Consider

Obsidian supports several link formats that affect conversion:

• Wiki-links — [[Note Name]] or [[Note Name|Display Text]]
• Markdown links — [Display Text](path/to/file.md)
• Image embeds — ![[image.png]] or ![](image.png)
• Relative vs absolute paths — Whether images reference ./attachments/img.png or just img.png

Conversion tools handle these differently. Pandoc can convert wiki-links if configured. PDF export flattens everything to static images. MarkDrop preserves standard Markdown image syntax but strips wiki-links.

If your notes heavily use wiki-links for internal navigation, you'll need to decide whether to convert them to standard Markdown links first or accept they'll become plain text in Word.

Method 1: Using Pandoc Plugin (Best for Single Files)

Pandoc is the Swiss Army knife of document conversion. It's a command-line tool that converts between dozens of formats, including Markdown to Word. The Obsidian Pandoc plugin wraps this power in a (slightly) more user-friendly interface.

Installing Pandoc on macOS

Pandoc requires Homebrew, the macOS package manager. If you don't have Homebrew installed:

1. Open Terminal (Applications → Utilities → Terminal)
2. Paste this command and press Enter: /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
3. Follow the prompts (it takes 5-10 minutes)
4. Once Homebrew is installed, run: brew install pandoc
5. Verify installation with: pandoc --version

This is the steepest part of the learning curve. If you're not comfortable with Terminal, this method may not be worth it.

Setting Up the Obsidian Plugin

Once Pandoc is installed system-wide:

1. In Obsidian, go to Settings → Community plugins
2. Disable Safe mode if it's your first plugin
3. Click Browse and search for "Pandoc Plugin"
4. Install and enable the plugin
5. Go to the plugin settings and set the Pandoc path (usually /opt/homebrew/bin/pandoc on Apple Silicon Macs, or /usr/local/bin/pandoc on Intel Macs)

Converting Your First File

To convert a note to Word:

1. Open the note in Obsidian
2. Open the command palette (Cmd+P)
3. Type "Pandoc" and select "Pandoc Plugin: Export as Word Document (.docx)"
4. Choose where to save the .docx file

The conversion takes ~2-5 seconds per file. Pandoc preserves headings, lists, code blocks, tables, and images (if paths are correct). It's the most accurate conversion method available.

Limitations of This Approach

Pros:

• Free and open source
• Best formatting preservation (handles complex tables, code blocks, nested lists)
• Highly customizable via Pandoc templates
• Works offline

Cons:

• Requires Homebrew and command-line setup
• Converts one file at a time (no batch processing in the plugin)
• Steep learning curve for customization
• Image paths must be correct or embeds break
• Wiki-links become plain text unless you write custom filters

For converting 5-10 files, this is manageable. For converting your entire 500-note vault? You'll spend an hour clicking through the command palette.

Method 2: PDF Export Then Convert (Quick but Lossy)

Obsidian has a built-in PDF export feature (Settings → Core plugins → PDF export). You can export any note to PDF, then use Preview or Adobe Acrobat to convert PDF → Word.

Step-by-Step PDF Conversion

1. In Obsidian, open the note you want to convert
2. Click the three-dot menu (⋮) in the top-right
3. Select "Export to PDF"
4. Save the PDF
5. Open the PDF in Preview (or Adobe Acrobat)
6. In Preview: File → Export as Word (this option may not appear on older macOS versions)
7. In Adobe Acrobat: File → Export To → Microsoft Word → Word Document

This creates a .docx file, but the result is barely editable. PDF-to-Word conversion uses OCR-like text extraction. You'll get text blocks, but formatting is destroyed.

When This Method Makes Sense

Pros:

• No installation or setup required
• Works immediately
• Preserves visual layout (as an image-like representation)

Cons:

• Not actually editable — text is extracted, not converted
• Tables, code blocks, and formatting become mangled
• Images are embedded as low-res bitmaps
• No batch processing
• Requires Adobe Acrobat for reliable conversion (Preview's Word export is buggy)

This method only makes sense if you need a quick visual reference document, not an actual editable Word file. If someone just needs to see your notes in Word format without editing them, this works. For anything else, skip it.

Method 3: MarkDrop for Batch Conversion (Fastest for Multiple Files)

MarkDrop is a native Mac app that converts Markdown files to Word documents via Finder's right-click menu. It's designed specifically for the "I have 50 .md files and I need them all as .docx now" scenario.

Setting Up MarkDrop on Mac

1. Download MarkDrop from mark-drop.app
2. Open the .dmg and drag MarkDrop to your Applications folder
3. Open MarkDrop once to grant it Finder extension permissions (System Settings → Privacy & Security → Extensions → Finder → Enable MarkDrop)
4. That's it. No command-line setup, no Homebrew, no configuration files.

Converting Single Files

To convert one Obsidian note:

1. In Finder, navigate to your vault folder
2. Right-click any .md file
3. Select "Convert to Word with MarkDrop"
4. The .docx appears in the same folder ~2 seconds later

Free tier gives you 5 conversions per month. Pro ($9.99 one-time) unlocks unlimited conversions plus batch processing and Google Docs upload.

Batch Converting Your Entire Vault

To convert dozens or hundreds of notes at once:

1. In Finder, select all the .md files you want to convert (Cmd+A selects all files in a folder)
2. Right-click the selection
3. Choose "Convert to Word with MarkDrop"
4. All selected files convert in parallel

Tested on a 100-file vault: conversion takes ~15-20 seconds total. Compare this to Pandoc Plugin where you'd manually run the command 100 times.

What Formatting Gets Preserved

MarkDrop preserves:

• Headings (H1-H6 become Word heading styles)
• Bold, italic, strikethrough
• Ordered and unordered lists (including nested lists)
• Code blocks (converted to Word's monospace style)
• Tables (Markdown tables become Word tables)
• Images with standard Markdown syntax ![alt](path)
• Blockquotes

What doesn't convert:

• Wiki-links (they become plain text)
• Obsidian-specific syntax (callouts, embedded notes)
• Custom CSS or themes
• Footnotes (converted to plain text with [^1] notation preserved)

MarkDrop is optimized for clean Markdown that uses standard syntax. If you rely heavily on Obsidian plugins and custom formatting, expect some manual cleanup in Word.

Pros:

• Native Mac experience — right-click in Finder, done
• Batch processing — convert entire vault in seconds
• No technical setup or command-line knowledge
• Preserves standard Markdown formatting well
• Files stay on your machine (no upload to online converters)

Cons:

• macOS only (no Windows or Linux support)
• Paid app for unlimited use ($9.99, though free tier covers testing)
• Doesn't handle Obsidian-specific syntax beyond standard Markdown

Side-by-Side Comparison: Which Method Should You Choose?

Comparison Table

Decision Framework

Choose Pandoc Plugin if:

• You're converting fewer than 10 files
• You need the absolute best formatting quality (complex tables, nested lists, code blocks)
• You're comfortable with command-line tools
• You want free and open-source tools

Choose MarkDrop if:

• You need to convert 10+ files (or your entire vault)
• You want a native Mac workflow (no command line)
• You prioritize speed over absolute formatting perfection
• You're willing to pay $10 for unlimited conversions

Skip PDF export unless:

• You literally just need a visual snapshot
• The recipient won't edit the document
• You have zero other options available

Time comparison for converting different vault sizes (tested on M1 MacBook Pro):

Best Practices for Converting Obsidian Vaults

Pre-Conversion Checklist

Before converting your vault, prepare your notes to minimize post-conversion cleanup:

• Check image paths — Open a few notes with images and verify embeds work. If images show broken in Obsidian, they'll break in Word too.
• Convert wiki-links to Markdown links — If preserving clickable links matters, use a find-and-replace to convert [[Note Name]] to [Note Name](Note%20Name.md). Tools like Obsidian Link Converter plugin automate this.
• Clean up frontmatter — YAML frontmatter (the metadata between --- lines at the top of notes) becomes visible text in Word. Delete it or move it to the end if you don't need it in the Word doc.
• Organize attachments — Make sure all images are in one consistent location (like attachments/) and paths are relative, not absolute.
• Test on a subset first — Convert 3-5 representative notes before batch-processing your entire vault. Check the Word output for issues.

Post-Conversion Tips

After conversion, expect some cleanup in Word:

• Apply Word styles — Headings convert to plain bold text. Reapply Word's Heading 1/2/3 styles for proper document structure and table of contents generation.
• Fix broken image links — If images don't appear, they're likely using absolute paths. Copy images into the same folder as the .docx file and re-insert them manually.
• Remove wiki-link artifacts — Text like [[Note Name]] will appear as plain text. Find and replace [[ and ]] to clean it up.
• Check code block formatting — Code blocks should be monospace. If they're not, select them and apply Courier New or Consolas font.
• Verify table formatting — Complex Markdown tables may need border/spacing adjustments in Word.

Troubleshooting Common Conversion Issues

Broken image links: This happens when images use absolute paths (/Users/yourname/vault/attachments/img.png) instead of relative paths (attachments/img.png). Fix by:

• In Obsidian Settings → Files and links, set "Default location for new attachments" to "In subfolder under current folder"
• Use relative paths: ![](./attachments/img.png) instead of absolute paths
• If images are already broken, re-embed them using drag-and-drop in Obsidian to regenerate correct paths

Internal wiki-links not converting: Wiki-links ([[Note Name]]) are Obsidian-specific and don't translate to Word hyperlinks. Solutions:

• Use standard Markdown links instead: [Note Name](Note%20Name.md)
• Accept they'll become plain text and manually hyperlink them in Word if needed
• For Pandoc users, write a Lua filter to convert wiki-links (advanced, see Pandoc Lua filters documentation)

Code blocks losing monospace formatting: If code blocks appear in regular font, manually select them in Word and apply Courier New or Consolas. Or set up a Pandoc template that maps code blocks to a custom Word style.

Tables with weird spacing/borders: Markdown tables use plain text alignment. Word tables need explicit border and spacing settings. After conversion, select the table, right-click → Table Properties → Borders and Shading to adjust.

Special characters displaying as & or <: HTML entities sometimes leak through in conversions. Find and replace:

• & → &
• < → <
• > → >

File path problems on Mac: If files won't convert, check that file names don't contain special characters (:, /, ?). macOS allows these in Finder but they break paths in conversion tools. Rename files to use only letters, numbers, hyphens, and underscores.