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

# Text fields

> Single line text, multiline text, and rich text fields on Filla forms.

## What these fields do

Text fields let respondents enter freeform written content. Filla supports three text field types that map directly to their Airtable equivalents:

* **Single line text**: a one-line input, best for short answers like names, IDs, or short labels
* **Multiline text**: a resizable textarea for longer answers like descriptions or notes
* **Rich text**: a full WYSIWYG editor with formatting options (bold, italic, headings, lists, links)

## Settings reference

All three field types share the following settings.

### Universal settings

See [Labels and descriptions](/docs/field-settings/labels-and-descriptions), [Required fields and validation](/docs/field-settings/required-fields-and-validation), [Default values and prefilling](/docs/field-settings/default-values-and-prefilling), [Conditional visibility](/docs/field-settings/conditional-visibility), and [Conditional read-only](/docs/field-settings/conditional-read-only) for settings that apply to every field type.

### Single line text settings

| Setting                   | Description                                                                                                                            |
| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| **Placeholder text**      | Hint text shown inside the input when it's empty. Supports `@` variable references to personalize the hint.                            |
| **Default value**         | Pre-filled value when the form loads. Supports `@` variable references.                                                                |
| **Hide typed characters** | Characters appear as dots (like a password field). Use this for PINs, access codes, or reference IDs you don't want visible on screen. |
| **Address autocomplete**  | Show Google Maps address suggestions as the respondent types. See [Address autocomplete](/docs/field-settings/address-autocomplete).        |
| **Minimum characters**    | The minimum number of characters required before the field is considered valid.                                                        |
| **Maximum characters**    | The maximum number of characters allowed. The form blocks input beyond this limit.                                                     |

### Multiline text settings

| Setting                  | Description                                                                            |
| ------------------------ | -------------------------------------------------------------------------------------- |
| **Placeholder text**     | Hint text shown inside the textarea when it's empty. Supports `@` variable references. |
| **Default value**        | Pre-filled value when the form loads. Supports `@` variable references.                |
| **Address autocomplete** | Show Google Maps address suggestions as the respondent types.                          |
| **Minimum characters**   | Minimum character count required.                                                      |
| **Maximum characters**   | Maximum character count allowed.                                                       |

### Rich text settings

| Setting                | Description                                        |
| ---------------------- | -------------------------------------------------- |
| **Placeholder text**   | Hint text shown inside the editor when it's empty. |
| **Default value**      | Pre-filled value when the form loads.              |
| **Minimum characters** | Minimum character count required.                  |
| **Maximum characters** | Maximum character count allowed.                   |

## Common questions

<AccordionGroup>
  <Accordion title="When should I use single line vs multiline vs rich text?">
    Use **single line text** for short, structured answers (names, codes, titles). Use **multiline text** when you expect longer free-form responses but plain text is fine (feedback, descriptions, addresses). Use **rich text** when you want respondents to format their content with headings, lists, or links, for example a blog post body or a detailed proposal.
  </Accordion>

  <Accordion title="Can I use the same field for address entry?">
    Yes. Enable **Address autocomplete** on a single line text or multiline text field. As the respondent types, Google Maps suggestions appear as a dropdown. Selecting one fills the field with the formatted address.
  </Accordion>

  <Accordion title="What does 'hide typed characters' do?">
    It renders the input as a password field. Typed characters show as dots. Use this when you want respondents to enter a value (like an ID or code) without it being visible on screen. The value is stored normally in Airtable.
  </Accordion>

  <Accordion title="Can I reference earlier answers in a text field's default value?">
    Yes. In the **Default value** setting, type `@` to open the variable picker and select any field from the form. The default value resolves dynamically when the form loads.
  </Accordion>
</AccordionGroup>