FIELD FEATURES

Common field options and text placement

Understand Logical Forms labels, descriptions, required states, placeholders, admin labels, defaults, CSS classes and per-field text placement.

3 min read · Updated November 19, 2026

Select a field on the builder canvas to open Field options. General, Appearance and Advanced organize its controls. The exact options depend on the field: a Content block, compound Address and ordinary Text input do not collect the same kind of answer.

Labels, descriptions and required answers

Setting What it does
Label The question or input name visitors see. Use a descriptive label. A blank label is allowed, but a placeholder is not a reliable replacement for an accessible name.
Description Instructions for completing this field. Use it for examples, units, allowed formats or context.
Required An applicable question must have a valid nonempty answer. It does not make the Label setting required or require every checkbox in a group.

A Number Slider already has a value and uses its range controls rather than an ordinary Required toggle. Display-only fields do not collect an answer. For compound inputs, the field and individual enabled components can have their own required behavior.

Appearance controls

Setting What it does
Placeholder A short hint inside an empty input, on fields that support it. It is not stored as an answer.
Hide label Hides the visible label while retaining it for assistive technology. Prefer this to deleting a useful label when you want a visually quiet layout.
CSS classes Space-separated class names on the outer field wrapper. Enter class names, not CSS declarations.
Description placement Inherit from form, Above inputs or Below inputs.
Validation message placement Inherit from form, Above inputs or Below inputs.
Sub-label placement On supported compound fields, positions labels for the component inputs. Time initially defaults below its inputs.

Inherited placement comes from General → Layout. Per-field overrides let one longer instruction sit below its input while other questions keep the form default. Form-wide colors and spacing belong to Appearance settings.

Administrative names, defaults and browser hints

Admin label identifies a field in relevant administration headings, pickers and summary columns. Visitors still see its ordinary label. Leave it blank to use the visible label, with a type/ID fallback where needed. Renaming either label does not change the numeric field ID.

Default value or default choices provide an initial answer. They do not refill a value the visitor deliberately clears or replace historical empty entries. Autocomplete, where offered, accepts a browser autocomplete token such as organization or off; the browser controls how it uses that hint.

Custom validation messages

Required message and Invalid value message can override the corresponding field feedback. Blank follows site-wide Messages or the provider's default. These controls accept plain text, not executable HTML or email merge tags. Use wording that covers the field's actual possible errors.

Use the dedicated guides for Visibility, Dynamic population, Conditional logic, validation limits and masks, and Pro duplicate prevention. A control appears only on supporting field types; its absence is not evidence that every other field is missing a setting.

Save the form after editing. The builder guide explains layout and preview; the testing guide covers the actual visitor path.