> For the complete documentation index, see [llms.txt](https://help.blings.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.blings.io/apps/blings-studio/connectors/input-field.md).

# Input Field

Use the Input Field connector when viewers should type text directly inside the MP5 experience. Typical uses include names, feedback, quiz answers, survey responses, preference notes, and free-text messages.

Input Field captures the typed value in the player. Use [Submit Form](/apps/blings-studio/connectors/submit-form.md) when the value should be submitted, saved, or sent to another system.

<figure><img src="/files/xD0N1YzYvk436tZOYKCZ" alt="Shared Studio connector detail panel where connector source, fallback, editing access, and internal description controls are configured" width="375"><figcaption></figcaption></figure>

## Options

| Option                   | What it controls                                           | Notes                                                                       |
| ------------------------ | ---------------------------------------------------------- | --------------------------------------------------------------------------- |
| **Input text layer**     | The text layer that becomes editable by the viewer.        | Select the visual layer where the viewer should type.                       |
| **Field name**           | The name used to identify the entered value.               | Use a stable name such as `viewer_name`, `email`, or `feedback_message`.    |
| **Placeholder**          | The prompt shown before the viewer types.                  | Keep it short and specific, such as `Type your name here`.                  |
| **Input mode**           | Whether the field accepts a single line or multiple lines. | Use single-line for short answers and multiline for longer messages.        |
| **Empty state**          | What happens when the viewer leaves the field blank.       | Decide whether empty input should be allowed before adding submit behavior. |
| **Text fit**             | How typed text fits in the input area.                     | Preview long values, multiline values, and mobile entry when relevant.      |
| **Internal description** | A note explaining what the input collects.                 | Useful when a scene has several input fields.                               |

## Configure an Input Field

{% stepper %}
{% step %}

### Select the Text Layer

Choose the text layer that should accept viewer input.
{% endstep %}

{% step %}

### Name the Field

Set the field name that identifies the viewer-entered value.
{% endstep %}

{% step %}

### Add Placeholder Text

Use placeholder copy that tells the viewer exactly what to enter.
{% endstep %}

{% step %}

### Choose the Input Mode

Use single-line input for short values and multiline input for longer messages.
{% endstep %}

{% step %}

### Preview Entry Behavior

Test typing, editing, empty values, long values, and multiline behavior in the player preview.
{% endstep %}
{% endstepper %}

## Success Checks

Before publishing an Input Field connector, confirm:

* The field name is stable and easy to identify.
* Placeholder text fits inside the input area.
* Single-line or multiline behavior matches the expected response.
* Long values do not break the layout.
* Empty input behavior is intentional.
* A Submit Form connector exists when the project needs to capture the entered value.

{% content-ref url="/pages/zCRyVOOHtlj7mplqnham" %}
[Submit Form](/apps/blings-studio/connectors/submit-form.md)
{% endcontent-ref %}

{% content-ref url="/pages/vF3GOo8viXK19zuT75hD" %}
[Data in Studio](/apps/blings-studio/data.md)
{% endcontent-ref %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.blings.io/apps/blings-studio/connectors/input-field.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.