How common is a dedicated settings screen in web products?
- By Ali Abouelatta
- n = 11,753
- Published
- Updated
- 2 min read
- saas · web · ux-patterns · design
Short answer
51% of tracked web companies have a settings screen captured: 345 of 671 companies, across 1,351 labeled screens — the 3rd most common screen type.source[1]source[2] Settings is 100% in-product, so it never appears in the marketing/pre-auth surface.source[3] The named leaders (google-workspace, front, clerk) each carry 20+ distinct settings screens, signaling deep settings hierarchies.
51% of 671 tracked web companies (345) have a settings screen; 1,351 settings screens in all — Lazyweb Research, July 2026.
Bar chart · Settings screens
Settings screens — The finding
One block is about 1.4 Settings screens
- google-workspace
- 39
- front
- 28
- clerk
- 22
- calendly
- 18
- okta
- 16
- notion
- 15
The finding
Settings ranks 3rd of 15 screen types by volume (1,351 screens) and by company coverage (345 of 671, 51.4%).source[1]source[2] It sits just behind editor and inbox and just ahead of feed. Every one of the 1,351 settings screens is in-product — settings is one of eight screen types that are 100% authenticated (editor, inbox, settings, feed, dashboard, profile, onboarding, cancellation).source[3]
The companies with the deepest settings coverage:
| Company | Settings screens |
|---|---|
| google-workspace | 39 |
| front | 28 |
| clerk | 22 |
| calendly | 18 |
| okta | 16 |
| notion | 15 |
How to apply it
A single settings page is the norm, but the leaders show settings is often a multi-screen surface (google-workspace 39, front 28).source[4] If you're scoping a settings redesign, benchmark against a hierarchy, not one page — infrastructure and identity products (clerk, okta) capture especially deep settings because account, security, and team configuration each get their own screen. Settings is also a candidate location for an in-product upgrade entry point, since it's authenticated and high-intent, though this census cannot confirm what individual settings screens surface.
Caveats
This census counts screen presence, not content. It cannot tell you whether settings surfaces plan/billing, profile, or notifications first — the web corpus has no element-level vision join.source[1] Company-level counts reflect capture depth: a company with 1 captured settings screen may have many more in production. Single June 2026 capture wave.
The numbers
| # | Stat | Computed from |
|---|---|---|
| [1] | 1,351 settings screens (3rd most common type) | screen_type_leaderboard: settings 1,351 |
| [2] | 345 of 671 companies (51.4%) have settings | screen_type_company_coverage: settings 51.4% (345/671) |
| [3] | settings is 100% in-product | in_product_by_screen_type: settings 100% in-product |
| [4] | top settings depth: google-workspace 39, front 28, clerk 22, calendly 18, okta 16, notion 15 | qualitative settings examples |
Methodology
Universe: 11,753 labeled desktop product screens across 671 web companies (sites_screen_labels), captured June 2026. Method: per-company presence and per-company screen counts for screen_type='settings'. Caveat: structural census — no element-level content data; single capture wave.
Sources
- [1]
Lazyweb Research analysis of 11,753 labeled desktop product screens (671 web companies), July 2026
Screen-type frequency, 15-type vocabulary, captured June 2026; structural only.
- [2]
Lazyweb Research analysis of 11,753 labeled desktop product screens (671 web companies), July 2026
Per-company settings coverage.
- [3]
Lazyweb Research analysis of 11,753 labeled desktop product screens (671 web companies), July 2026
is_in_product by screen type; settings 100% in-product.
- [4]
Lazyweb Research analysis of 11,753 labeled desktop product screens (671 web companies), July 2026
Named top-settings examples (per-company distinct screen counts).
Source: Lazyweb Research — proprietary analysis of real, in-market app screens. Cite as Lazyweb Research, 2026-07-07.