> For the complete documentation index, see [llms.txt](https://docs.varbase.vardot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.varbase.vardot.com/content-designers/search-forms-and-email/webforms/create-new-webform.md).

# Create New Webform

This page shows how to create a form, from a template or from scratch, add fields, and test it before visitors use it.

## Starting From a Template

1. Go to **Structure** \ **Webforms** and open the **Templates** tab (`/admin/structure/webform/templates`).
2. Find a template, for example **Contact Us**, and click **Select**.
3. Enter the **Title** of your form, and click **Save**.

The new form has the template's fields and emails, ready to change.

## Starting From Scratch

1. Go to **Structure** \ **Webforms** and click **Add webform**.
2. Enter the **Title** and, optionally, an **Administrative description**.
3. Click **Save**.

## Adding Fields

1. On the form's **Build** tab, click **Add element**.
2. Search for or choose the field type, such as **Text field**, **Email**, **Select** or **Checkboxes**.
3. Fill in the **Title** (the label visitors see), and tick **Required** if it must be filled in.
4. Click **Save**.
5. Drag the fields into order, then click **Save elements**.

<figure><img src="https://410909369-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcuWLZ87gvtX5vA2YGD%2Fuploads%2Fgit-blob-2c87215e79b9b1717353081c22172544c780fd03%2Fwebforms-create-02-build.png?alt=media" alt="The Build tab of a webform listing its fields with drag handles, the Add element button and the Save elements button"><figcaption><p>Building the Form</p></figcaption></figure>

## Conditions and Validation

* **Conditions** show or hide a field depending on an earlier answer, so visitors see only what applies to them. Open a field's settings and use its **Conditions** tab. For example, a form can ask for a company name only when the visitor says they are writing on behalf of a business.
* **Validation** checks an answer before the form is sent, such as a valid email address, a number range or a maximum length. It is in the field's settings too.

Both make forms shorter and cleaner, and both are settings, not code.

## Main Settings

On the **Settings** tab you can change, among others:

* **General**: open or close the form.
* **Form**: the submit button label.
* **Submissions**: **Submission limit settings**, such as one submission per person for a registration or a total for an event with limited places, and **Submission purge settings**, which delete old submissions after a set number of days. Agree the period with the client and state it in the privacy notice.
* **Confirmation**: the message or page visitors see after submitting.
* **Emails / Handlers**: who is emailed. See [Setting up Email Handlers](https://docs.varbase.vardot.com/content-designers/search-forms-and-email/webforms/setting-up-email-handlers.md).
* **Access**: who may fill in the form, for example everyone or only logged-in staff, and who may see, edit or delete its submissions. An internal request form can be limited to staff while a contact form stays open to everyone.

## Testing the Form

1. Open the **Test** tab, fill in the form and submit it.
2. Check the confirmation, and the emails if any are set up.
3. Ask a **Site Admin** to check the test submission under **Results** and delete it.

## Tips

* Ask only for what you need; every extra field loses some visitors.
* Write labels as plain questions, and use **Description** for help text.
* Do not use the placeholder text as the only label; screen readers may not read it.
* Close a form when a campaign or event is over, rather than deleting it and its results.
