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

# Document types

> The difference between a Standard and a Dynamic document, and which one to choose when you add a file.

**Add a document** ("Choose how you'd like to add your document.") offers two ways in: **Standard** and **Dynamic**. The choice decides what happens to the file after you pick it, and it is made per document, so one package or template can hold both.

|                | Standard                                             | Dynamic                              |
| -------------- | ---------------------------------------------------- | ------------------------------------ |
| Accepts        | PDF, DOC, DOCX, XLS, XLSX, PPT, PPTX, PNG, JPG, TIFF | `.docx` only                         |
| The file is    | flattened to a PDF for signing                       | kept as Word content you can edit    |
| Wording        | fixed, exactly as you uploaded it                    | can change from one send to the next |
| Signing fields | placed on the page                                   | placed on the page                   |
| Release label  | none                                                 | **Experimental**                     |

## Standard

A **Standard** document ("Upload a file as-is and place fields on it.") is the common case. The file goes up as you uploaded it and is flattened to a PDF for signing, and you place fields on the page from there.

Accepted formats are PDF, Word (`.doc`, `.docx`), Excel (`.xls`, `.xlsx`), PowerPoint (`.ppt`, `.pptx`) and images (`.png`, `.jpg`, `.jpeg`, `.tiff`). Anything that is not already a PDF is converted to one before signing.

Choose Standard when:

* The document is already written and you only need signatures, dates or a few typed answers on it.
* The wording is the same for everyone who receives it.
* The file is not a `.docx` at all.

Fields go on in the [fields editor](/guides/packages/fields-editor): signature, initials, date, text, checkbox, dropdown and the rest.

## Dynamic

A **Dynamic** document ("Use a .docx file that adapts to each send.") keeps the Word content rather than flattening it, so the wording can change from one send to the next. It opens in the **Dynamic document editor**, where you set up two things:

* **Variables**, the placeholders in the text. Each one is filled from a merge field: a value you type when sending, a value that is always the same, or a recipient's name or email for a given role.
* **Logic**, the rules over **marked content**. A question answered at send time can show a passage, hide it, or swap it for another version.

When you send, you fill the merge fields and answer the questions once, and the document is produced from those answers for that send. Everyone on that package receives the same produced document.

Choose Dynamic when:

* The document is a `.docx` and parts of its wording change each time you send it.
* You keep sending the same agreement with different names, dates or clauses.
* You want those variations held in a [template](/guides/templates/template-builder) rather than in separate files.

<Note>
  Dynamic documents are labelled **Experimental**, so how they work may change as we improve them. See [Release labels](/release-labels). They also need a plan that includes **Dynamic documents**.
</Note>

## Which to choose

If the file is not a `.docx`, the choice is made for you: it is Standard. If it is a `.docx` and the wording never changes, Standard is still the simpler route. Reach for Dynamic when the text itself has to differ between sends.

The choice is per document. Both kinds sit in the same document list, and a Dynamic one carries a **Dynamic** badge so you can tell them apart later.

## Related

* [Create a package](/guides/packages/create-package)
* [Template builder](/guides/templates/template-builder)
* [Fields editor](/guides/packages/fields-editor)
* [Release labels](/release-labels)