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

# Screens

> Welcome, Statement, and End screens — their purpose and configuration options.

Screens are nodes that display content to respondents without collecting an answer. There are three screen types: **Welcome**, **Statement**, and **End**. Every form must have at least one Welcome and at least one End.

***

## Welcome

The Welcome screen is the entry point of your form — the first thing respondents see when they open the link. It sets context and invites them to start.

<img src="https://mintlify.s3.us-west-1.amazonaws.com/feedal/images/building-forms-screens-welcome.png" alt="A Welcome screen in the canvas" />

**Configuration options:**

| Field          | Type      | Default | Notes                              |
| -------------- | --------- | ------- | ---------------------------------- |
| `title`        | Text      | —       | Edited directly in the canvas      |
| `description`  | Rich text | —       | Optional; supports formatting      |
| `image_url`    | Image     | —       | Banner image shown above the title |
| `button_label` | Text      | `Start` | Label on the "begin" button        |

<Note>
  A form can have multiple Welcome screens, but only one can be set as the
  **entry node** — the one respondents land on first. You set this in the right
  panel with "Set as entry".
</Note>

***

## Statement

A Statement is an informational screen that can appear anywhere in the flow. Use it to give instructions, show a section header, or provide context between questions. Respondents click a button to continue — no answer is collected.

**Configuration options:**

| Field          | Type      | Default | Notes                         |
| -------------- | --------- | ------- | ----------------------------- |
| `title`        | Text      | —       | Edited directly in the canvas |
| `description`  | Rich text | —       | Optional                      |
| `image_url`    | Image     | —       | Optional banner image         |
| `button_label` | Text      | —       | Label on the continue button  |

***

## End

The End screen is the final node in a form's path. When a respondent reaches it, their session is marked **completed**. There are two modes:

### Screen mode (default)

Displays a thank-you message. Respondents stay on the page.

| Field          | Type                   | Default  | Notes                                |
| -------------- | ---------------------- | -------- | ------------------------------------ |
| `title`        | Text                   | —        | Edited directly in the canvas        |
| `description`  | Rich text              | —        | Optional closing message             |
| `image_url`    | Image                  | —        | Optional banner image                |
| `button_label` | Text                   | `Submit` | Button label shown on the end screen |
| `mode`         | `screen` \| `redirect` | `screen` | Controls end-screen behavior         |

### Redirect mode

Immediately redirects the respondent to a URL when they reach this node. The thank-you screen is not shown.

| Field          | Type                   | Default  | Notes                         |
| -------------- | ---------------------- | -------- | ----------------------------- |
| `mode`         | `screen` \| `redirect` | `screen` | Set to `redirect` to enable   |
| `redirect_url` | URL                    | —        | Full URL including `https://` |

<Warning>
  When using redirect mode, make sure the `redirect_url` is reachable and does
  not require authentication the respondent might not have.
</Warning>

### The fallback end node

Every form has one designated **fallback end node**. If the engine evaluates all outgoing edges from a question and none of their conditions match, it falls back to this node. You set the fallback in the right panel using "Set as fallback end". A form can have multiple End nodes — for example, one for each branch in a conditional flow.

***

## Common fields

All screen types (and question nodes) share a set of common fields. See [Common fields](/building-forms/content/common-fields) for details on title, description, image, and entry/fallback pointers.

***

## Next steps

<CardGroup cols={2}>
  <Card title="Common fields" icon="square-list" href="/building-forms/content/common-fields">
    Title, description, image, and the required toggle.
  </Card>

  <Card title="Conditional branching" icon="code-branch" href="/building-forms/workflow/branching">
    Route respondents to different End screens based on their answers.
  </Card>
</CardGroup>