Skip to content

Notes & knowledge

Notion or Obsidian Markdown to PDF or Word

Get knowledge-base entities: headings, paragraphs, backlinks text, callouts, lists, tables, code blocks, images, Mermaid text, and KaTeX source.

  • Output: PDF
  • Free: 5 conversions a day · 5 MB each
  • Deleted after 24 h · never used for training

Before you start

What to expect

  • Uploads are not used to train models, and retained files are deleted after 24 hours unless your account policy says otherwise.
  • This is Markdown document conversion, not a Notion API or Obsidian vault graph resolver.
  • Wikilinks, callouts, toggles, Mermaid, and KaTeX may need preprocessing for polished PDF or Word output.

What the output contains

  • A typeset PDF from exported Markdown; switch to DOCX when the goal is Word editing instead of distribution.
  • Headings, lists, tables, code blocks, links, and standard Markdown images handled through the document engine document path.
  • Obsidian wikilinks and Notion callouts are rendered as text unless you preprocess them into standard Markdown.
  • Embedded images work only when the export package or relative image paths are available to the converter.

A real run

Obsidian project note export

Input
18 Markdown notes combined into one file, 52 headings, six callouts, nine wikilinks, three local PNGs, and two Mermaid code fences.
Output
PDF with table of contents, headings, images, and code blocks; wikilinks remained as bracketed text and Mermaid diagrams stayed as fenced code.

Known failure modes and how they're handled

Broken [[wikilinks]] or backlinks
Wikilinks are not resolved against a vault graph. Convert them to normal Markdown links or keep them as readable text.
Notion callouts, toggles, and databases
Exported Markdown is rendered, but interactive Notion blocks flatten. Convert databases to CSV/XLSX separately when tables matter.
Images missing from an export
The Markdown must reference uploaded image files. A lone .md file cannot fetch private Notion or vault assets.
Mermaid and KaTeX expectations
Source blocks are preserved as code/text unless your pipeline renders diagrams or math before conversion.

Command line

Do it yourself

pandoc --reference-doc

bash
pandoc notes.md -o notes.docx --reference-doc=brand-template.docx

Great for Word output after you normalize wikilinks, callouts, and image paths.

pandoc

bash
pandoc notes.md -o notes.pdf --toc --pdf-engine=typst

Does not magically resolve private Notion assets or render vault-specific plugins.

Questions about this workflow

Can it convert a whole Obsidian vault?

Not as a graph-aware vault export. Combine or batch Markdown files deliberately and make sure linked images are included.

Will Notion databases become Word tables?

Only if they are exported as real Markdown/CSV tables. Rich database views should be exported separately.

Can I get DOCX instead of PDF?

Yes. Use the Markdown-to-Word path when editing in Word matters more than a fixed PDF.

What happens to Obsidian callouts?

They usually become blockquote-like text. Custom icons, fold states, and plugin behavior are not preserved.