Welcome screen design examples

A welcome screen greets new users after sign-up and guides them to their first meaningful action. Our examples show a personal greeting, three getting-started choices, a five-step setup checklist with progress and a primary call to action, designed for web and mobile in eight visual styles with light and dark themes. 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 · First run to first project

Welcome design tips

Greet people by name and get to the point in one line; the screen's job is to start them doing something.
Offer a small number of starting paths, such as a template, an import or a blank start, matched to common goals.
Pre-tick checklist items the person has already completed, like creating an account, so progress starts above zero.
Make the checklist dismissible and reachable later, because some users prefer to explore before following guided steps.

Questions

What should a welcome screen after sign-up include?

A short greeting, a clear first action and a way to choose between a few starting points. A setup checklist helps if the product needs several steps before it is useful. Avoid long tours on this screen; let people begin and offer help in context.

Do setup checklists help new users?

They often help because they make the path to value visible and give people a sense of progress. Keep the list short, order items by importance, and make each item link straight to the place where the task is completed.

Should a welcome screen use a product tour?

Brief, optional tours can help with unfamiliar interfaces, but many people skip them. Contextual hints that appear when a feature is first used tend to be more effective than a long tour shown immediately. Always provide an obvious way to skip.

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.