← Docs/Login form design patterns

Login form design patterns

Battle-tested patterns for auth forms that convert.

Single-field flow

Show one input at a time. Email first, then password. Reduces cognitive load and keeps the user focused on a single action. Works best for returning-user flows where account lookup happens server-side between steps.

Inline validation

Validate on blur, not on submit. Show errors next to the field immediately. Green checkmark on valid fields builds momentum. Never clear the password on a failed attempt — it erodes trust.

Too short

Social-first layout

Place OAuth buttons above the email/password divider. Most users prefer social login when available. The divider with “or continue with email” signals that email is the fallback, not the primary path.

or

Error state grace

Never say “invalid credentials” without offering a path forward. Pair every error with a one-click recovery action: reset password link, magic-link resend, or support contact. The form should feel helpful, not accusatory.

Email or password doesn't match. Reset password