FAQ section design examples

An FAQ section answers the questions that would otherwise stop someone from signing up or buying. Our examples show a section heading, six questions in an accordion with the first one expanded, and a contact card for anything not covered, laid out for desktop and mobile across eight visual styles, each with HTML and a design token file. 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

FAQ design tips

Write each question the way customers actually phrase it, taken from support tickets and sales calls, rather than questions you wish they asked.
Make the whole question row the click target and show a clear plus or chevron that changes state when the answer is open.
Answer directly in the first sentence, then add detail, so people scanning the accordion get what they need quickly.
Use proper button elements with aria-expanded on accordion triggers, so keyboard and screen reader users can open answers.

Questions

How many questions should an FAQ section have?

Enough to cover the real objections, usually between five and ten on a landing page. If you have more, group them under headings or link to a full help centre. A long list of minor questions buries the important ones and makes the section harder to scan.

Should FAQ answers be in an accordion?

Accordions keep long FAQ sections compact and let people scan questions quickly, which suits landing pages. For short lists or pages where every answer matters, showing everything open can be better, since nothing is hidden and the page can be searched with the browser's find tool.

Should the first FAQ item be open?

Opening the first item is a useful cue that the rows expand, and it lets you surface the most important answer. Keep the rest closed so the list stays scannable. Let several items stay open at once, so people can compare answers without losing their place.

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.