Obsidian is a powerful note-taking tool built on plain Markdown files. If you have years of notes, reports, or documents stored in Word format, converting them to Markdown lets you bring everything into your Obsidian vault. This guide walks through the best workflow for Word to Obsidian conversion.
Why Move Word Documents to Obsidian?
Obsidian’s core strength is linking notes together. Once your content is in Markdown, you can:
- Create
[[wikilinks]]between related notes - See backlinks — every note that mentions the current one
- Build a knowledge graph of connected ideas
- Use community plugins for spaced repetition, tasks, templates, and more
- Keep everything in plain text files that will outlast any app
Converting Word Documents to Markdown
The fastest way is WordToMD:
- Open the converter and drag your .docx file onto it
- Review the Markdown output on the right
- Download the .md file
The output preserves headings, bold/italic, lists, tables, and hyperlinks — exactly what Obsidian needs.
What Obsidian-Specific Formatting to Add
After the initial conversion, you’ll want to add Obsidian-specific elements:
YAML Frontmatter
Obsidian supports YAML frontmatter for metadata:
---
title: "Project Proposal"
date: 2026-05-23
tags: [project, planning, Q2]
status: active
---
Add this block at the very top of your converted .md file. Obsidian reads these properties and makes them searchable via the Properties panel.
Wikilinks
External hyperlinks convert from Word like this:
See the [project plan](https://docs.example.com/plan)
For internal note references in Obsidian, replace or add wikilinks:
See [[Project Plan]] for details.
You can use both formats — Obsidian handles standard Markdown links and its own [[wikilink]] syntax.
Tags
In Obsidian, tags are written as #tagname inline or listed in frontmatter. Add relevant tags after conversion to integrate the note into your vault’s tagging system.
Handling Headings
Obsidian’s Outline panel and Heading search work best when headings follow a logical hierarchy. After conversion, verify your heading levels:
# Document Title (H1 — one per file)
## Section One (H2)
### Subsection (H3)
## Section Two (H2)
See Markdown Headings Guide for rules on heading hierarchy.
Tables in Obsidian
Obsidian renders standard GFM tables. Tables from your Word document will convert correctly via WordToMD. Example:
| Meeting | Date | Outcome |
|---|---|---|
| Q1 Review | 2026-03-01 | Budget approved |
| Strategy | 2026-04-15 | Roadmap updated |
For complex tables with merged cells or nested content, you’ll need to simplify them manually. Read Markdown Tables: A Complete Guide for Obsidian-specific table tips.
Images
Images embedded in your Word document won’t carry over automatically. After conversion:
- Export images from Word: Save As → Web Page (Filtered) — Word saves images to a separate folder
- Copy the image files to your Obsidian vault’s attachment folder
- Add image references in your note:
![[meeting-diagram.png]]
Obsidian uses its own ![[filename]] syntax for images in the vault, or standard Markdown .
Bulk Import: Converting Multiple Word Files
If you’re migrating a large document library:
- Convert files one at a time with WordToMD (free, no limits)
- Save each .md file to your vault directory
- For dozens or hundreds of files, see Batch Convert Word to Markdown
After bulk import, use Obsidian’s search to find notes that should be linked together, and add wikilinks progressively.
Common Issues
Bold text not rendering in Obsidian
Obsidian uses **bold** syntax. If your Word doc had manually bolded text without proper mapping, check the output for any unconverted formatting.
Tables showing raw pipe characters instead of rendering
Make sure you’re viewing the file in Reading Mode (not Editing Mode) in Obsidian, or check that the table has at minimum a header row separator (|---|---|).
Headings all showing as the same level The Word document used manual text formatting instead of Heading styles. Open the original in Word, apply Heading styles, and reconvert.
FAQ
Can I convert .doc files (old Word format)? Save them as .docx first (File → Save As → Word Document), then convert.
Does Obsidian support all Markdown syntax generated by WordToMD? Yes. Obsidian supports CommonMark plus GFM extensions, which is what WordToMD outputs.
How do I preserve the document’s internal section links?
Word bookmarks don’t directly convert. After conversion, replace bookmark links with Obsidian heading anchors: [[Note Name#Section Heading]].
What about callout boxes in Word? They convert to blockquotes in Markdown. Obsidian has its own callout syntax you can use instead:
> [!note]
> This is a note callout in Obsidian.
Conclusion
Converting Word to Obsidian Markdown is a two-step process: use WordToMD to get clean Markdown, then add Obsidian-specific elements like frontmatter, wikilinks, and tags. Once your documents are in your vault, Obsidian’s linking and search capabilities transform static documents into a connected knowledge base.