Skip to main content

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.

Form pages are the core building blocks of your form. Each form page holds a set of fields that respondents fill out. You can have as many form pages as you need.

When to use multiple form pages

  • Break a long form into logical steps (e.g., “Contact info” then “Project details”)
  • Show different pages to different respondents using page visibility conditions
  • Reduce cognitive load so respondents focus on one topic at a time

Settings

SettingTypeDescription
TitleTextHeading shown at the top of the page (used in the editor page tabs)
DescriptionTextOptional text below the title to give context
Show title on formToggleDisplay the page title and description to respondents. Off by default — page titles are editor-only unless you enable this.
Display conditionsFilter builderWhen set, the page is only shown if the conditions are met. If not met, the page is skipped automatically. See page visibility.
Use a text block widget instead of the page title for richer page introductions with formatting, links, and variable references.

What you can put on a form page

  • Any Airtable field type (text, numbers, selects, dates, attachments, linked records, etc.)
  • Any widget (sections, text blocks, images, embeds, signatures, etc.)
  • Fields and widgets can be arranged in rows and columns by dragging them in the editor

Progress indicator

When your form has multiple pages, respondents see a progress bar showing how many pages they’ve completed. Pages that are skipped via display conditions don’t count toward the total.
Keep each page focused on one topic. Forms with 3-5 fields per page have higher completion rates than forms that pack everything onto one page.