> ## Documentation Index
> Fetch the complete documentation index at: https://filla.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Page visibility

> Skip or show entire form pages based on answers from earlier pages.

## What page visibility does

Page visibility lets you skip an entire form page based on answers the respondent gave on a previous page. When a page's conditions evaluate to true, that page is skipped and respondents jump directly to the next visible page.

This is different from field-level display conditions, which hide individual fields. Page visibility removes an entire page from the flow.

## When to use it

* Show a "Business details" page only to respondents who identified themselves as a company
* Skip a "Spouse information" page for respondents who are single
* Show a "Medical history" page only if the respondent selected a specific condition
* Route respondents through different page sequences based on their first-page answers

## Setting up page visibility

<Steps>
  <Step title="Select the page">
    Click the page tab in the page navigation panel to open the page settings.
  </Step>

  <Step title="Find the Page Visibility section">
    In the right-hand settings panel, look for the **Page Visibility** section.
  </Step>

  <Step title="Choose the visibility mode">
    You'll see two options:

    * **Always show this page**: the default, every respondent sees this page
    * **Only show this page when...**: the page only appears when conditions are met
  </Step>

  <Step title="Add conditions">
    Select **Only show this page when...** and build your conditions using the filter builder.
  </Step>
</Steps>

## How skipped pages work

When a page is skipped:

* The respondent does not see it and does not need to fill it in
* Required fields on that page are not validated
* Any values from that page are not submitted

The progress indicator updates to reflect the reduced number of steps.

## Using multiple conditional pages

You can set up complex branching flows by making multiple pages conditional. For example:

* Page 2: Show only when "Type" is "Individual"
* Page 3: Show only when "Type" is "Business"

Respondents who pick "Individual" see page 2 and skip page 3. Respondents who pick "Business" see page 3 and skip page 2.

<Tip>
  Build your page flow on paper first when logic is complex. Map out which answers lead to which pages before setting up conditions.
</Tip>

## Common questions

<AccordionGroup>
  <Accordion title="Can conditions reference fields from the current page?">
    No. Page visibility conditions can only reference fields from pages that come before the current page. You cannot use a condition that depends on a field on the same page.
  </Accordion>

  <Accordion title="What happens to required fields on a skipped page?">
    Required checks on skipped pages are bypassed. The respondent is never blocked by a required field they can't see.
  </Accordion>

  <Accordion title="Can I have a page that's always the last page regardless of branching?">
    Yes. Place the Thank You page at the end. It is always the final page, and all conditional branches ultimately lead to the Thank You page.
  </Accordion>

  <Accordion title="Is there a limit to how many conditional pages I can have?">
    No limit. You can make every page conditional if needed.
  </Accordion>
</AccordionGroup>