Notion export not working? Fix stuck exports, failed downloads, and PDF page break issues

TL;DR If your Notion export is stuck, it is usually a client-side memory timeout or a server queue failure. For fast fixes, switch from the desktop app to a Chrome/Edge browser, clear your cache to reset the JS trigger, and export smaller nested pages rather than the full workspace. If your issue is broken PDF page breaks, bypass native export entirely: export to HTML first, then add explicit page breaks in Google Docs or Word.

Diagnostic Decision Tree (Probability & Fastest Fix)

Stop guessing and use this probability-based diagnostic tree to find your exact fix based on the failure mechanism.

Symptom 1: The export button clicks, but stays on "Preparing" forever.

• Probability: Very High (40% of failures — community-reported estimate)
• Mechanism: Client-side JavaScript failed to communicate with Notion's server queue, or the browser cache is corrupted.
• Fastest Fix: Hard refresh (Ctrl+F5) -> Clear Page Cache -> Switch to Web Browser.

Symptom 2: The progress bar starts, but silently crashes or throws an error.

• Probability: High (35% of failures — community-reported estimate)
• Mechanism: The server timed out generating the ZIP file. Notion's internal timeout thresholds are undisclosed, but community reports suggest exports with large media libraries or deep relational database loops are most likely to hit this limit.
• Fastest Fix: Chunking. Isolate the largest databases or media galleries and export them individually.

Symptom 3: The PDF downloads, but tables split and headings are orphaned.

• Probability: Extremely High (Layout Issue)
• Mechanism: Notion's PDF engine treats content as a fluid web canvas, not physical paper. It lacks strict pagination logic.
• Fastest Fix: Export as HTML -> Open in Word/Docs -> Insert manual page breaks (Ctrl+Enter).

Symptom 4: The "Export" option is completely missing from the menu.

• Probability: Low (Usually Enterprise users)
• Mechanism: Workspace admin has toggled off "Allow Export" in security settings, or you are logged into a guest account via SSO. Enterprise deployments may also encounter SCIM-provisioned role limitations or workspace-level vs. page-level permission inheritance conflicts that block export for specific accounts without surfacing a clear error.
• Fastest Fix: Verify permissions in Settings & members -> Security & Data. If you are on an Enterprise plan, confirm with your workspace admin whether export restrictions are applied at the workspace level, the team space level, or the individual role level.

Error Message Reference

If you are seeing a specific error string, use this table to map it to the likely failure mechanism and fix.

The Mechanics of Failure: Why Notion Exports Break

Understanding how Notion exports your data is critical to fixing it when it fails.

When you click "Export," your local client sends a request to Notion's AWS-hosted backend. The server must traverse your workspace, resolve every relational database link, fetch embedded media, compile it into Markdown/CSV/HTML, compress it into a ZIP, and send it back.

According to consistent reports across r/Notion and official documentation, this process breaks at three primary choke points:

1. Electron App Memory Limits (Client-Side): The Notion desktop app is built on Electron. During massive exports, the local app may exhaust available memory and silently crash before the server finishes — a behavior consistent with how Electron applications handle large heap allocations, though Notion has not publicly documented a specific threshold. This is why switching to a dedicated browser like Chrome or Edge often resolves "stuck" exports.
2. Server-Side Timeouts: Notion's servers queue export jobs. If your workspace contains large uploaded files or deeply nested relational databases, the server compilation time can exceed Notion's internal timeout thresholds. Notion has not publicly disclosed these thresholds; the limits described here are based on community-reported patterns, not official documentation.
3. Cache Corruption: Stale browser cookies or cached scripts can break the initial JavaScript trigger, causing the "Preparing..." infinite loop.

High-Probability Troubleshooting Steps

! notion-export-menu-desktop

Fix 1: The Client Swap (Bypass App Memory Limits)

Because the desktop app and web browsers handle memory allocation differently, swapping clients is the highest-leverage fix.

1. If the desktop app fails, log into Notion via Google Chrome or Edge.
2. If the browser fails, try the desktop app.

Fix 2: Reset the Trigger (Clear Cache)

! notion-clear-cache

If the export is stuck on "Preparing," the server likely never received your request.

1. Desktop App: Click the ? icon in the bottom right -> Select Clear Page Cache.
2. Browser: Clear your site cookies, or attempt the export in a fresh Incognito/Private window to bypass conflicting extensions (like ad-blockers preventing popup downloads).

Fix 3: Circumvent Network Routing Issues

If your export compiles but the ZIP file download repeatedly fails midway, the issue is local network routing. Disabling enterprise VPNs or custom DNS firewalls prevents them from aggressively terminating the large file transfer.

Fix 4: Chunking (Bypass Server Timeouts)

If you have a massive, media-heavy workspace, a single "Export All" command will likely fail.

1. Navigate to your largest individual pages or databases.
2. Export them one by one.
3. Edge Case Note: If a specific database repeatedly fails, temporarily remove large file attachments from the rows, export the CSV, and download the media manually.

PDF Page Breaks: Mechanisms and Workarounds

Notion's native PDF export is notorious for awkward page breaks—splitting tables horizontally, leaving headings stranded at the bottom of pages, and creating unpredictable margins.

The Tradeoff: Notion is optimized for block-based digital rendering, not physical pagination. Unlike Google Docs or Microsoft Word, which render data onto a fixed physical page layout in real-time, Notion blindly slices its fluid web canvas into A4/Letter dimensions during the export phase.

To achieve professional formatting, you must rely on workarounds.

Workaround 1: HTML to Word (The Definitive Fix)

Consensus from community troubleshooting confirms that the only way to get perfect PDF page breaks is to stop using Notion's PDF engine.

1. Export the specific Notion page as HTML.
2. Open the resulting .html file in Microsoft Word or Google Docs.
3. The structural formatting (headings, tables, bold text) will be perfectly preserved.
4. Insert explicit page breaks (Ctrl + Enter) exactly where you need them.
5. Export as a polished PDF from Word/Docs.

Workaround 2: In-App Spacing Hacks

If you must use native export, you can attempt to force breaks visually:

• The Divider Hack: Type --- to insert a horizontal rule before major headings. Notion's PDF engine tries to avoid splitting content immediately after a divider.
• Blank Blocks: Press Enter multiple times to push a stranded heading down to the next page. Note: This requires trial and error with the export scale percentage.

Edge Cases: Filtered & Relational Database Errors

If your database export completes, but the CSV looks incomplete or broken, you have likely hit a view or relationship error.

• The Filtered View Illusion: According to Notion's documentation, exporting a database inherently exports the current active view. If you have a filter applied (e.g., "Status = To Do"), your CSV will permanently exclude all other data. Ensure you select a view with zero filters before exporting.
• Relational ID Dumps: When exporting relational databases, Notion cannot natively nest CSVs. Instead of plain text names, it will export raw, alphanumeric internal IDs for linked pages. You must create a formula column (prop("Name")) to extract the readable text prior to exporting.
• Page Table vs. Database Block: Ensure you are exporting the full database page, not just a simple linked database view embedded inside a standard page.

Export Method Comparison: Native Export vs. Notion API vs. Third-Party Tools

If native exports keep failing, you have two other paths before escalating to a full migration service. Here is how they compare:

The Notion API is the most reliable path for developers dealing with repeated native export failures. It paginates responses, avoids the ZIP compilation bottleneck entirely, and lets you handle media and relations programmatically. The official endpoint documentation is at developers.notion.com.

Scaling Up: When to Abandon Native Exports for Custom Integrations

If you are a solo user, the troubleshooting steps above will eventually force your export through. However, if you are an enterprise team dealing with continuous timeouts, missing SSO permissions, and the nightmare of mapping raw alphanumeric relational IDs back together, native ZIP exports are no longer viable.

At that scale, the options are: use the Notion API directly, integrate a third-party sync tool, or bring in a migration service if you are moving data to a new platform entirely.

Sources & References

• Notion Help Center: Export your content
• Notion Help Center: Troubleshooting & Error Messages
• Notion API Reference: Get block children
• r/Notion Community Troubleshooting: Export Isn't Working
• r/Notion Guide: How to Properly Export Notion to PDF
• r/Notion Discussions: PDF Page Break Fixes