Skip to main content

Page Break Logic

Understand how GetAccept determines page breaks in the Editor, how block structure affects layout, and how to design content for consistent PDF output.

Updated this week

The GetAccept Editor automatically manages page breaks to ensure your document displays cleanly when exported, printed, or viewed as a PDF. Page breaks depend on the structure of your content, the size of each Editor block, and how elements are arranged within those blocks. Understanding how page breaks behave helps you design documents that look consistent and professional across devices and formats.


1. How Page Breaks Are Determined

Block-based layout

The Editor uses a block system.
Each Editor block is treated as a single content unit, and the PDF engine will keep the entire block together whenever possible.

This means:

  • Blocks try not to split across pages

  • If a block is too tall, it will move to the next page

  • Content inside the block flows vertically based on the elements you add


2. Internal Element Flow

Inside a block, page breaks depend on element stacking:

  • Text, images, tables, and pricing tables stack in the order added

  • Large images or long tables increase block height

  • Columns are calculated as a single structure, so they move together to the next page

Important:
Blocks do not split mid-column. The entire column layout stays intact.


3. When a Block Forces a Page Break

A block will automatically push to the next page when:

  • Its total height exceeds the remaining space on the page

  • It contains large media (full-width images, tables, pricing tables)

  • Column structures can't fit in the available space

  • Elements within the block require more vertical room than what's left on the page

The Editor ensures your document does not break mid-element for readability and stability.


4. Elements That Influence Page Breaks Most

Large images

Tall images increase the total block height and can move an entire block to the next page.

Tables & pricing tables

Because they must remain intact, long tables often shift the entire block to a new page.

Multi-column layouts

A column layout is treated as one piece, so it either fits fully or moves.

Nested lists or long text sections

If text grows beyond the page, the block shifts to the next page.


5. Best Practices to Control Page Break Behavior

  • Use multiple smaller blocks instead of one large block

  • Place long content such as pricing tables or large images in their own block

  • Avoid mixing large images and long text in the same block if layout stability is important

  • Break up sections into logical blocks to improve control and predictability

  • For consistent formatting, keep similar content grouped in similar block sizes

These practices give you much more influence over where natural breaks occur.


6. Understanding Why Page Breaks Cannot Be Manually Placed

The Editor is designed for flexible digital documents rather than rigid print layout.
Because recipients primarily view documents online, GetAccept optimizes for:

  • Responsive digital rendering

  • Content stability

  • Clean PDF exports

Manual page breaks could interfere with these behaviors, which is why the Editor relies on structural logic instead.


Summary

Page breaks in GetAccept are managed automatically based on:

  • Block size

  • Element height

  • Column structures

  • Layout flow

By structuring your content into clear, purposeful blocks, you maintain predictable and professional page transitions both online and in exported PDFs.

Did this answer your question?