> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dforms/builder/create-a-form.md).

# Create a form

Create a new dForms form from the Forms page: name it, choose between the Slides and One page layouts, start from scratch or from a template, and duplicate, move or delete forms from the list.

Every form starts from the **Forms** page. You give it a name, pick how questions are shown, and then either start with a blank canvas or load one of four ready-made templates that you can edit live.

***

**Step 1:** Sign in at [app.dforms.ai](https://app.dforms.ai), open **Forms** in the left menu and click **Create form** in the top right corner.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-5d2189bc1b32bebcf7670bc1f91b0fc86165220e%2Fforms-create-a-form-01-create-button.png?alt=media" alt="The Forms page with the New folder and Create form buttons in the top right corner, Create form highlighted"><figcaption><p>Your forms are listed here. <strong>Create form</strong> opens the new form dialog.</p></figcaption></figure>

***

**Step 2:** In the **Create a new form** dialog, type a **Form name**, choose a **Folder** if your workspace uses folders, and pick a **Layout**. Click **Create form**.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-46c04971ebca78f6d3b5dd5192872af07eec45c4%2Fforms-create-a-form-02-dialog.png?alt=media" alt="Create a new form dialog with the Form name field, the Folder select and the Slides and One page layout cards"><figcaption><p>The name is required (<strong>Give your form a name.</strong> appears if you leave it empty). The layout can be changed later.</p></figcaption></figure>

| Layout       | What respondents see                                                                                                                                                                                                                                                |
| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Slides**   | One screen at a time: one question per screen, or several questions you group on the same screen. Respondents move with **Next**, a single choice question that is alone on its screen advances on tap, and the progress bar fills as they go. This is the default. |
| **One page** | All questions on a single page, one **Submit**. The whole form is visible at once and is validated when the respondent submits.                                                                                                                                     |

The form name is internal: it is what you see in the Forms list and in the editor topbar. When you create the form, the name also becomes the last part of its public link (`Lead qualification quiz` becomes `lead-qualification-quiz`, with `-2`, `-3` and so on added when another form in the workspace already uses it). You can rename the form at any time by clicking its name in the editor topbar; that never changes the link. To change the link, use **Edit link** next to **Copy link** in the editor topbar.

A new form starts in the language you use dForms in, so its buttons and messages appear in that language. Change it, or let it follow each visitor's browser, in **Design → Language**. See [Language & button text](/dforms/design/language-and-button-text.md).

> **💡 Tip:** You can switch between **Slides** and **One page** later from **Design → Layout**. Read [One-page layout](/dforms/builder/one-page-layout.md) to see what changes when every question sits on a single page.

***

**Step 3:** The editor opens on the empty state **Let's build your form**. Choose how you want to begin:

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-3764f8b256be30f1aac3f013011844519381d860%2Fforms-create-a-form-03-empty-state.png?alt=media" alt="The editor empty state with the Start from scratch card and the four templates Lead qualifier, Contact form, Feedback survey and RSVP"><figcaption><p>Start blank, or pick a template and edit it live.</p></figcaption></figure>

* **Start from scratch** opens the **Add a question** gallery so you can drop in your first question. See [Question types](/dforms/builder/question-types.md).
* **Or choose a template** loads a complete form you can edit right away:

| Template            | What it contains                                                                        |
| ------------------- | --------------------------------------------------------------------------------------- |
| **Lead qualifier**  | 6 questions · scoring · logic. Scores prospects and routes hot leads to a booking link. |
| **Contact form**    | 3 questions · no scoring. Name, email and a message, sent to your inbox or CRM.         |
| **Feedback survey** | 4 questions · scale. A rating scale plus open comments to gauge satisfaction.           |
| **RSVP**            | 4 questions · logic. Collects attendance, headcount and dietary notes for an event.     |

Templates are a starting point, not a lock-in: every question, option, point value and rule they bring can be edited or deleted like anything you add yourself.

***

**Step 4:** Build, preview and publish. Your questions are not public until you click **Publish** in the topbar; until the first publish, the form's link shows an empty page. Your edits are saved automatically all along: the status pill next to the form name reads **Draft** while the form still has no questions, and **Saved** from the first question onwards. See [Building Forms](/dforms/builder.md) for the editor tour and [Autosave, drafts & publishing](/dforms/builder/autosave-and-publishing.md).

***

## Duplicate, move or delete a form

Back on the **Forms** page, each row has quick actions (**Edit**, **Submissions**, **Analytics**, **Connect**, **Copy link**, **Open form**) and a **⋮** menu on the far right with **Duplicate**, **Move to folder** (when the workspace has folders) and **Delete**:

* **Duplicate** creates a copy named `{name} (copy)` in the same folder. It is built from the original's published version: the same questions, logic, design and settings as the live form. Edits the original has not published yet are not copied, and neither are submissions. The copy gets its own link and answers at it right away; edit it and **Publish** it when it is ready.
* **Move to folder** files the form in one of your folders, or back to **No folder**.
* **Delete** asks **Delete this form and all its submissions?** and, if you confirm, removes the form together with its submissions, analytics events, bookings and per-form notification settings. There is no undo.

> **⚠️ Note:** There is no "unpublish" action. If a form must stop accepting answers, delete it, or remove the link from wherever you shared it.

## What's next

* [Building Forms](/dforms/builder.md): a tour of the editor.
* [Question types](/dforms/builder/question-types.md): the 14 question tiles and how to add them.
* [Preview on desktop, tablet and mobile](/dforms/builder/preview.md): check the form before you publish.


---

# 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://docs.dapta.ai/dforms/builder/create-a-form.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.