Slowly
The builderBlocks

Input

A form control for collecting input from visitors.

The Input block is a form control, the field a visitor types into or selects from. It is the building piece for forms you assemble yourself, rather than a whole form in one block.

Every setting in the table below (type, name, placeholder, value, the min/max/step/length bounds, pattern, autocomplete, and the required/disabled/readonly/checked/multiple/autofocus toggles) is applied as a real HTML attribute on the published field, not just in the editor canvas. A required email field publishes with type="email" and required, and the browser validates it accordingly.

Adding one

  1. Select the container or form wrapper to hold it.
  2. Open the inserter and search "input".
  3. Pick the Input block.

Settings

In the input's own panel. Appearance lives in the shared design panel.

SettingWhat it doesReach for it when
TypeThe kind of input: text, email, password, number, tel, url, date, time, checkbox, radio, range, file, hidden, textarea, and moreAlways; the browser uses it for keyboard type, validation, and built-in pickers
LabelVisible label text above or beside the field; on by defaultKeep it on; hiding it is only for cases where a visible label would be redundant and a screen-reader label is supplied another way
Label (dynamic)Pulls the label text from a dynamic sourceWhen labels come from a query or custom field
PlaceholderLight hint text shown inside the field before the visitor typesA short example value or format hint, not a replacement for a label
NameThe field's name attribute, used as the key when the form submitsRequired for any field whose value needs to reach your form handler
IDThe field's id attributeWhen you need to pair the input with an external label or script
RequiredMarks the field as mandatory and triggers browser validationContact and booking forms where the field cannot be blank
DisabledRenders the field non-interactiveShowing a value that the visitor cannot change
Read onlyThe field shows a value but the visitor cannot edit itPre-filled reference fields that should travel with the form
AutocompleteHints to the browser which autofill category applies, e.g. email, given-name, postal-codeFaster checkout and contact flows; set off to suppress autofill
AutofocusMoves focus to this field when the page loadsThe first and only prominent field on a dedicated landing or search page
Min / MaxLower and upper bounds for number, date, and range inputsPrice filters, date pickers, age gates
StepIncrement between valid values for number and rangeQuantity selectors that count in whole numbers or fixed intervals
Min length / Max lengthCharacter count bounds for text-based inputsPassword rules, short-code fields
PatternA regular expression the value must matchCustom formats such as reference numbers or postal codes
RowsNumber of visible text rows; turns the field into a textarea when above 1Message and notes fields that benefit from more vertical space
MultipleAllows more than one value, for file and email typesFile uploads that accept several attachments at once
ValueA pre-filled valueSeeding a field with a default or a value from a dynamic source

Styling

The input uses the shared design panel for spacing, colour, typography, borders, and effects. The states panel is where you style the focus ring and hover appearance, which matter most for keyboard users.

Accessibility

Give every input a label. The label setting is on by default; leave it on. A placeholder alone does not satisfy the requirement because it disappears the moment the visitor starts typing, and assistive tools do not consistently expose it as a label.

For checkbox and radio inputs, the label text is the thing a screen-reader user hears when they land on the field. Write it to make sense on its own, not just in the visual context around it.

If you turn the label off for a search field or similar, supply an aria-label or aria-labelledby via the HTML attributes panel so the field still has an accessible name.

On this page