FIELDS

Page Break field

Split Logical Forms into steps with Pro Page Breaks, set page titles and navigation labels, and distinguish page visibility from Next-button rules.

2 min read · Updated November 19, 2026

Use Page Break to begin another step in a Pro form. It is a full-row layout marker, not an answer. The questions after it belong to the following page until another page marker.

Availability: Pro.

Add and configure the field

  1. Open the form in Build and add Page Break from Add fields.
  2. Select its canvas card to open Field options, then configure the controls below.
  3. Save the form and check its saved Preview and embedded page.

Field-specific settings

Setting What it does
Following page title Following page title identifies the page that starts after this break.
Next button text Next button text belongs to the button before this break. Leave blank to use the form default.
Previous button text Previous button text overrides the following page's back button. Leave blank to use the form default.
Page CSS classes Page CSS classes apply to the page wrapper.
Next button conditional logic Next button conditional logic independently controls navigation forward. It does not hide a page or remove its answers.

Applicable shared options

Answers and behavior

The builder's first-page header owns the shared Pagination settings. Select it for the first page title and overall progress/navigation choices. See multi-page forms for the complete workflow.

The Page Break's ordinary conditional logic controls whether its following page applies. That differs from its Next button rule: hiding or preventing Next can strand visitors if no valid route remains. Test every branch. Conditions cannot use ambiguous repeated child values or calculated Number fields as navigation sources.

Moving a break changes which questions are on each page. Next validates the current page according to the selected submission mode; final Submit performs complete server validation. Moving through steps does not create partial entries or a save-and-return session.

Example and checks

Put contact details on page one, add a Page Break titled Project details, then add a Review Answers step near the end. Give button overrides only where the default Next and Previous labels need clarification.

Check forward and back navigation, required answers, errors, phone layout and all conditional paths. When using CAPTCHA, keep it on the final unconditional page.

Use the testing checklist to check validation and the saved entry. Explore all fields provides live examples.