> For the complete documentation index, see [llms.txt](https://support.pipefile.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pipefile.com/forms-and-esignature/fillable-forms.md).

# Fillable forms

Turn a PDF attachment into a form your recipients fill out in the browser, with fields you place in the form builder.

{% hint style="info" %}
Available on the **Professional** and **Enterprise** plans, and during the free trial.
{% endhint %}

A fillable form is a PDF attached to a request that your recipient completes directly on the request page. They don't need to download, print or scan anything. When they finish, Pipefile saves the completed PDF to the checklist item like any other upload.

## Create a form

{% stepper %}
{% step %}

### Attach a PDF

While creating or editing a request or template, open the checklist item that needs the form and click **Attach Files**. Choose a PDF. (On an open-ended request, attach it below the message instead.) Only PDFs can become forms.
{% endstep %}

{% step %}

### Click Create Form

Next to the attached PDF, click **Create Form**. The form builder opens, titled with the file name. If the PDF already has fillable fields, Pipefile imports them for you.
{% endstep %}

{% step %}

### Place your fields

Drag fields from the **Form Fields** panel onto the page: **Text**, **Checkbox**, **Date** or **Signature**. Drag a field to move it, and drag its edges to resize it.
{% endstep %}

{% step %}

### Set field properties and save

Click a field to open its properties (see below). When you're done, click **Save Form**.
{% endstep %}
{% endstepper %}

To change a form later, click **Edit Form** next to the attachment.

## Field types

| Field                       | How it works                                                                                                                                                                  |
| --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Text**                    | A text box. Text fields imported from a fillable PDF keep their settings: multi-line boxes, combed boxes (one character per box, like an account number), and maximum length. |
| **Checkbox**                | A box the recipient ticks.                                                                                                                                                    |
| **Date**                    | Fills in automatically with today's date when the signer finishes. The recipient doesn't type it.                                                                             |
| **Signature**               | The recipient types or draws a signature. See [E-signature](/forms-and-esignature/e-signature.md).                                                                            |
| Radio buttons and dropdowns | Imported from fillable PDFs and filled in the same way.                                                                                                                       |

## Field properties

Click any field to open its properties panel. What you see depends on the field type.

* **Required** – Block submission if the field is empty. When a recipient submits with required fields empty, Pipefile lists the ones they missed.
* **Read-only** – Prefilled and not editable. Set the text in **Default value** (or **Default checked** for a checkbox). Use this to fill in details on your side before you send.
* **Assignment** – Which recipient fills the field. Text and checkbox fields can stay **Unassigned**, which means any recipient can fill them. Signature and date fields always belong to one recipient. See [Multiple signers](/forms-and-esignature/e-signature.md#multiple-signers).
* **Signature** – For signature fields: **Type or draw**, **Draw only** or **Type only**.
* **Field name**, **Placeholder text** and **Help text** – Help text appears when the recipient hovers over the field.

To remove a field, click **Delete field** in the panel.

## Keyboard shortcuts

Hover the help icon at the top of the form builder to see the full list.

| Keys                         | Action                            |
| ---------------------------- | --------------------------------- |
| `Tab` / `Shift` + `Tab`      | Next / previous field on the page |
| `Esc`                        | Deselect field                    |
| Arrow keys                   | Move field 1px                    |
| `Shift` + arrow keys         | Move field 10px                   |
| `Cmd`/`Ctrl` + arrow keys    | Resize field                      |
| `Delete` / `Backspace`       | Delete field                      |
| `Cmd`/`Ctrl` + `D`           | Duplicate field                   |
| `Cmd`/`Ctrl` + `Z`           | Undo                              |
| `Cmd`/`Ctrl` + `Shift` + `Z` | Redo                              |

## What your recipient sees

On the request page, the attachment shows a **Fill Form** button. The recipient fills the form, then chooses **Submit Form** to send it, or **Finish Later** to save their progress and come back. Progress is saved as they go. See [Fill and sign a form](/for-your-clients/fill-and-sign-a-form.md) for their side.

If several recipients share a request, they all work on the same copy of the form. Each person's changes show up for the others as they type.

## Long answers: addendum pages

If a recipient types more into a multi-line text box than fits on the page, the box shows "Continued in addendum" with a number. The full text goes on an addendum page added to the end of the completed PDF. Single-line boxes are cut off at the edge of the box and don't get an addendum, so give fields enough room or use a multi-line box for long answers.

## Forms in templates

You can create forms on template attachments the same way. Every request sent from the template includes the form, its fields and their role assignments. See [Create and edit templates](/templates/create-and-edit-templates.md).

## Related

* [E-signature](/forms-and-esignature/e-signature.md)
* [Build your checklist](/requests/checklists-and-sections.md)
* [Plans and features](/getting-started/plans-and-features.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://support.pipefile.com/forms-and-esignature/fillable-forms.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.