Paywall design examples

An upgrade prompt appears when someone reaches a plan limit and needs to decide whether to pay for more. Our examples show a project-limit paywall with a usage meter, Team plan benefits, a yearly-billing toggle, a price breakdown and Upgrade and Maybe later actions, across 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

Upgrade a plan

Paywall upgrade design tips

Explain which limit was reached and why the prompt appeared, so the upgrade feels connected to what the person was doing.
List the two or three benefits that solve the current problem first, rather than the full feature comparison table.
When offering yearly billing, show the per-month equivalent and the total charged today, so the saving is honest and easy to check.
Give a clear, respectful way to dismiss the prompt; disguising the decline option erodes trust and can breach consumer protection rules.

Questions

When is the best moment to show an upgrade prompt?

Show it when a person hits a real limit or tries a paid feature, because the value is obvious at that moment. Interrupting people at random, or on first launch before they have used the product, tends to feel pushy and is easy to dismiss without reading.

Should a paywall show the price straight away?

Yes, showing the price on the prompt itself builds trust and saves a click. Hiding the cost behind another screen makes people suspicious. Include the billing period, any tax note and whether the price is per user so the figure is not misleading.

How should the decline button be worded?

Use neutral, plain wording such as Maybe later or Not now. Avoid guilt-tripping labels that mock the person for declining, because they damage goodwill and are increasingly treated as a dark pattern by regulators and app store reviewers.

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.