Skip to main content

Password field

The password field component securely collects sensitive information from users. Use password field for password entry, where input characters are automatically masked for privacy.

Password fields support validation, help text, and accessibility features to create secure and user-friendly authentication experiences. For general text input, use text field.

Support
Targets (46)

Supported targets


Configure the following properties on the password field component.

Anchor to maxLength
maxLength
number
Default: Infinity
required

The maximum number of characters allowed in the field.

Anchor to minLength
minLength
number
Default: 0
required

The minimum number of characters required in the field.

Anchor to value
value
string
required

The current password value in the field as a string. When setting this property programmatically, it updates the field's display value. When reading it, you get the user's current input. The value is masked in the UI for security.

Anchor to autocomplete
autocomplete
"on" | "off" | | `section-${string} current-password` | `section-${string} new-password` | "shipping current-password" | "shipping new-password" | "billing current-password" | "billing new-password" | `section-${string} shipping current-password` | `section-${string} shipping new-password` | `section-${string} billing current-password` | `section-${string} billing new-password`
Default: 'on' for everything else
required

Controls browser autofill behavior for the field.

Basic values:

  • on - Enables autofill without specifying content type (default)
  • off - Disables autofill for sensitive data or one-time codes

Specific field values describe the expected data type. You can optionally prefix these with:

  • section-${string} - Scopes autofill to a specific form section (when multiple forms exist on the same page)
  • shipping or billing - Indicates whether the data is for shipping or billing purposes
  • Both section and group (for example, section-primary shipping email)

Providing a specific autofill token helps browsers suggest more relevant saved data.

Learn more about the set of autocomplete values supported in browsers.

Anchor to defaultValue
defaultValue
string
required

The initial value of the field when it first loads. Unlike placeholder, this is a real value that the user can edit and that gets submitted with the form. Once the user starts typing, their input replaces it. Changing this property after the field has loaded has no effect. To update the field value at any time, use value instead.

Anchor to details
details
string
required

Supplementary text displayed below the checkbox to provide additional context, instructions, or help. Use this to explain what checking the box means or provide guidance to users. This text is announced to screen readers.

Anchor to error
error
string
required

An error message displayed below the checkbox to indicate validation problems. When set, the checkbox is styled with error indicators and the message is announced to screen readers.

Anchor to label
label
string
required

The text displayed as the field label, which identifies the purpose of the field to users. This label is associated with the field for accessibility and helps users understand what information to provide.

Anchor to labelAccessibilityVisibility
labelAccessibilityVisibility
"visible" | "exclusive"
Default: 'visible'
required

Controls whether the label is visible to all users or only to screen readers.

  • visible: The label is shown to everyone (default).
  • exclusive: The label is visually hidden but still announced by screen readers.

Use exclusive when the surrounding context makes the label redundant visually, but screen reader users still need it for clarity.

Anchor to placeholder
placeholder
string
required

The placeholder text displayed in the field when it's empty, providing a hint about the expected input format or value.

Anchor to readOnly
readOnly
boolean
Default: false
required

Whether the field is read-only and can't be edited. Read-only fields remain focusable and their content is announced by screen readers.

Anchor to required
required
boolean
Default: false
required

Whether the field requires a value before form submission. Displays a visual indicator and adds semantic meaning, but doesn't automatically validate or show errors. Use the error property to display validation messages.

Anchor to disabled
disabled
boolean
Default: false
required

Whether the field is disabled, preventing any user interaction.

string
required

A unique identifier for the element. Use this to reference the element in JavaScript, link labels to form controls, or target specific elements for styling or scripting.

string
required

The name attribute for the field, used to identify the field's value when the form is submitted. Must be unique within the nearest containing form.

The password field component provides event callbacks for handling user interactions. Learn more about handling events.

<'input'>
required

A callback fired when the password field loses focus.

Learn more about the blur event.

Anchor to change
change
<'input'>
required

A callback fired when the password field value changes.

Learn more about the change event.

Anchor to focus
focus
<'input'>
required

A callback fired when the password field receives focus.

Learn more about the focus event.

Anchor to input
input
<'input'>
required

A callback fired when the user inputs data into the password field.

Learn more about the input event.


Securely collect sensitive credentials from users. This example pairs a label with masked input.

Preview

html

<s-password-field
label="Password"
placeholder="Enter your password"
details="Must be at least 8 characters long"
minLength="8"
></s-password-field>

Anchor to Set validation rulesSet validation rules

Enforce password requirements before submission. This example configures a required field with minimum length validation and autocomplete for new passwords.

Preview

html

<s-password-field
label="Password"
name="password"
required
minLength="8"
autocomplete="new-password"
></s-password-field>

Anchor to Show validation errorsShow validation errors

Communicate password problems clearly to users. This example displays an error message when the password doesn't meet length requirements.

Preview

html

<s-password-field
label="Password"
name="password"
error="Password must be at least 8 characters"
minLength="8"
autocomplete="new-password"
></s-password-field>

Help users understand password requirements upfront. This example adds helper text beneath the field explaining what makes a valid password.

Preview

html

<s-password-field
label="Create password"
name="new-password"
details="Password must be at least 8 characters and include uppercase, lowercase, and numbers"
minLength="8"
autocomplete="new-password"
></s-password-field>

Create a complete authentication form. This example combines a password field with an email field for login or registration.

Preview

html

<s-stack gap="base">
<s-email-field
label="Email"
name="email"
autocomplete="email"
required
></s-email-field>
<s-password-field
label="Password"
name="password"
autocomplete="current-password"
required
></s-password-field>
</s-stack>

Anchor to Display a requirement checklistDisplay a requirement checklist

Display a password requirements checklist alongside the field. This example lists requirements like character length and case requirements.

Preview

html

<s-stack gap="large-100">
<s-password-field
label="Create password"
name="password"
value="example-password"
autocomplete="new-password"
required
></s-password-field>
<s-stack gap="small-200">
<s-text tone="success">✓ At least 8 characters</s-text>
<s-text color="subdued">â—‹ Contains uppercase letter</s-text>
<s-text color="subdued">â—‹ Contains lowercase letter</s-text>
<s-text color="subdued">â—‹ Contains number</s-text>
</s-stack>
</s-stack>

  • Support password managers: Ensure the component works correctly with password managers by setting appropriate autocomplete values. Password managers help merchants create and store strong passwords, improving overall security.
  • Communicate requirements clearly: Show all password requirements before merchants start typing, not after they've already entered an invalid password. This prevents frustration and reduces form abandonment.
  • Provide helpful feedback for password creation: When merchants create new passwords, show real-time strength feedback and explain what would make their password stronger. Help them understand security trade-offs rather than just enforcing arbitrary rules.
  • Never block paste functionality: Merchants rely on password managers and other tools that use paste. Blocking paste forces merchants toward weaker passwords they can remember and type manually.
  • Validate server-side: Always validate passwords on the server. Client-side constraints can be bypassed by password managers, browser extensions, or merchants with developer tools. Use client-side validation for immediate feedback, not security.

  • The component doesn't include a built-in show/hide password toggle. If you need this feature (recommended for better UX), you must implement it yourself by conditionally switching between a password field and a text field.

Was this page helpful?