Website footer design examples

A site footer is where visitors go for anything the header does not cover, from careers to legal pages. Our examples include a logo with a one-line description, four link columns, a newsletter signup, social icons, a legal row and a system status pill, shown on desktop and mobile across eight visual styles in 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

Footer design tips

Group footer links into a few labelled columns, such as Product, Company, Resources and Legal, so people can find what they want quickly.
Collapse link columns into accordions on mobile, or keep them short enough to list, so the footer does not become an endless scroll.
Keep the newsletter signup to a single email field and button, with one line saying what subscribers will receive and how often.
Put copyright, privacy, terms and cookie settings in a slim bottom row, separated from the main navigation links.

Questions

What should a website footer include?

Typically the logo and a short description, grouped navigation links, contact details, social profiles, a newsletter signup if you send one, and a legal row with copyright, privacy policy, terms and cookie settings. Include only links people genuinely look for at the bottom of a page.

How many links should a footer have?

Enough to cover the pages people look for at the end of a page, usually four or five columns of up to six or seven links each. A footer stuffed with dozens of links is hard to scan and looks cluttered. Put rarely needed pages on a sitemap instead.

Should a footer include a newsletter signup?

If you publish a newsletter, the footer is a natural, low-pressure place for it, because it appears on every page without interrupting reading. Keep it to an email field, a clear button and a line about what people will get. Confirm the signup inline.

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.