Nothing to preview yet.
Export Obsidian notes to PDF with real page setup and proper bookmarks. Your vault is already plain Markdown on disk, so a note converts directly — the wrinkle is that a few pieces of Obsidian syntax are not standard Markdown.
An Obsidian vault is an ordinary folder of .md files, which makes this simpler than it looks. Open the vault folder and drag the note onto this page. To copy instead, switch the note to source mode first — on the rendered view you will copy formatted text and lose the Markdown structure.
Obsidian adds several conveniences that only mean something inside Obsidian. Outside it they are just characters, so they need converting before the note leaves.
Obsidian prints through the same engine, but it prints the note as it appears in the app. Your theme, your custom CSS and your font size all come along, so a dark theme becomes a dark PDF and a comfortable reading width becomes an odd measure on A4. Here the document is laid out for paper from the start: you choose the page size, margins and typeface, and the preview shows the actual page rather than the app.
Every heading becomes a real PDF bookmark, so a long note stays navigable in a reader's sidebar instead of being one continuous scroll. Turn on Contents in the style panel for a linked table of contents at the front, and Title page to promote the note's title onto its own page. Both are useful for anything you intend to share rather than skim.
The syntax that does not carry over is covered above; it is worth saying that just as much does, because underneath its own additions Obsidian is standard Markdown. Headings, bold and italic, ordinary links, fenced code blocks with a language tag, tables, task lists, footnotes and block quotes all convert exactly as written. What is worth checking before converting is specifically Obsidian's own layer on top — wikilinks, transclusions and callouts — rather than everything in the note.
Batch conversion is not supported here, and exporting a whole vault is arguably the wrong goal anyway. The realistic workflow is exporting the specific notes that need to leave Obsidian as standalone documents: a set of meeting notes to send to someone outside the vault, or a finished piece of writing ready to go out. The rest of a typical vault — notes full of unresolved internal links and half-formed thoughts meant to be read inside Obsidian, next to everything they link to — does not stand alone as a document regardless of the export tool, so it is no great loss that it does not convert as a batch.
Open your vault folder in the file manager and drag the .md file onto this page, or switch the note to source mode, copy the text and paste it in. Then click Download PDF.
They stay as text, because they resolve against your vault and a PDF cannot reach it. Rewrite the ones readers need to follow as normal Markdown links with full URLs before converting.
A callout is a block quote with a marker line, so it renders as a block quote. The text and structure survive; the coloured box and icon do not.
No — Dataview builds them when you view the note, so the file itself only contains the query. Copy the rendered table out of Obsidian and paste it in as a Markdown table.
No. A transclusion embeds another note live, inside Obsidian, and there is nothing to resolve that reference against once the text leaves the vault, so it arrives as literal text. Paste the transcluded note's content in by hand if it needs to appear.
Properties are stored as YAML front matter at the top of the note's raw source. Front matter is recognised here rather than printed, and can be promoted onto a title page, so it will not appear as a stray block of key-value pairs in the output.
No — only the Markdown text converts. An embedded PDF, audio file or other attachment is not something a Markdown-to-PDF converter can pull in; only images referenced by URL or embedded as data URIs are handled.