Enter a one-time code with support for pasting, autofill, and native form validation.
Use an OTP Input for a short code sent by text or email, like a sign-in or verification code. Each character gets its own slot, and a pasted or autofilled code fills them all at once.
<script lang="ts">
import { MinusIcon } from "@lucide/svelte"
import { Field, FieldLabel } from "@ui-sdk/svelte/field"
import {
OTPInput,
OTPInputGroup,
OTPInputSeparator,
OTPInputSlot,
} from "@ui-sdk/svelte/otp-input"
</script>
<Field>
<FieldLabel>Verification code</FieldLabel>
<OTPInput maxLength={6}>
<OTPInputGroup>
<OTPInputSlot index={0} />
<OTPInputSlot index={1} />
<OTPInputSlot index={2} />
</OTPInputGroup>
<OTPInputSeparator>
<MinusIcon aria-hidden="true" />
</OTPInputSeparator>
<OTPInputGroup>
<OTPInputSlot index={3} />
<OTPInputSlot index={4} />
<OTPInputSlot index={5} />
</OTPInputGroup>
</OTPInput>
</Field>Installation
npm install @ui-sdk/svelte @ui-sdk/coreComposition
Use the following composition to build an OTPInput:
OTPInput
โโโ OTPInputGroup
โโโ OTPInputSlot
โโโ OTPInputSlotOTPInput creates the native input and holds the code. OTPInputGroup lays out a run of slots. Each OTPInputSlot displays the character at its zero-based index. Add OTPInputSeparator between groups when the code is easier to read in sections, like the dash in the example above.
Groups and separators change the presentation of one value. They do not create additional fields or tab stops: the slots display the value of a single native input, which handles selection, paste, undo, form submission, and autofill. It uses autocomplete="one-time-code" so supported browsers and password managers can offer a saved or received code.
Usage
Import the parts and put them together:
<script lang="ts">
import {
OTPInput,
OTPInputGroup,
OTPInputSlot,
} from "@ui-sdk/svelte/otp-input"
</script>
<OTPInput maxLength={4} aria-label="Verification code">
<OTPInputGroup>
<OTPInputSlot index={0} />
<OTPInputSlot index={1} />
<OTPInputSlot index={2} />
<OTPInputSlot index={3} />
</OTPInputGroup>
</OTPInput>Four Digits
Set maxLength to the code's length and render that many slots. The default length is six.
<script lang="ts">
import { Field, FieldLabel } from "@ui-sdk/svelte/field"
import {
OTPInput,
OTPInputGroup,
OTPInputSlot,
} from "@ui-sdk/svelte/otp-input"
</script>
<Field>
<FieldLabel>PIN</FieldLabel>
<OTPInput maxLength={4} textAlign="center">
<OTPInputGroup>
{#each [0, 1, 2, 3] as index (index)}
<OTPInputSlot {index} />
{/each}
</OTPInputGroup>
</OTPInput>
</Field>Alphanumeric
Set pattern to digits, letters, or alphanumeric. The default is digits. The pattern filters characters and selects a suitable keyboard on touch devices.
<script lang="ts">
import { MinusIcon } from "@lucide/svelte"
import { Field, FieldLabel } from "@ui-sdk/svelte/field"
import {
OTPInput,
OTPInputGroup,
OTPInputSeparator,
OTPInputSlot,
} from "@ui-sdk/svelte/otp-input"
</script>
<Field>
<FieldLabel>Recovery code</FieldLabel>
<OTPInput maxLength={8} pattern="alphanumeric">
<OTPInputGroup>
{#each [0, 1, 2, 3] as index (index)}
<OTPInputSlot {index} />
{/each}
</OTPInputGroup>
<OTPInputSeparator>
<MinusIcon aria-hidden="true" />
</OTPInputSeparator>
<OTPInputGroup>
{#each [4, 5, 6, 7] as index (index)}
<OTPInputSlot {index} />
{/each}
</OTPInputGroup>
</OTPInput>
</Field>Custom Pattern
Pass a regular expression, such as /[0-9A-F]/i to accept hexadecimal characters. Use inputMode to choose the keyboard separately. The example displays letters in uppercase without changing their stored case.
<script lang="ts">
import { Field, FieldLabel } from "@ui-sdk/svelte/field"
import {
OTPInput,
OTPInputGroup,
OTPInputSlot,
} from "@ui-sdk/svelte/otp-input"
</script>
<Field>
<FieldLabel>Device code</FieldLabel>
<OTPInput maxLength={6} pattern={/[0-9A-F]/i} inputMode="text">
<OTPInputGroup>
{#each [0, 1, 2, 3, 4, 5] as index (index)}
<OTPInputSlot {index} />
{/each}
</OTPInputGroup>
</OTPInput>
</Field>Validation
Inside a Field, pass invalid when your code rejects the value, such as a code the server didn't accept. The field marks the input with aria-invalid and connects its FieldError. Outside a field, pass aria-invalid and aria-describedby yourself.
<script lang="ts">
import { Field, FieldError, FieldLabel } from "@ui-sdk/svelte/field"
import {
OTPInput,
OTPInputGroup,
OTPInputSlot,
} from "@ui-sdk/svelte/otp-input"
let invalid = $state(true)
</script>
<Field {invalid}>
<FieldLabel>Verification code</FieldLabel>
<OTPInput defaultValue="482913" onValueChange={() => (invalid = false)}>
<OTPInputGroup>
{#each [0, 1, 2, 3, 4, 5] as index (index)}
<OTPInputSlot {index} />
{/each}
</OTPInputGroup>
</OTPInput>
<FieldError>That code has expired. Request a new one.</FieldError>
</Field>Controlled
Use bind:value to bind the code. onValueChange also receives the change details. Call details.cancel() in the change callback to reject a change. Incoming values are filtered by the pattern and limited to maxLength, just like typed values.
<script lang="ts">
import { Field, FieldLabel } from "@ui-sdk/svelte/field"
import {
OTPInput,
OTPInputGroup,
OTPInputSlot,
} from "@ui-sdk/svelte/otp-input"
import { useLog } from "./log"
const log = useLog()
let value = $state("")
</script>
<Field>
<FieldLabel>One-time password</FieldLabel>
<OTPInput
bind:value
onValueChange={(next, details) =>
log(`${next || "Empty"} (${details.reason})`)}
>
<OTPInputGroup>
{#each [0, 1, 2, 3, 4, 5] as index (index)}
<OTPInputSlot {index} />
{/each}
</OTPInputGroup>
</OTPInput>
</Field>See State and Events for the shared state conventions. The reason distinguishes typing, pasting, undo, and controller actions.
On Complete
onValueCommit runs when a change fills every slot, including typing, paste, autofill, and controller writes. Changing an already-full code runs it again. Form resets and page restoration do not.
<script lang="ts">
import { Field, FieldLabel } from "@ui-sdk/svelte/field"
import {
OTPInput,
OTPInputGroup,
OTPInputSlot,
} from "@ui-sdk/svelte/otp-input"
import { useLog } from "./log"
const log = useLog()
</script>
<Field>
<FieldLabel>Verification code</FieldLabel>
<OTPInput
onValueCommit={(value, details) =>
log(`Checking ${value} (${details.reason})`)}
>
<OTPInputGroup>
{#each [0, 1, 2, 3, 4, 5] as index (index)}
<OTPInputSlot {index} />
{/each}
</OTPInputGroup>
</OTPInput>
</Field>Forms
Set name to include the code in FormData. required blocks an empty code, and a partial code fails length validation. Reset restores the default value. Use form to associate a control outside the form with its ID.
<script lang="ts">
import {
Field,
FieldDescription,
FieldError,
FieldLabel,
} from "@ui-sdk/svelte/field"
import {
OTPInput,
OTPInputGroup,
OTPInputSlot,
} from "@ui-sdk/svelte/otp-input"
import { useLog } from "./log"
const log = useLog()
function onsubmit(event: SubmitEvent & { currentTarget: HTMLFormElement }) {
event.preventDefault()
const data = [...new FormData(event.currentTarget)].map(
([name, value]) => `${name}=${value}`
)
log(`Submitted ${data.join(", ")}`)
}
</script>
<div data-slot="stack">
<form id="verify-sign-in" {onsubmit}>
<Field>
<FieldLabel>Verification code</FieldLabel>
<OTPInput name="code" required>
<OTPInputGroup>
{#each [0, 1, 2, 3, 4, 5] as index (index)}
<OTPInputSlot {index} />
{/each}
</OTPInputGroup>
</OTPInput>
<FieldDescription
>Enter the six-digit code we sent to hollis@example.com.</FieldDescription
>
<FieldError />
</Field>
</form>
<Field>
<FieldLabel>Recovery code (optional)</FieldLabel>
<OTPInput
name="recovery"
form="verify-sign-in"
maxLength={8}
pattern="alphanumeric"
>
<OTPInputGroup>
{#each [0, 1, 2, 3, 4, 5, 6, 7] as index (index)}
<OTPInputSlot {index} />
{/each}
</OTPInputGroup>
</OTPInput>
<FieldError />
</Field>
<div data-slot="row">
<button type="reset" form="verify-sign-in">Reset</button>
<button type="submit" form="verify-sign-in" data-variant="solid"
>Verify</button
>
</div>
</div>A typed partial code reports tooShort. Partial default values and controller writes are checked through the native input's pattern, because browsers do not apply minlength validation to those values.
Disabled and Read-Only
A disabled input cannot be focused, changed, or submitted. readOnly prevents changes while keeping the input focusable and included in form data.
<OTPInput disabled defaultValue="123456" aria-label="Disabled code">
...
</OTPInput>
<OTPInput readOnly defaultValue="654321" aria-label="Read-only code">
...
</OTPInput>Controller
Create a createOTPInputController() and pass it as controller to read, fill, clear, or focus the input from another control. Writes use the imperative reason and pass through the same filtering and change callbacks as typing.
<script lang="ts">
const code = createOTPInputController()
</script>
<button onclick={() => code.setValue("123456")}>Fill</button>
<button onclick={() => code.clear()}>Clear</button>
<button onclick={() => console.log(code.getValue())}>Read</button>
<button onclick={() => code.focus()}>Focus</button>
<OTPInput controller={code} aria-label="Verification code">...</OTPInput>Controllers covers creating and sharing a controller.
Custom Rendering
The root's state exposes all slots. Each slot exposes char, active, and hasFakeCaret if you want to draw its contents yourself. See Parts and Composition for the rendering conventions.
Styling
Draw the active slot and caret with data-active and data-fake-caret. The examples include the caret animation and disable it for reduced motion. Keep position: relative on each slot so its caret stays inside it.
Each part has a data-slot, such as otp-input-slot, and its state attributes are listed under Data Attributes.
Data Attributes
OTPInput
[data-slot="otp-input"]
| Attribute | What it means |
|---|---|
data-complete | Present while every slot is filled. |
data-filled | Present while the code holds any character. |
data-disabled | Present when disabled, by its own prop or a <fieldset>. |
data-focused | Present while the input has focus. |
OTPInputGroup
[data-slot="otp-input-group"]
| Attribute | What it means |
|---|---|
data-complete | Present while every slot is filled. |
data-filled | Present while the code holds any character. |
data-disabled | Present when disabled, by its own prop or a <fieldset>. |
data-focused | Present while the input has focus. |
OTPInputSlot
[data-slot="otp-input-slot"]
| Attribute | What it means |
|---|---|
data-filled | Present while the slot holds a character. |
data-disabled | Present when disabled, by its own prop or a <fieldset>. |
data-active | Present on the slot typing goes to: the selected character, or the empty slot after the last one. Only while focused. |
data-fake-caret | Present on the active slot while it's empty. Draw a blinking caret in it; the input's own caret is hidden. |
OTPInputSeparator
[data-slot="otp-input-separator"]
| Attribute | What it means |
|---|---|
data-disabled | Present when disabled, by its own prop or a <fieldset>. |
API Reference
Props and callbacks are the same as below, as Svelte props. value can be bound with bind:value. id, autofocus, aria-label,
aria-labelledby, aria-describedby and aria-invalid go to the input.
OTPInput
debug?boolean- Logs every state change with its reason to the console, in development builds.
value?string- The code, for a controlled input.
defaultValue?string- The code it starts with, when uncontrolled. A form reset returns here.
onValueChange?((value: string, details: ChangeDetails<OTPInputValueChangeReason>) => void)- Runs when the code changes: typing or deleting (
"input-change"), a paste ("paste"), the browser's undo and redo, a form reset, or a controller. Autofill and codes from the keyboard's suggestions are"input-change".details.cancel()keeps the code as it was. onValueCommit?((value: string, details: CommitDetails<OTPInputValueChangeReason>) => void)- Runs when a change fills every slot, with the whole code, like to verify it. A controller filling it counts, so does a code that changes while full.
maxLength?number- How many characters the code has, one slot each.
pattern?OTPInputPattern- Which characters it accepts:
"digits","letters","alphanumeric", or a regular expression each character must match, like/[A-F0-9]/i. Anything else typed, pasted or dropped is ignored. inputMode?"decimal" | "none" | "numeric" | "tel" | "text"- The keyboard touch screens show.
textAlign?"center" | "end" | "start"- Where the invisible input keeps its text and caret. It decides where the browser puts its own popups, like the paste menu on phones.
"start"and"end"follow the reading direction. autoComplete?string- The input's
autocomplete."one-time-code"lets phones offer a code from a message, and password managers fill it. disabled?boolean- Disables it like a native input: it can't be focused, and isn't submitted.
readOnly?boolean- Makes it read-only: focusable and submitted, but the code can't change.
required?boolean- Requires a code before the form submits. A partial code is too short either way.
name?string- The name it submits the code under.
form?string- The id of a form to belong to, when it isn't inside that form.
controller?{ getValue: () => string; setValue: (value: string, options?: OTPInputChangeOptions) => boolean; clear: (options?: OTPInputChangeOptions) => boolean; focus: () => void; }- Reads and writes the code from anywhere. Create one with
createOTPInputController().
OTPInputSlot
indexnumber- Which character of the code the slot shows, from 0.
State
What render and children snippets receive. The root, groups and separators get the
input's state.
valuestring- The code.
slotsOTPInputSlotData[]- One entry per slot: its character, whether it's active, and whether it draws a caret.
focusedboolean- Whether the input has focus.
completeboolean- Whether every slot is filled.
disabledboolean- Whether it's disabled, by itself or by a
<fieldset>.
Slots get their own:
charstring | null- The character in the slot, or null when it's empty.
activeboolean- Whether the slot is where typing goes: the selected character, or the empty slot after the last one.
hasFakeCaretboolean- Whether the slot should draw a caret: it's active and empty. The real caret is hidden.
indexnumber- Which character of the code the slot shows.
focusedboolean- Whether the input has focus.
disabledboolean- Whether it's disabled, by itself or by a
<fieldset>.
Reasons
details.reason says why the code changed. Autofill and a code from the keyboard's suggestions are input-change.
input-changeEvent- Typing, pasting or dropping changed a text field's value; in a combobox it can also open or close it, or Enter keeps the typed text as the value.
pasteClipboardEvent- Files were pasted, like a screenshot, or text and tokens into a token input.
undoKeyboardEvent | InputEvent- Undo, from the keyboard, the Edit menu or a controller.
redoKeyboardEvent | InputEvent- Redo, from the keyboard, the Edit menu or a controller.
resetnone- A form reset.
restorenone- The browser restored state, like after going back, or a saved value was read back from storage.
imperativenone- A controller or
apicall, or a property set on a web component.
Controller
Create one with createOTPInputController() and pass it as controller.
setValue() and clear() take an optional { reason, event }, and run the change callback like typing.
getValue()() => string- The code.
setValue(value, options?)(value: string, options?: OTPInputChangeOptions | undefined) => boolean- Sets the code, as typing it would. Characters that don't fit the pattern are dropped. Returns false when the change was canceled or nothing changed.
clear(options?)(options?: OTPInputChangeOptions | undefined) => boolean- Empties the code. Returns false when the change was canceled or nothing changed.
focus()() => void- Moves focus to the input.
Events
Callbacks get the code first, then the details. A bound value only updates when onValueChange didn't cancel the change.
| Prop | On | Receives |
|---|---|---|
bind:value | OTPInput | The code |
onValueChange | OTPInput | (value, details): the new code and the reason |
onValueCommit | OTPInput | (value, details): the full code and the reason that filled it |
Accessibility
Name the input with FieldLabel, a native label, aria-label, or aria-labelledby. Screen readers encounter one input with the whole code; the visual slots, groups, and separators are hidden from them.
Keyboard
The input keeps its native keys. Arrow keys, Home, and End move the selection between slots, Backspace deletes, and your usual shortcuts undo and redo. Pasting a code such as 123-456 removes the separators.
Tested Behavior
Every line below is an automated test.
- Typing fills the slots in order.
- Characters the pattern doesn't accept are ignored.
- Filling every slot completes the code.
- Backspace deletes the last character.
- ArrowLeft goes back a slot, and typing replaces its character.
- Pressing a filled slot lets you retype it.
- Pasting a code with a dash fills every slot.
- The form submits the code under its name.
- A partial default code is too short to submit.
- A typed partial code is too short, not the wrong format.
- A canceled change keeps the code.
- A disabled code can't be typed into.
- A code of letters and digits takes both.
- The input asks for a one-time code and a numeric keyboard.
- Typing a whole code with no waits fills it.
Runs in React, Vue and web components.