ConvertMDapp

Guide

How to Export Obsidian Notes to PDF

June 17, 2026 · 6 min read

Obsidian ships with a built-in Export to PDF command, so you don't need a plugin or an external tool to turn a note into a shareable, print-ready file. This guide walks through the exact steps, the export dialog options, and the gotchas that trip people up — dark themes, unrendered plugin content, and page breaks in long notes.

Export a single note to PDF

Open the note you want to export in reading or editing view, then choose one of these:

Obsidian renders the current note and opens an export dialog before saving. It exports whatever is currently displayed, so what you see is essentially what you get — including your theme, which matters more than you'd expect (see below).

The export dialog options

The dialog gives you a handful of settings that control layout. Here's what each one does.

Option What it controls Recommended for sharing
Page size A4, Letter, Legal, Tabloid, or custom dimensions A4 or Letter
Portrait / Landscape Page orientation Portrait (Landscape for wide tables)
Margin None, Minimum, Default, or Maximum whitespace around content Default
Downscale percent Scales content down to fit more per page (like zoom) 100% unless content overflows
Include filename as title Adds the note's name as an H1 at the top On, for standalone docs
Optimize for printing Adjusts colors/contrast for physical print On if you'll print it

Downscale percent is the setting most people miss. If a code block or table runs off the right edge of the page, drop the downscale to 90% or 80% and the whole thing shrinks to fit rather than getting clipped.

Gotcha #1: your theme comes along for the ride

The single most common surprise: the PDF uses your current Obsidian theme. If you're working in a dark theme, you'll export white text on a dark background — a huge ink-hog that looks wrong in most documents.

Before exporting, switch to a light theme:

  1. Open Settings → Appearance.
  2. Set Base color scheme to Light.
  3. Export, then switch back.

This applies to community themes too. A light base scheme gives you black text on white — the layout you almost always want for a document you'll send or print.

Gotcha #2: plugin content may not render

Obsidian's exporter captures rendered Markdown. Content generated by community plugins — Dataview queries, some callouts, certain embeds and transclusions — is generated on the fly and may not appear, or may export as raw code, if it hasn't finished rendering.

Fix it before you export:

Standard Markdown — headings, lists, tables, links, and native callouts — exports reliably. It's the dynamic, plugin-driven blocks you need to babysit.

Images and attachments

Good news: images and attachments stored in your vault export fine. Whether you embed with ![[image.png]] or a standard Markdown image link, Obsidian bundles them into the PDF as long as the file exists in the vault. Externally hosted images (linked by URL) require a connection at export time and can fail silently, so keep image files local when you need a reliable export.

Gotcha #3: page breaks in long notes

Obsidian flows a long note across pages automatically, but it won't always break where you'd like — a heading can land at the bottom of a page, orphaned from its section. To force a break, add a small CSS snippet.

Create a file in YourVault/.obsidian/snippets/page-breaks.css and enable it under Settings → Appearance → CSS snippets:

/* Add a manual page break before any horizontal rule */
@media print {
  hr.page-break,
  .page-break {
    page-break-after: always;
    border: none;
  }
}

Then drop an HTML divider wherever you want a new page to start:

<div class="page-break"></div>

Anything after that div begins on a fresh page in the exported PDF.

Exporting from Obsidian mobile

Here's a real limitation: Obsidian mobile has limited or no built-in PDF export. The ⋯ menu on iOS and Android often doesn't offer the same Export to PDF command as desktop, and results are inconsistent across versions.

The cross-device workaround is simple. Copy the note's raw Markdown, then paste it into a browser-based converter like ConvertMDapp at /. It runs 100% in your browser, so the note never leaves your device — the same privacy posture you get from a local vault — and you get a clean PDF from any phone, tablet, or computer with no signup, no watermark, and a live two-way preview so you can tweak the Markdown and watch the output update. It's also handy on desktop when you want editable tables in the preview or syntax-highlighted code without touching Obsidian's theme at all.

Quick workflow: desktop and mobile

To keep exports consistent wherever you are:

  1. On desktop: switch to a light theme, render the note in Reading view, then Export to PDF with A4/Letter and Default margins.
  2. On mobile (or when export misbehaves): copy the Markdown and paste it into the converter at / for a clean PDF in seconds.
  3. For long or complex notes: add the page-break snippet above, and downscale to fit wide content.

If you're new to converting Markdown generally, the complete guide to converting Markdown to PDF covers the fundamentals, and the Mac and Windows walkthrough shows platform-specific options.

FAQ

Why is my exported Obsidian PDF dark? Because the export uses your active theme. Switch to a light base color scheme under Settings → Appearance before exporting, then switch back afterward.

Why don't my Dataview tables or callouts show up in the PDF? Plugin-generated content must be fully rendered first. Open the note in Reading view, scroll through it so every block resolves, then export. If a block still won't render, paste the finished Markdown into the browser converter at / instead.

How do I control where pages break in a long note? Add a CSS snippet that applies page-break-after: always to a .page-break class, enable it in Settings, and insert <div class="page-break"></div> wherever you want a new page to start.