Obsidian uses standard markdown — the same format every major LLM outputs. Getting that content into a professional PDF should not require CSS hacking or a theme workaround. Paste your note into MarkdownTools, pick a theme designed for print, and download in 30 seconds.
Obsidian's native PDF export renders your note using your vault theme. Vault themes are optimized for screen reading — dark backgrounds, comfortable line heights, editor-specific typography. These choices look wrong in a PDF: low contrast on white paper, fonts that are not tuned for print, and margins that assume a screen, not a page.
There is no built-in way to apply a separate print-optimized theme for PDF specifically. The workaround is writing custom CSS — which works, but is a maintenance burden that most Obsidian users should not have to deal with just to share a note.
Theme mismatch
Screen themes look wrong on paper
No print themes
No separate PDF styling built in
Vault-specific syntax
Wikilinks, callouts need handling
Typical Obsidian note (source mode)
--- title: Project Alpha date: 2026-05-16 tags: [project, active] --- # Project Alpha ## Status > [!NOTE] Current phase > Discovery and research ## Key contacts - [[Alice Chen]] — product lead - [[Bob Kim]] — engineering ## Next steps - [ ] Review [[Architecture ADR]] - [ ] Draft spec by Friday
Four steps. Works for any Obsidian note that uses standard markdown structure.
Open the note in Obsidian. Switch to source mode (top-right icon or Cmd+E) to see the raw markdown. Select all (Cmd+A) and copy. Source mode ensures you get the raw markdown, not the rendered text. About 5 seconds.
Open MarkdownTools and paste your note into the editor. The live preview renders the note immediately. Frontmatter (the --- block at the top) is stripped automatically. Standard markdown renders correctly — headings, lists, code blocks, tables. 5 seconds.
Choose Clean for documentation or technical notes, Classic for readable reports and summaries, or Elegant for client-facing documents. Scan the preview to check that any Obsidian-specific syntax (wikilinks, callout blocks) was handled. 15 seconds.
Click the PDF button. A professionally formatted PDF is generated server-side using Chromium and downloads in under a second. Your content is never stored. 5 seconds.
Obsidian-specific syntax that needs handling before PDF export — and exactly how to handle it.
Wikilinks: [[Note Name]]
Problem: Renders as literal text with double brackets. External readers see [[Note Name]] instead of a link or the linked concept.
Fix: Replace with plain text (the concept name), a standard markdown link if you have a URL, or delete if the link was only for internal vault navigation. Most notes read fine without wikilinks.
[[Alice Chen]] → Alice Chen [[Architecture ADR]] → the architecture decision record
Callouts: > [!NOTE] text
Problem: The [!NOTE] type identifier renders as literal text inside a blockquote. The callout type and any icon are Obsidian-only features.
Fix: Remove the [!TYPE] line and keep the blockquoted content as a standard blockquote. Or rewrite as a bold paragraph. The content is the valuable part, not the callout wrapper.
> [!NOTE] > Key finding here → > Key finding here → OR: **Key finding:** text here
Frontmatter: --- ... ---
Problem: YAML frontmatter with title, date, tags, and Obsidian properties appears at the top of the note.
Fix: MarkdownTools strips frontmatter automatically. You do not need to delete it before pasting — it will not appear in the rendered output or the PDF.
--- title: My Note tags: [project] --- Note content begins here.
Dataview blocks: ```dataview ... ```
Problem: Dataview queries are plugin-specific code that executes inside Obsidian. Outside the vault, they render as code blocks — the query syntax, not the results.
Fix: Run the Dataview query in Obsidian first. Copy the rendered table or list output. Replace the query block with the actual data as a standard markdown table or list.
```dataview LIST FROM #project ``` → Replace with the actual list items
Embedded notes: ![[Note Name]]
Problem: Note transclusion (embedding one note inside another) does not work outside Obsidian. The ![[]] syntax renders as an exclamation mark followed by wikilink text.
Fix: Open the embedded note separately, copy its content, and paste it inline in your export note. This is a manual step but necessary for the embedded content to appear in the PDF.
![[Meeting Notes 2026-05-15]] → Paste the actual content of that note here
Tasks plugin: - [ ] and - [x]
Problem: Standard markdown task syntax (- [ ] and - [x]) renders correctly as checkboxes in most parsers. Obsidian Tasks plugin extended syntax (- [>] for deferred, - [-] for cancelled) does not.
Fix: Standard task checkboxes ([ ] and [x]) convert cleanly — no action needed. Tasks plugin extended states should be converted to a text label (e.g., "deferred:", "cancelled:") before export.
- [ ] Pending task → renders as checkbox - [x] Done task → renders as checked - [>] Deferred → convert to: - [ ] (deferred)
Notes that live in a vault but need to travel outside it — to collaborators, clients, or an archive that does not require Obsidian to open.
Compile a week of daily notes into a single document and export as PDF for a personal review or team status update. Strip out the wikilinks before exporting, and the remaining content — tasks, notes, decisions — converts to a clean, shareable PDF that does not require anyone to have Obsidian.
Obsidian is a popular choice for meeting notes because the keyboard-driven workflow is fast. After a meeting, copy the note, paste into MarkdownTools, and export a formatted PDF to share with attendees or file in a project folder. No reformatting, no copy-paste into a word processor.
Research notes in Obsidian typically include extensive wikilinks to connected notes, embedded queries, and callout blocks for key findings. Strip the Obsidian-specific syntax and the underlying research content — summaries, quotes, analysis — converts cleanly to a PDF that can be shared with collaborators who do not use Obsidian.
Project notes, architecture decisions, and planning documents written in Obsidian are ideal for export. These notes tend to use standard markdown — headings, lists, code blocks, and tables — with minimal Obsidian-specific syntax. They convert cleanly and produce professional documentation that stands on its own outside the vault.
Literature notes and book summaries are among the cleanest Obsidian content for PDF export. They rarely use wikilinks or callouts in ways that need significant cleanup. Paste, pick the Elegant theme for a polished reading-document feel, and export a PDF worth keeping.
Evergreen notes — Obsidian's permanent note format — are written to be self-contained explanations of a concept. These notes are designed to be readable in isolation, which makes them ideal for PDF export. They typically use clean heading structure, minimal vault-specific syntax, and prose that reads well outside the graph view.
Obsidian is built for thinking, not publishing. The note-taking workflow — fast keyboard input, wikilink navigation, graph view — is excellent. But when you need to share a note with someone who does not use Obsidian, or when you need a polished document for a client or manager, the built-in PDF export falls short.
The fundamental issue is that Obsidian's PDF export renders your note using the current vault theme. Vault themes are designed for long reading sessions on screen — they optimize for eye comfort, dark mode compatibility, and visual hierarchy in the editor. These are different requirements from a print or PDF output, where you need high contrast on white, appropriate margins, and typography that looks professional when printed or viewed in a PDF reader.
There is also no built-in way to apply a separate print theme for PDF export. You can write custom CSS to override print styles, but this is a developer task, not something a typical Obsidian user wants to maintain. For a note-taking app used primarily by non-developers, this is a real gap.
Obsidian uses standard CommonMark markdown with several extensions. For PDF export, you need to understand which Obsidian features are vault-specific and which are standard markdown that will render correctly in any parser.
Wikilinks ([[Note Name]] and [[Note Name|Display Text]]) are the most common Obsidian-specific element. They are navigation links within the vault. Outside Obsidian, they are meaningless — there is no vault to navigate. Before exporting, decide whether each wikilink adds value to the PDF reader. If the linked concept is explained in the same note, you can remove the brackets and keep the text. If the link points to context the reader needs, add a brief explanation inline. If the link is pure internal navigation, delete it entirely.
Callout blocks (> [!NOTE], > [!WARNING], > [!TIP], etc.) are a more significant challenge. The callout type identifier on the first line is not standard markdown. The content below it is blockquoted markdown. For PDF export, the cleanest approach is to decide whether the callout is structural (meant to highlight something important) or content (the information itself matters). For structural callouts, replace with bold text or a heading. For content callouts, keep the text and remove the [!TYPE] line, leaving a clean blockquote.
Dataview and Tasks plugin blocks execute inside Obsidian but are static code blocks outside it. These should be replaced with the actual output you want in the PDF. Run the Dataview query in Obsidian, copy the rendered table or list, and paste that as a standard markdown table or list in your export note.
If you frequently export specific notes or note types to PDF, it is worth structuring those notes with export in mind from the start. The changes are small but make export significantly faster.
Use a clear heading hierarchy. Obsidian power users sometimes rely on visual hierarchy through formatting rather than headings, because the graph view provides navigation context. In a PDF, the heading structure is the navigation. Use H1 for the document title, H2 for major sections, and H3 for subsections. Avoid skipping levels. A note with a clean heading structure converts to a PDF that is easy to navigate without any editing.
Limit wikilinks in export-intended notes. If a note is meant to be shared, minimize wikilinks in the prose. Use them in the backlinks panel for your own navigation, but write the prose to be readable without link context. This means explaining concepts inline rather than relying on a link to a connected note.
Avoid Obsidian-specific callout types in export notes. If you want to highlight a key insight or warning in a note that will be shared, use standard markdown: bold text, a standalone paragraph, or a blockquote without the [!TYPE] identifier. These all convert cleanly and look professional in PDF.
Keep frontmatter minimal. MarkdownTools strips frontmatter automatically, so it does not affect your PDF. But if you have complex nested frontmatter with Obsidian-specific properties, it is worth keeping export-intended notes clean so you can visually confirm where the frontmatter ends and the content begins.
Everything you need to know.
Obsidian's native PDF export renders your note using your current vault theme — which is designed for screen use, not print or PDF. The result is often low-contrast, depends on your color scheme, and lacks the typographic polish of a purpose-built PDF export. There is no built-in option to apply a print-optimized theme for the PDF specifically, and no way to control page margins or font size for the export without editing CSS directly. MarkdownTools uses professionally designed print themes that are tuned for PDF output, not screen rendering.
Paste it. Pick a theme. Download. No signup, no vault access needed, no cost.