Density Settings
Density Settings is the Salesforce Setup page that controls the default visual density of Lightning Experience: Comfy (more whitespace, larger row heights, easier-to-click targets) or Compact (tighter spacing, more data on screen, denser tables).
Definition
Density Settings is the Salesforce Setup page that controls the default visual density of Lightning Experience: Comfy (more whitespace, larger row heights, easier-to-click targets) or Compact (tighter spacing, more data on screen, denser tables). The org-wide default applies to users who have not personally adjusted; individual users can override their preference through the user settings menu in the Lightning header. Most orgs configure the default based on user population (sales reps lean Comfy, support agents working many records lean Compact) and let users override personally.
Density Settings exists because Lightning Experience renders the same data very differently at different density levels. A list view that shows 10 records per page at Comfy density shows 20 at Compact. A record detail page that requires a scroll at Comfy fits in one screen at Compact. The trade-off is real: Comfy is easier to read and click; Compact shows more data per pixel. The right default depends on the org's user population and the dominant screen size; the per-user override accommodates individual preference.
Why Density Settings is the small UI choice that shapes daily user experience
Where Density Settings lives and what it controls
Setup, User Interface, Density Settings. The page has one primary control: the default density (Comfy or Compact). The setting applies org-wide as the default for users who have not personally adjusted. Per-user override happens through the user settings menu in the Lightning header (View > Display Density). The setting affects spacing throughout Lightning: list view row heights, record detail field spacing, related list densities, navigation bar height, button spacing.
Comfy vs Compact: what each looks like
Comfy uses generous whitespace around every UI element. List view rows are taller, field labels above input fields, sections separated by clear visual gaps. Compact tightens everything: shorter rows, field labels beside inputs in some layouts, less whitespace between sections. The difference is most visible on data-heavy pages (list views with many rows, record pages with many fields, related lists with many entries). On simple pages, the difference is subtle.
User populations and the right default
Sales reps typically prefer Comfy. They spend most of their time on individual records (Account, Opportunity) where readability matters more than data density. Support agents typically prefer Compact. They work many records simultaneously in the Service Console where seeing more data per screen reduces tab-switching. Marketing operations and analytics users vary; those working in reports and dashboards lean Compact, those working in record-heavy curation lean Comfy. Pick the default based on the majority population; the per-user override handles minority preferences.
Per-user override and the persistence behavior
Users override the default through View > Display Density in the user settings menu. The override persists per user across sessions and devices; a rep who picks Compact on their laptop sees Compact on their tablet too. The override survives org-wide default changes; users who set their preference keep it when admins switch the org-wide default. This matters for change management: switching the org-wide default does not affect existing users who have customized; only new users and users who never customized see the new default.
Mobile and the responsive interaction
The Salesforce Mobile App renders independently of Density Settings; mobile uses its own touch-optimized density that prioritizes target size for finger interaction. Density Settings affects only desktop Lightning Experience. Tablet browsers usually render as desktop, so Density Settings does apply there. The pattern: Density Settings shapes desktop, mobile is its own thing. Test on representative devices before declaring the density choice done.
Accessibility and the readability trade-off
Comfy density supports accessibility better than Compact. Larger touch targets, more whitespace between elements, clearer visual hierarchy aid users with vision or motor accessibility needs. Compact density packs more data on screen but reduces accessibility margins. Most orgs subject to accessibility compliance (US federal, EU public sector, broader WCAG-driven contexts) default to Comfy and educate users on the Compact override for those who want it. The default-Comfy stance is the safer accessibility position.
Audit and the periodic preference review
Density Settings is one of the lowest-traffic Setup pages but deserves periodic review. Annual audit: confirm the org-wide default still matches the dominant user population; survey a sample of users on their preference; consider if user-population shifts (acquisition of a service-heavy team, expansion into accessibility-required market) change the right default. The change is small but the user-experience impact is visible; the audit catches drift between the configured default and current reality.
How to pick the right Density Setting for the org
The pattern: identify the dominant user population, set the default to match their preference, let per-user override handle minority preferences. The cost is minimal; the user-experience impact compounds across thousands of daily sessions.
- Survey the user population on density preference
Quick survey of representative users from each role. Sales reps, support agents, marketing ops, executives. The data drives the default decision.
- Open Setup, User Interface, Density Settings
The configuration is a single radio button choice between Comfy and Compact.
- Set the org-wide default to match the dominant population
Comfy for sales-rep-dominated orgs, Compact for service-agent-dominated orgs. When unsure, default to Comfy for accessibility.
- Communicate the per-user override path to users
View > Display Density in the user settings menu. Users who prefer the non-default option need to know how to switch.
- Test on representative devices (laptop, large monitor, tablet)
Density renders differently per screen size. Confirm the choice works across the org's actual device mix.
- Document the choice and the rationale
Admin documentation. Future admins should understand why the org defaulted to Comfy or Compact.
- Audit annually as user population evolves
User-population shifts may change the right default. The annual audit catches the drift.
Generous spacing, easier to read, better for accessibility, common for sales-rep orgs.
Tighter spacing, more data per screen, common for service-agent orgs.
Each user can pick their preference through View > Display Density.
Salesforce Mobile App ignores Density Settings; uses touch-optimized density.
Review as user population evolves; the right default can shift over years.
- Per-user overrides persist across org-wide default changes. Users who customized keep their preference; only new users and uncustomized users see the new default.
- Density Settings affects desktop only. The Salesforce Mobile App uses its own density independent of this setting.
- Comfy is more accessible than Compact. Orgs subject to accessibility compliance should default to Comfy unless there is a strong reason otherwise.
- Switching the org-wide default does not retroactively change customized users. Communication is needed if you want all users to experience the new default.
- The setting is low-traffic and easy to forget. The annual audit cadence catches drift between the configured default and current user population.
Trust & references
Cross-checked against the following references.
- Density Settings referenceSalesforce
- Lightning Experience overviewSalesforce
Straight from the source - Salesforce's reference material on Density Settings.
- Density SettingsSalesforce Help
- Lightning ExperienceSalesforce Help
- Accessibility OverviewSalesforce Help
Hands-on resources to go deeper on Density Settings.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is the primary benefit of Density Settings for Salesforce administrators?
Q2. Can a Salesforce admin configure Density Settings without writing code?
Q3. In which area of Salesforce would you typically find Density Settings?
Discussion
Loading discussion…