> For the complete documentation index, see [llms.txt](https://help.form.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.form.io/form-building/form-types.md).

# Form Types

Understanding Web forms, Wizards, and PDF forms

Form.io offers several different options on how the form is displayed and consumed by the end-user. These different form options serve different use cases and purposes, however, the form type can be changed at any time by clicking the '**Display As**' dropdown within the Form Builder. The form type is selected when the form is created. Below are the different form options to create.

<figure><img src="https://501951130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6LdEf8SjBIeQDsRL3BdV%2Fuploads%2F2nxTCJDRStIxRJSC9aDW%2Fformcreation2.jpg?alt=media&amp;token=4e33f485-b7e4-429a-83e2-3cd215a053e4" alt=""><figcaption></figcaption></figure>

## Web Form

A traditional web form that is typically filled out by end-users from top to bottom. To create a Web Form, click the **+New Form** button and select Web Form.

## Wizard

This form configuration allows users to progress through the form in bite-size sections instead of presenting the entire form to the user. If you are creating a form containing many fields, this is a great option to improve the user experience.

To create a Wizard, select the Webform option. While in builder mode, click the **Display As** dropdown and switch the options from Webform to Wizard.

<figure><img src="https://501951130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6LdEf8SjBIeQDsRL3BdV%2Fuploads%2FuqFnZrlATodFa3KEw7CZ%2Fform3.jpg?alt=media&amp;token=77c73c43-b747-4e16-a97a-dc20d5729ada" alt=""><figcaption></figcaption></figure>

The formatting will dynamically change within the builder into a Wizard-style form. The Wizard utilizes the **Panel** layout component for the Pages. When a form is switched to a Wizard, all fields will be moved into a Panel by default representing the first page of the wizard when the form is rendered.

{% hint style="info" %}
To transfer components from one Wizard Page to another, switch the Display As mode to Webform. In doing so, the Wizard Pages will separate into individual Panels where fields can be moved to and from. Switch the form back to Wizard mode to restore the previous format.
{% endhint %}

When rendered, the Wizard introduces **Cancel, Previous** and **Next** navigation buttons at the bottom of the form. The user can progress through the Wizard or use the header tabs to navigate through the form.

<figure><img src="https://501951130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6LdEf8SjBIeQDsRL3BdV%2Fuploads%2FqZPHfIW64Al3yRtx0mvv%2Fforms4.jpg?alt=media&amp;token=a1acda89-7c3b-4258-ba25-1699bdfcc4e9" alt=""><figcaption></figcaption></figure>

## PDF Forms

PDF-First forms allow users to upload a PDF form and add overlay fields to the form, modernizing the traditional old and clunky PDF form. For a more in-depth guide on the PDF forms please navigate to the [**following documentation**](/form-building/pdf-forms.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.form.io/form-building/form-types.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.