Components
Component
productdevbook/ui

Stable in React

OTP Field

A one-time password input made of single-character slots.

Loading React 19.3.1…
Hover a part or use it. The code follows. · Loading React…
405Tests passing in React · 0 failing
10.7 KiBSize
Not measured yetMemory
Not measured yetSpeed
productdevbook and 10 upstream authors9 commits · last

Install#

One package per framework. OTP Field's parts come from it; the anatomy tab at the top shows how they nest.

bun add @▢▢▢▢/react

Three parts. The example uses three of them; the data does not say which are required.

  • OTPField.RootGroups all OTP field parts and manages their state.
  • OTPField.SeparatorA separator element accessible to screen readers.
  • OTPField.InputAn individual OTP character input.

Examples#

Common ways to put it to work. Each one runs live.

validationType accepts letters and digits for recovery or invite codes.

OTPFieldAlphanumeric.tsx

Styling and accessibility#

The parts ship no styles. Style their states with these attributes; the CSS tab at the top has a sheet. The same CSS works in all five frameworks.

  • [data-complete]Present when all slots are filled. On Root, Input.
  • [data-disabled]Present when the OTP field is disabled. On Root, Input.
  • [data-readonly]Present when the OTP field is readonly. On Root, Input.
  • [data-required]Present when the OTP field is required. On Root, Input.
  • [data-valid]Present when the OTP field is in a valid state (when wrapped in Field.Root). On Root, Input.
  • [data-invalid]Present when the OTP field is in an invalid state (when wrapped in Field.Root). On Root, Input.
  • [data-touched]Present when the OTP field has been touched (when wrapped in Field.Root). On Root, Input.
  • [data-dirty]Present when the OTP field's value has changed (when wrapped in Field.Root). On Root, Input.
  • [data-filled]Present when the OTP field contains at least one character. On Root, Input.
  • [data-focused]Present when one of the OTP field inputs is focused. On Root, Input.
  • [data-orientation]Indicates the orientation of the separator. On Separator.

Keyboard

  • Fills the slot and moves to the next one On Input.
  • ArrowLeftArrowRightMoves between slots On Input.
  • HomeMoves to the first slot On Input.
  • EndMoves to the first empty slot at the end On Input.
  • BackspaceDeletes the character and moves to the previous slot On Input.
  • DeleteDeletes the character and stays in the slot On Input.

Set for you

  • role="group", aria-labelledby to the Field labelthe slots are read as one named fieldRoot
  • tabindex="0" on the active slot onlyTab passes the whole code in one stepInput
  • the field's label on the first slot, your aria-label on the otherseach slot can be named, such as "Character 2 of 6"Input
  • aria-invalid when validation failsthe error state is read on every slotInput
  • role="separator"a visual break between groups of slots is announced as suchSeparator

API reference#

19 props across 3 parts, in React syntax, and className, style, render once for every part. Open a row to try it.

OTPField · all parts
Shared propsEvery part that renders an element takes these.
classNameCSS class applied to the element, or a function that returns a class based on the component's state.string | ((state: State) => string | undefined)
styleStyle applied to the element, or a function that returns a style object based on the component's state.React.CSSProperties | ((state: State) => React.CSSProperties | undefined)
renderAllows you to replace the component's HTML element with a different tag, or compose it with another component.React.ReactElement<unknown, string | React.JSXElementConstructor<any>> | ComponentRenderFn<React.DetailedHTMLProps<React.InputHTMLAttributes<HTMLInputElement>, HTMLInputElement>, State>

Use it in React#

What differs from the React API. Switch the framework at the top of the page.

@▢▢▢▢/react is the React 19 package. Its parts, props, data attributes and error messages are upstream Base UI's, and upstream's own tests run against it.

  • Parts

    Each component is its own entry point and exports one namespace named after it.

    import { Switch } from '@base-ui-next/react/switch'
    
    export function Example() {
      return (
        <Switch.Root>
          <Switch.Thumb />
        </Switch.Root>
      )
    }

    A part renders the element its API reference names, such as a <span> for Switch.Root.

  • Props and events

    Props and callbacks have upstream's names and signatures: onCheckedChange(checked, details), onOpenChange(open, details), onValueChange(value, details). details carries reason, event, cancel() and allowPropagation(). Native handlers are React's (onClick, onKeyDown), and event.preventBaseUIHandler() stops a part's own handler.

  • Styling

    className takes a string or a function (state) => string; style takes an object or a function (state) => object. The state's data-* attributes are on the element for CSS.

  • render

    render takes an element (render={<a href="/docs" />}) or a function (props, state) => element that spreads props on what it returns.

  • Refs

    ref reaches the part's element. Imperative handles are ref props, as upstream: inputRef, and actionsRef ({ validate } on Field and Form, { unmount, close } on Dialog).

  • Binding

    A part is controlled when its value prop (checked, open, value) is set, and uncontrolled with the default form (defaultChecked, defaultOpen, defaultValue). React has no two-way binding: pair the value with its change callback.

  • From @base-ui/react
    Change the import from @base-ui/react/<component> to @▢▢▢▢/react/<component>.
  • From @base-ui/react
    Nothing else changes: props, parts, data attributes and errors are the same.