search⌘K

Input

Last Updated: September 2026

Inputs are information capture elements that allow the user to directly enter short, unstructured text.

Anatomy

link
Dotted grid scale: 8px
  1. 1Container
  2. 2Control
  3. 3Adornment

Variants

link

Default

Plain text field with placeholder.

Start adornment

Prefix content via Input.Adornment position="start".

End adornment

Suffix content or icon via position="end".

Disabled

disabled greys out the control and blocks interaction.

Sizes

link

Inputs support 3 sizes: S, M, and L.

Line spacing scale: 8px
28px
36px
48px

Usage Guidelines

link

When to use

  • •For single-line text, email, search, or numeric entry.
  • •When you need start/end adornments (currency, units, icons).
  • •As the text control inside a labeled Field.

When not to use

  • •For choosing from a fixed list — use Select.
  • •For international phone numbers with a country picker — use PhoneInput.
  • •For multi-line notes — use a textarea pattern instead.
checkDo

Use adornments to reinforce meaning (search, units, currency).

closeDon't

Don't rely on placeholder alone as the only label in production forms.

checkDo

Set the correct type (email, search, number) for better mobile keyboards.

closeDon't

Don't build country + phone yourself — use PhoneInput.

Behaviors

link

Focus

  • •Focus styles apply on the container via focus-within (accent border and ring).

Invalid / disabled

  • •Invalid styling responds to data-invalid on the control (typically from Field).
  • •Disabled styling responds to data-disabled; use the disabled prop.

Adornments

  • •Children are slotted: Input.Adornment with position start or end.
  • •Only one start and one end adornment are extracted via useSlots.

Content Guidelines

link

Placeholders

  • •Use short examples ('name@email.com'), not instructions.
  • •Prefer a visible Field.Label; placeholders are supplementary.

Adornment content

  • •Keep adornments short — a symbol, unit, or single icon.
  • •Don't put interactive primary actions inside adornments.

Accessibility

link

Text & Labels

  • •Pair with a visible label (Field.Label) in forms.
  • •Icon-only adornments should not be the only accessible name — label the input.

ARIA attributes

  • •Forward aria-invalid / aria-describedby when composing with Field.
  • •Native disabled is exposed on the input element.

Keyboard Support

  • •Tab → focus the text control.
  • •Standard text editing keys apply.

FAQs

link

How do I add a prefix or suffix?

Render Input.Adornment as a child with position="start" or position="end".

Can I change height?

Use size="sm" | "md" | "lg". Default is md.

Input vs PhoneInput?

Use Input for general text. Use PhoneInput when you need a country dial-code picker plus tel entry.

link