Notion has a built-in PDF export. It works, but it produces a plain document with no theme control, no typography options, and an output that looks like every other Notion export. The markdown export workflow gives you a professionally designed PDF in 60 seconds.
Notion's native export gets your content out as a PDF. It does not give you any control over how that PDF looks. There are no theme options, no typography settings, no way to apply visual identity, and the output looks like a Notion export regardless of the content or audience.
The markdown export path fixes this. Notion produces excellent markdown — the heading hierarchy, table syntax, and code block formatting all translate correctly. Route that markdown through MarkdownTools and you get theme control, professional typography, and a PDF that looks designed.
No theme control
Built-in export looks identical every time
No font options
Fixed Notion typography, no customization
No design identity
Outputs signal "Notion export" not "our doc"
Notion markdown export — typical output
# Project Kickoff — Q3 Initiative ## Goals Complete the **authentication redesign** by end of quarter. Three parallel workstreams: | Workstream | Owner | Due | |-----------|-------|-----| | Backend API | Dana | Aug 15 | | Frontend | Lee | Aug 22 | | QA | Mika | Aug 29 | ## Notes > Key constraint: zero downtime deployment > required for all production changes. ```bash # Run migration dry-run first ./scripts/migrate.sh --dry-run ```
Use Workflow A for most pages. Use Workflow B for simple pages when you want to skip the file download.
Best for: pages with tables, code blocks, callouts, or complex formatting.
Best for: simple pages with text, headings, and basic bullets. May need light cleanup for complex formatting.
Workflow A in detail — the markdown file export path.
Open the Notion page. Click the three-dot menu (top right) and select Export. Choose "Markdown & CSV" as the format. Notion downloads a zip file containing a .md file for each page and .csv files for any inline databases. Unzip it and open the .md file in any text editor. About 20 seconds.
Select all the content in the .md file (Cmd+A) and copy it. Notion's markdown export is clean for standard page content — headings, paragraphs, bullets, and tables all translate correctly. You may see some Notion-specific syntax for callouts or toggles that needs a quick cleanup, covered below. 5 seconds.
Open MarkdownTools and paste into the editor. The preview panel shows the rendered output immediately. Pick a theme: Clean for technical docs and wikis, Classic for meeting notes and reports, Elegant for client-facing proposals. The live preview updates as you switch themes. 20 seconds.
Click the PDF button. A professionally formatted PDF is generated server-side using Chromium and downloads to your device in under a second. Your content is never stored. 5 seconds.
Standard Notion content is ready to go. Some block types need a quick adjustment.
Converts cleanly — no prep needed
Headings (H1, H2, H3)
Full hierarchy preserved
Paragraphs and inline formatting
Bold, italic, inline code
Bulleted and numbered lists
Including nested lists
Tables
Up to 5–6 columns; wider tables need splitting
Code blocks
Language tag preserved if set in Notion
Checkboxes
Render as checked/unchecked items
Dividers
Export as horizontal rules
Links
URLs preserved and clickable in PDF
Needs light prep before export
Callout blocks
Export as blockquotes. Icon is lost — add a text label ("Note:", "Warning:") if the icon carried meaning.
Toggle blocks
Content exports fully expanded. Review that expanded content reads logically in a linear format.
Images
Export to separate files with relative paths. Images will not render if you paste only the markdown text. Delete broken image references or re-add via URL.
Databases / inline tables
Export as separate CSV files — not as page content. Paste small datasets as a markdown table manually.
Synced blocks
Export content at the time of export. Sync relationship is not preserved. For archiving, this is usually correct behavior.
Any page you would normally email as a Notion link but the recipient does not have access — or does not want to open Notion.
Notion is a common home for project specs, PRDs, and technical design documents. When you need to share a spec with stakeholders outside your Notion workspace — a client, an investor, or a team member without Notion access — exporting as a themed PDF takes 60 seconds and produces a document that looks intentional, not like a raw export.
Meeting notes in Notion typically have a clean structure: date, attendees, agenda, action items. This structure translates directly to markdown. Export to PDF using the Classic theme for a clean, readable document that can be emailed to participants or archived without requiring them to have a Notion account.
Wiki pages written in Notion — onboarding guides, process documentation, runbooks — are often the kind of content that benefits from a PDF version for offline reference or printing. Pages with standard content (headings, bullets, code blocks, tables) export cleanly and render well with the Clean theme.
If your team writes proposals or status reports in Notion, the built-in PDF export does not look professional enough to send to clients. Route the markdown export through MarkdownTools with the Elegant theme and the output is a polished document that reads like it was designed, not auto-generated.
Notion personal pages — reading notes, research summaries, reference material — accumulate over time. When you need to extract a specific page for sharing or offline reading, the markdown export workflow produces a clean, self-contained PDF without requiring the recipient to access your Notion workspace.
When a team member leaves or a project transitions, documentation that lives in Notion needs to be shared in a format that does not depend on workspace access. Exporting key pages as PDF through MarkdownTools produces a permanent, readable record that does not expire when workspace permissions change.
Notion's native PDF export does one thing well: it gets the content out. What it does not do is make that content look good. The output uses Notion's default typography with no customization options — no theme selection, no font choice, no control over spacing or heading styles. The result is a document that looks unmistakably like a Notion export, which is fine for internal use but not for anything client-facing or public.
There is also no way to apply a visual identity to the export. If your company has design standards, they are not going to show up in a Notion PDF. Every export looks the same regardless of the content or the audience.
The markdown export workflow fixes both of these problems. Notion's markdown export is well-structured — it represents the same content hierarchy that the Notion editor produces. Routing that markdown through MarkdownTools gives you theme control, typography choices, and a PDF that looks like it was designed rather than auto-generated.
Standard Notion page content exports cleanly to markdown: headings (H1, H2, H3), paragraphs, bulleted and numbered lists, checkboxes, bold and italic text, inline code, fenced code blocks, tables, and images (exported as separate files with relative paths in the markdown). If your page uses these elements, the markdown export is ready to paste into MarkdownTools with no cleanup.
Notion tables export as standard markdown tables with pipe syntax. Tables with up to five or six columns render cleanly within standard page margins. Wider tables will need to be split or reformatted — the same limitation applies to any markdown-to-PDF converter, not just MarkdownTools.
Code blocks export with the language tag preserved if you specified one in Notion. If you used the generic "Code" block without selecting a language, the exported markdown will have a code block without a language identifier. You can add one manually in the MarkdownTools editor — it takes five seconds per block and enables syntax highlighting in the PDF.
Notion callout blocks export as blockquotes in markdown. They lose the icon and background color, but the content is preserved and blockquotes render with a left border in MarkdownTools, which is a reasonable substitute. If the icon was meaningful (a warning sign, for example), add a text prefix like "Note:" or "Warning:" before the blockquote content.
Toggle blocks export as the toggle heading followed by the content — the collapsed/expanded behavior is lost, but all the text is preserved. Review toggle-heavy pages after export to make sure the content is organized logically when fully expanded. You may want to add a heading before toggle content that was previously hidden under a toggle, so it does not appear mid-paragraph.
Synced blocks export the content as it appears at export time — the sync relationship is not preserved in markdown. This is expected behavior. If the synced block content changes after export, you need to re-export. For PDF archiving purposes, this is usually the correct behavior anyway.
Notion databases do not export as page content — they export as separate CSV files. The inline database view that appears on your page will be absent from the markdown export. If the database data is important, export the CSV separately and either paste it into the markdown as a table (for small datasets) or reference it as a separate attachment.
If you do not want to deal with the zip file download, there is a faster path for pages without databases or images: select all content on the Notion page (Cmd+A in the page body) and copy. Paste into a text editor to check what you have — Notion copies formatted text that is close to markdown but not identical. You may see some differences in heading syntax or list formatting that need a quick fix.
For simple pages — meeting notes, short docs, plain text with some formatting — this approach is faster than the full export workflow. For pages with tables, code blocks, or complex formatting, the markdown file export is more reliable because it uses a proper markdown serializer.
A third option for users with the Notion API access: fetch the page content programmatically using the Notion API and the notion-to-md library, which converts Notion blocks to clean markdown. This is a more robust approach for teams that regularly export Notion content, but requires technical setup that is out of scope for a one-off export.
Everything you need to know.
Not directly through this workflow. Notion databases export as CSV files, not as page content. The inline database view that appears on a Notion page does not appear in the markdown export. For small databases, you can open the CSV file, copy the data, and paste it into the MarkdownTools editor as a markdown table. For large databases, you would need to filter and export a subset, or use the Notion API to fetch the data and format it as markdown.
Export as markdown, paste, pick a theme, download. No signup, no formatting work, no cost.