When you export a Notion page to PDF, the resulting document often contains unexpected page breaks that split content across pages in awkward places. This happens because Notion applies its own internal rules for where to break pages, which are different from word processors like Microsoft Word or Google Docs. Notion does not allow manual page break insertion, and the export engine uses a combination of content block types, page width settings, and font size to determine break points. This article explains exactly how Notion decides where to break pages, what settings you can adjust to control the output, and which content patterns cause the most unpredictable breaks.
Key Takeaways: Notion PDF Page Break Rules
- Settings & Members > Settings > Export > Page Size: Choosing A4 or Letter changes how many characters fit per line and shifts break points.
- Custom CSS in Export: Adding
page-break-before: alwaysto a block forces a break, but only when using the Markdown + CSS export option. - Database and Table Blocks: These always start on a new page when exported, even if the previous page has empty space.
How Notion Determines Page Breaks During PDF Export
Notion does not use a standard pagination engine like a browser’s print function. Instead, it converts the page content into an intermediate format and then applies a set of fixed rules to split the content into pages. The primary factors are the page size setting, the width of the content area, and the height of each block type.
When you export, Notion calculates the available vertical space per page based on the selected page size. It then fills that space with blocks in order. A block that does not fit entirely on the current page is moved to the next page. Notion does not split individual blocks across pages. For example, a long paragraph or a large image is moved as a whole unit to the next page if it exceeds the remaining space.
The export settings available in the dialog are limited to page size, margin size, and the option to include or exclude page numbers. There is no setting to insert a manual page break. However, you can influence breaks by changing the page size from the default Letter to A4, which is slightly taller and narrower, or by reducing margins to gain more usable space per page.
The Role of Block Types in Page Breaks
Each block type has a minimum height that affects pagination. A single line of text takes up one line height. A bulleted list with five items takes five line heights. A database or table block, regardless of its content size, always triggers a page break before it. Notion treats these blocks as separate sections that must start on a new page. This behavior is hardcoded and cannot be disabled.
Images, embeds, and code blocks also cannot be split. If an image is 800 pixels tall and the remaining space on the current page is only 600 pixels, the image moves to the next page, leaving a large blank area at the bottom of the current page. This is the most common cause of unexpected white space in exported PDFs.
Steps to Control Page Breaks in Notion PDF Exports
You cannot insert manual page breaks, but you can adjust settings and restructure content to reduce unwanted breaks. Follow these steps to gain more control over the final PDF layout.
- Change the page size before exporting
Open the page you want to export. Click the three-dot menu in the top-right corner. Select Export. In the dialog, click the Page Size dropdown. Choose A4 instead of Letter. A4 is 297 mm tall versus Letter’s 279 mm, giving you 18 mm more vertical space per page. This reduces the number of blocks that overflow to the next page. - Reduce margins to gain space
In the same Export dialog, click the Margins dropdown. Select Narrow instead of Normal. This increases the usable width and height of the content area. More text fits per line, and fewer lines are pushed to the next page. - Compact your content blocks
Before exporting, review the page for tall blocks. Replace large images with smaller versions. Convert long paragraphs into shorter ones. Collapse toggle blocks that are not essential. Each collapsed toggle reduces the vertical space used. - Move databases and tables to separate pages
Since databases always start on a new page, place them near the top of a page or on their own subpage. Export the subpage separately if you need the database to appear immediately after preceding text. - Use the Markdown + CSS export for advanced break control
If you need manual page breaks, export the page as Markdown + CSS instead of PDF. In the Export dialog, select Markdown & CSV from the Export format dropdown. This downloads a ZIP file containing the Markdown file and a CSS file. Open the CSS file in a text editor. Addpage-break-before: always;to any block selector where you want a break. Then use a tool like Pandoc or a Markdown-to-PDF converter to generate the final PDF with your custom breaks.
Common Issues and Workarounds for Page Break Problems
Large blank space appears before an image in the PDF
This happens when the image block is taller than the remaining space on the current page. Notion moves the entire image to the next page, leaving the gap. To fix this, reduce the image size before export. Click the image in Notion, drag the corner handle to make it smaller. Alternatively, move the image earlier in the page so it lands at the top of a page.
Database or table block breaks in the middle of a page
Notion always forces a page break before a database block. The preceding content may end in the middle of the page, and the database starts on the next page. To avoid this, place the database on its own subpage. Export the parent page without the database, then export the subpage separately.
Code blocks are cut off at the bottom
Code blocks have a fixed height based on the number of lines. If a code block is too tall for the page, it is moved entirely to the next page. To work around this, split the code block into two smaller code blocks using the /code command. Or reduce the font size in the code block by using a smaller code block style if available.
Header and subheader blocks cause unexpected breaks
Notion treats headings as blocks that should not be separated from their following content. If a heading is at the bottom of a page and the next paragraph would start on the next page, Notion moves the heading to the next page as well. This can create a gap. To prevent this, add a short paragraph or an empty line between the heading and the next block. This gives Notion more flexibility to keep the heading with its content.
Notion Export Page Size vs Content Fit
| Setting | Letter (Default) | A4 |
|---|---|---|
| Page dimensions | 215.9 x 279.4 mm | 210 x 297 mm |
| Usable height (Normal margins) | ~237 mm | ~257 mm |
| Usable height (Narrow margins) | ~255 mm | ~275 mm |
| Lines of text per page (approx) | 55-60 | 65-70 |
| Page break before database | Always | Always |
| Manual page break support | No | No |
The table shows that switching to A4 with narrow margins provides the most vertical space. This reduces the frequency of blocks being pushed to the next page. However, database blocks still force a break regardless of page size.
After adjusting these settings, you can produce a PDF with fewer unexpected page breaks. For complete control, use the Markdown + CSS export method and add custom page-break rules. This approach is best for users who need precise layout control, such as when generating reports or documents for print.