Obsidian to Word: Export Without Losing Formatting

You wrote something great in Obsidian. A project proposal, a technical spec, a client deliverable, meeting notes for your team. Now someone needs it as a Word document. Maybe your boss uses Word. Maybe the client's contract requires .docx deliverables. Maybe your team's shared drive is full of Word files and that's where work lives.

Whatever the reason, you need your Obsidian note in Word with the formatting intact. And if you've tried this before, you know it doesn't go smoothly.

Here are five methods for getting Obsidian notes into Word, ranked by formatting quality and ease of use.

Why direct copy-paste fails

Before the methods, it helps to understand the core problem. Obsidian stores your notes as plain markdown files. The formatted view you see in the editor is Obsidian's live rendering of that markdown source.

When you copy from Edit Mode and paste into Word, you get raw markdown syntax: ## instead of headings, **text** instead of bold, pipe characters instead of tables. Word doesn't interpret markdown.

When you copy from Reading Mode, the results are better but unreliable. Bold text has been inconsistent since Obsidian 1.x. Tables often paste as plain text or misaligned columns. Code blocks lose their monospace styling. Dark mode users get gray text on a dark background pasted into a white document.

The fundamental issue is that Obsidian's clipboard output isn't optimized for Word. Obsidian is a markdown editor; Word is a rich text processor. Something needs to bridge that gap.

Method 1: Pandoc Plugin

Formatting quality: Medium. Ease of use: Low.

Pandoc is a command-line document converter that handles markdown to .docx conversion. The Obsidian Pandoc Plugin brings this functionality into Obsidian's interface.

How it works:

1. Install Pandoc 3.1.9 or later on your system (it's a separate application, not just a plugin).
2. Install the Pandoc Plugin from Obsidian's community plugin directory.
3. Open the note you want to export.
4. Run the "Export to Word Document" command from the command palette.
5. Pandoc generates a .docx file.

What works: Standard markdown elements (headings, bold, italic, lists, links, basic tables) generally convert correctly. Pandoc is mature software with strong markdown-to-docx support.

What breaks: Obsidian-specific syntax is the problem. Wikilinks ([[page name]]) either break or render as literal text. Callouts (> [!note]) aren't recognized by Pandoc and export as plain blockquotes without the callout type or styling. Embedded files (![[note]]) don't resolve. Dataview queries export as raw code. If your notes use these Obsidian extensions heavily, the exported document will have gaps.

Other considerations: The plugin is beta-quality software. Installation requires both the plugin and a separate Pandoc install, which can be confusing. The output uses Word's default styling, which is functional but plain. There's no template system for professional formatting.

Method 2: Enhancing Export plugin

Formatting quality: Medium. Ease of use: Low.

The Enhancing Export plugin is another community plugin that wraps Pandoc (and other converters) with additional configuration options.

How it works: Similar to the Pandoc Plugin, but with more export format options and some additional settings for controlling the output. Still requires Pandoc installed on your system.

What works: Same as the Pandoc Plugin for standard markdown. The additional configuration options let you tweak some aspects of the output.

What breaks: Same limitations as Pandoc. Obsidian-specific syntax (wikilinks, callouts, embeds, dataview) still breaks or exports as raw text. The plugin adds a layer of configuration but doesn't solve the fundamental Obsidian-to-Word conversion challenges.

Other considerations: More configuration options means more complexity. If you're already comfortable with Pandoc, this plugin adds convenience. If you're not, the additional settings can be overwhelming.

Method 3: PDF-to-Word workaround

Formatting quality: Low. Ease of use: Medium.

This method uses Obsidian's built-in PDF export as an intermediate step, then opens the PDF in Word.

How it works:

1. Open your note in Obsidian.
2. Use Cmd+P (or Ctrl+P) and select "Export to PDF."
3. Save the PDF file.
4. Open the PDF in Microsoft Word (File > Open).
5. Word converts the PDF into an editable document.

What works: The visual layout is generally preserved because Word is recreating the document from the rendered PDF, not from markdown source.

What breaks: Plenty. Tables become images or lose their structure. Text may be split into text boxes instead of flowing naturally. Heading styles are lost (text is sized and bolded but not tagged as H1, H2, etc., so it won't appear in Word's navigation pane or table of contents). Code blocks become plain text. The document is technically editable, but reformatting it to be genuinely usable often takes as long as recreating it from scratch.

Other considerations: This method is the most accessible because it requires no plugins or external tools. But the output quality is the lowest of all five methods. It's a last resort, not a workflow.

Method 4: Reading Mode copy-paste

Formatting quality: Low to Medium. Ease of use: High.

The simplest approach: switch to Reading Mode in Obsidian, select all, copy, and paste into Word.

How it works:

1. Open your note in Obsidian.
2. Switch to Reading Mode (click the book icon or press Cmd+E).
3. Press Cmd+A to select all, Cmd+C to copy.
4. Open Word and paste with Cmd+V.

What works: Basic prose with bold, italic, and simple lists usually transfers. Inline code sometimes keeps monospace styling. Links improved in Obsidian v1.12.3.

What breaks: Bold text has been inconsistent since Obsidian 1.x. Tables are unreliable. Code blocks often lose styling. Headings may transfer as large bold text rather than proper Word heading styles (meaning they won't appear in the navigation pane or work with Word's table of contents feature). Dark mode users get dark background colors pasted into the document. Callouts, wikilinks, tags, and dataview all fail.

Other considerations: This is the fastest method when it works. For a simple note that's mostly paragraphs with some bold text and bullet points, it might be good enough. For anything with tables, code, or structured content, expect to spend time fixing the formatting manually.

Method 5: Unmarkdown (recommended)

Formatting quality: High. Ease of use: High.

Unmarkdown™ is a purpose-built markdown conversion tool that produces destination-specific output. Its "Copy for Word" feature generates clipboard content optimized specifically for Microsoft Word.

How it works:

1. Open your note in Obsidian (Edit Mode / Source mode).
2. Press Cmd+A to select all, then Cmd+C to copy the raw markdown.
3. Open unmarkdown.com in your browser.
4. Paste your markdown into the editor.
5. (Optional) Choose a template for professional styling.
6. Click "Copy for Word" in the destination bar.
7. Open Word and paste with Cmd+V.

What you get:

Real Word heading styles. H1 through H6 are tagged as proper heading styles, not just large bold text. This means they appear in Word's navigation pane (View > Navigation Pane), they work with Word's automatic table of contents feature (References > Table of Contents), and they follow Word's heading hierarchy for document structure.

Formatted tables. Markdown tables become native Word tables with borders, header row formatting, and proper cell alignment. This is one of the biggest improvements over every other method, where tables consistently break.

Styled code blocks. Fenced code blocks get a monospace font (Consolas) and a background color. Syntax highlighting is preserved when a language is specified. Inline code also gets monospace styling.

Working bold, italic, and strikethrough. No inconsistency, no regression. These work reliably every time.

Properly nested lists. Ordered lists, unordered lists, and task lists all transfer with correct indentation and numbering.

Callout styling. Obsidian's > [!note], > [!warning], and other callout types render as styled blockquotes with the callout type preserved.

Math rendering. LaTeX math notation ($...$ and $$...$$) renders as formatted equations.

Links. Markdown links become clickable hyperlinks in Word.

What each method preserves

Here's a side-by-side comparison of formatting quality across all five methods.

Adding professional styling

When a document needs to look polished, Unmarkdown™'s template system makes a noticeable difference. Instead of Word's default styling (Calibri, minimal spacing, no visual personality), you can apply a template before copying.

A few examples where templates matter:

Client deliverables. Choose a Consulting or Executive template. Your document gets professional typography, balanced spacing, and a cohesive visual style that makes it look intentionally designed rather than default.

Technical documentation. GitHub or Terminal templates give code blocks, tables, and technical content appropriate styling that feels native to a development context.

Academic work. Thesis or Paper templates handle heading hierarchies, citations, and formal structure well.

Internal memos. Meeting Notes or Corporate Blue templates add structure without being flashy.

Templates are entirely optional and are a Pro feature (free users get 8 templates, Pro unlocks all 62). The core Word conversion, with proper heading styles, formatted tables, and styled code, works for everyone with no account required.

Word downloads

If you prefer a direct download instead of copy-paste, Unmarkdown™ Pro also offers Word (.doc) file downloads. The downloaded file uses the same formatting pipeline as "Copy for Word" and opens directly in Microsoft Word. This is available through the File menu or the Share modal's Export tab.

The bottom line

Getting Obsidian notes into Word with intact formatting is harder than it should be. Direct copy-paste (both Edit Mode and Reading Mode) produces unreliable results. Pandoc handles standard markdown well but chokes on Obsidian-specific syntax. The PDF workaround creates technically editable but practically unusable documents.

Unmarkdown™ produces the highest-quality output by treating the conversion as a first-class problem rather than an afterthought. Real Word heading styles, formatted tables, styled code blocks, and working bold text, all in about 30 seconds. The core conversion is free, and the template library adds professional styling when you need it.

Try the Unmarkdown plugin for Obsidian

Unmarkdown is now available as an Obsidian community plugin. Right-click any note and copy it formatted for Google Docs, Word, Slack, OneNote, Email, or Plain Text, directly from your vault. You can also publish notes to the web with 62 templates.

How to install (Community Plugins directory approval pending):

1. Download main.js, manifest.json, and styles.css from the latest release
2. In your vault, create the folder .obsidian/plugins/unmarkdown/
3. Move the three downloaded files into that folder
4. Open Obsidian Settings > Community Plugins > Enable "Unmarkdown"
5. Go to Settings > Unmarkdown > Click "Connect account" to link your free Unmarkdown account

Once approved for the Community Plugins directory, you can install by searching "Unmarkdown" in Obsidian's plugin browser.

Related reading

• How to Export Obsidian Notes to Google Docs Without Losing Formatting
• Why Obsidian Loses Formatting When You Copy-Paste (and How to Fix It)
• How to Paste AI Output into Word with Heading Styles
• The Best Free Markdown to Word Converter in 2026
• Pandoc vs Unmarkdown: GUI Publishing vs CLI Power