Why Obsidian Export to Word Breaks Formatting (+ What Works)

The root cause: Obsidian isn't standard Markdown

Obsidian uses CommonMark as its base but adds proprietary extensions. These extensions make Obsidian powerful as a note-taking tool, but they create problems when you try to export to a format like Word that doesn't understand them.

When you run an .md file through a converter, the converter parses standard Markdown syntax and translates it to Word styles. Anything it doesn't recognize gets treated as plain text — which is why you see raw bracket syntax, broken callouts, and orphaned query blocks in your Word output.

What breaks (and why)

Wikilinks: [[note name]]

Obsidian's wikilink syntax creates bidirectional links between notes in your vault. Word has no concept of a vault or bidirectional linking. Converters either strip the brackets and leave the text, or output the entire raw syntax including brackets.

Fix: Before exporting, find and replace [[note name]] with just "note name" or convert to standard Markdown links: [note name](url).

Callout blocks: > [!note]

Obsidian's callout syntax creates styled information boxes. Converters treat the > as a block quote and the [!note] as literal text. You get a block quote with "[!note]" as its first line.

Fix: Replace callouts with standard block quotes. Remove the [!type] prefix and keep just the content after the >.

Dataview queries

Dataview is a community plugin that lets you write database-style queries in your notes. These queries are fenced code blocks with a dataview or dataviewjs language tag. Converters render them as code blocks — which is technically correct, but not useful in a Word document.

Fix: Remove Dataview blocks before exporting, or replace them with the static content they would generate.

Transclusions: ![[other note]]

Embedding one note inside another is an Obsidian-only feature. No converter pulls in the referenced note's content because it would need access to your entire vault structure.

Fix: Manually inline the content you want included, or remove the transclusion references before exporting.

YAML frontmatter

The metadata block at the top of Obsidian notes (between --- delimiters) contains tags, aliases, and custom properties. Most converters either strip it silently or render it as a code block at the top of the document.

Fix: Pandoc strips frontmatter by default. MarkDrop also handles this cleanly. If using another tool, manually remove the frontmatter block before converting.

What converts correctly

The good news is that the core content of most Obsidian notes is standard Markdown that converts perfectly:

• Headings — become Word heading styles (Heading 1, Heading 2, etc.)
• Bold and italic — become Word bold and italic
• Ordered and unordered lists — become Word list styles
• Tables — become Word tables with borders
• Code blocks — become monospace-formatted paragraphs
• Block quotes — become indented, styled paragraphs
• Standard links — become clickable hyperlinks in Word

If your notes primarily use standard Markdown with occasional Obsidian features, you'll get a clean Word document with minimal cleanup needed.

Best approach for clean exports

1. Write export-friendly notes — if you know a note will be shared, use standard Markdown links instead of wikilinks and avoid callouts
2. Clean before exporting — do a quick find-and-replace for [[ and [! patterns
3. Use a reliable converter — Pandoc or MarkDrop handle standard Markdown accurately and strip frontmatter cleanly
4. Review the output — open the .docx and check for any raw syntax that slipped through