Form validation error design examples

Good validation tells people what went wrong and how to fix it. This create-workspace form is shown after a failed submit: an error summary links to each problem, invalid fields carry the danger colour plus an icon and a written message, a taken URL comes with alternatives, password rules show which are met, and valid fields are ticked. Every example is an original design that comes with its HTML code and a DESIGN.md of colour, type and spacing tokens, in light and dark. Free to use and adapt.

DeviceAll Web Mobile

StyleAll Minimal Editorial Brutalist Luxury Playful Corporate Retro Monochrome

Theme

16 examples

Web · minimal

Web · editorial

Web · brutalist

Web · luxury

Web · playful

Web · corporate

Web · retro

Web · monochrome

Mobile · minimal

Mobile · editorial

Mobile · brutalist

Mobile · luxury

Mobile · playful

Mobile · corporate

Mobile · retro

Mobile · monochrome

See it in a flow

Sign up and onboarding

Form validation errors design tips

Put an error summary at the top after submit, with each problem linking to its field.
Write messages that say how to fix it (“Add a number”), not just what is wrong (“Invalid password”).
Never rely on colour alone: pair the danger colour with an icon and text, and keep the label visible.
Validate on blur or submit, not on every keystroke, and confirm valid fields quietly.

Questions

When should form validation happen?

Check formats when a field loses focus and everything again on submit. Avoid showing errors while someone is still typing their first attempt.

Where should error messages go?

Directly below or beside the field they belong to, plus a summary at the top of the form after a failed submit so screen-reader and keyboard users can find every problem.

Should the submit button be disabled until the form is valid?

Usually not: a disabled button gives no reason. Let people submit and then show clear errors.

Browse by pattern

App screens

Dashboard
Data table
Analytics charts
Login
Sign up
Forgot password
Two-factor code
Welcome
Onboarding step
Permissions request
Home
Feed
List view
Detail view
Kanban board
Calendar
File manager
Search results
Editor toolbar
AI chat assistant
Chat list
Chat thread
Video call
Image viewer
Map view
Video player
Create post
Class schedule
Booking details
Booking confirmed
Product detail
Cart
Checkout
Order confirmation
Settings
Profile
Notifications center
Team members
Roles permissions
Audit log
API keys
Integrations
Billing plans
Invoice
Paywall upgrade
Cancel subscription
Empty state
404 error
Loading skeleton
Success confirmation
AI workspace
AI settings
Version history
Approval queue
Doctor directory
Telehealth visit
Clinic home
Music player
Playlist
Portfolio home
Case study
Security dashboard
Project tracker
Course dashboard
Multi-step form wizard
Bank onboarding
Product scan
Split view (master-detail)
Canvas editor
Floor plan
Voice call
Toast / snackbar with undo
Confirm dialog (destructive)
Side drawer
Command palette
Date range picker
Form validation errors
Sign-in error
Card declined at checkout
Find a pro (home services)
Book a home-service visit
Job tracker
Account email
Order email
Shift scheduler
Leave calendar
Time-off request
Multi-location operations dashboard
Inventory stock
Savings goal
Onboarding carousel

UI components

Tabs
Cards
Pagination
Popover
Tooltip
Dropdown menu
Accordion
Radio buttons
Breadcrumbs
Toggle switch
Stepper
Sidebar navigation
Loading spinner

Website sections

Website templates

Building with an AI coding agent? Every screen here is also in the free Made Good Designs MCP server: ask Claude, Cursor or ChatGPT to search_ui_screens (e.g. “billing settings, editorial style”), get_ui_flow for a whole journey, and get_ui_screen_code to pull the HTML and DESIGN.md straight into your project.