Import Word Documents Into Obsidian — Convert .docx to Markdown Free

Obsidian stores all notes as plain Markdown files. To bring a Word document into your Obsidian vault, the cleanest path is to convert the .docx to Markdown first, then move the .md file into your vault folder. Our free browser converter handles the conversion in seconds — no plugin, no upload, no Obsidian settings to configure.

Why You Cannot Directly Open Word Files in Obsidian

Obsidian is built around plain text Markdown files. While you can attach .docx files to a note using Obsidian's attachment system, you cannot open them as editable notes — Obsidian has no Word renderer built in. The file sits in your vault but does not become searchable, linkable, or renderable text in the Obsidian interface.

For a Word document to become a first-class Obsidian note — searchable, linkable with [[wiki links]], connected to your graph — it needs to be a .md file. Converting first is the required step.

Some Obsidian users install community plugins for document conversion, but a plugin is not necessary. The browser converter handles the .docx to .md transformation outside of Obsidian, and you copy the file in directly.

Step-by-Step: Converting and Importing

The full workflow:

1. Go to the Word to Markdown converter
2. Drop your .docx file onto the tool
3. Click Download .md to save the Markdown file
4. Move or copy the downloaded .md file into your Obsidian vault folder
5. Open Obsidian — the file will appear in your file list immediately

Your vault folder is wherever you created it on your computer. On most systems, you can find it via Settings > About > Override config folder in Obsidian, or just check where you initially set up your vault.

Once the .md file is in the vault, Obsidian treats it exactly like any other note. You can edit it, link to it with [[note name]] wiki links, include it in your graph view, and tag it normally.

Sell Custom Apparel — We Handle Printing & Free Shipping

What Converts Well for Obsidian Use

Obsidian's Markdown renderer supports the standard Markdown spec plus some Obsidian-specific extensions. Here is how the conversion maps:

Word Element	Markdown Output	Renders in Obsidian?
Heading 1	# Heading	Yes
Heading 2-6	##, ###...	Yes
Bold	**text**	Yes
Italic	*text* or _text_	Yes
Bullet list	- item	Yes
Numbered list	1. item	Yes
Link	[text](url)	Yes
Table	Pipe table syntax	Yes
Image	Not converted	Add manually

Nearly everything you need for a well-structured note converts cleanly. Images are the exception — see the section below.

Handling Images When Importing to Obsidian

Images from Word documents do not convert cleanly to Markdown format. Markdown images require a file path or URL: ![alt text](path/to/image.png). Our converter extracts image data from the .docx, but linking it correctly for Obsidian requires a bit of manual work.

The recommended approach for Word documents with images:

1. Rename your .docx file to .zip and unzip it (right-click > Open As ZIP or change extension)
2. Find the images inside the word/media/ folder
3. Copy those image files into your Obsidian vault's attachments folder
4. In the converted Markdown file, replace any broken image references with the correct Obsidian path: ![[image-filename.png]]

For text-heavy documents without images, skip all of this — the conversion output is ready to use as-is.

Adding Obsidian-Specific Features After Import

Once your converted note is in Obsidian, you can add Obsidian-specific elements that did not exist in the Word document:

Wiki links: Connect the note to other notes in your vault by adding [[Note Name]] references. These create bidirectional links in the graph view.

Tags: Add tags to the top of the note using YAML frontmatter:

---
tags: [project, documentation, 2026]
---

Callout blocks: Obsidian supports callout blocks for notes, warnings, and tips. Add them using the > [!NOTE] syntax after import where useful.

Embedded queries: If you use Dataview or other plugins, you can embed queries into the note after import to dynamically link related content.

The base Markdown structure from the Word conversion is the foundation — Obsidian's rich feature set layers on top of it naturally.

Frequently Asked Questions

Is there an Obsidian plugin that imports Word files directly?

Yes — the Pandoc plugin for Obsidian can import .docx files using Pandoc installed on your system. If you prefer an approach that requires no plugins or system installs, the browser converter plus manual file copy achieves the same result.

Can I convert multiple Word files for a large vault import?

The browser tool converts one file at a time. For bulk import of many Word files into Obsidian, the Pandoc command-line tool with a batch script is more efficient.

Will my Word document footnotes appear correctly in Obsidian?

Footnotes in Word may appear as inline text in the Markdown output rather than as proper footnote references. Standard Markdown footnotes use the [^1] syntax, which you can add manually after conversion.

Does this work for Logseq and Roam Research too?

Both Logseq and Roam Research also use Markdown internally. The converted .md output from our tool is compatible with Logseq. Roam uses a slightly different format for blocks; the Markdown is a good starting point but may need some restructuring for Roam.