Mini Page Layout
A Mini Page Layout is the legacy Salesforce Classic configuration that defined the contents of the hover-detail popup shown when users hovered over a record name in a list view, related list, or lookup.
Definition
A Mini Page Layout is the legacy Salesforce Classic configuration that defined the contents of the hover-detail popup shown when users hovered over a record name in a list view, related list, or lookup. Each Mini Page Layout selected a subset of fields from the full Page Layout and rendered them in the hover popup, letting users preview a record without navigating to it. The configuration lived under each object''s Page Layout edit screen and could be customized per record type.
Mini Page Layouts are a Classic-only concept. Lightning Experience replaced the Mini Page Layout with the Compact Layout, which serves the same purpose (drive hover details and highlight panels) but with a unified configuration that also feeds the Highlights Panel, the Salesforce mobile view, and search-result previews. Orgs migrating from Classic to Lightning typically drop Mini Page Layouts entirely and configure Compact Layouts as the modern equivalent. Mini Page Layout references in legacy documentation are historical context only.
Mini Page Layout vs. Compact Layout vs. Hover Detail
The Classic hover-detail popup
In Salesforce Classic, hovering over a record name in a list view or related list opened a small popup with a subset of the record''s fields. The Mini Page Layout controlled which fields appeared in this popup. Admins configured the layout from the Page Layout edit screen by clicking Mini Page Layout and picking a subset of the layout''s fields.
Compact Layout as the Lightning replacement
Lightning Experience replaced the Mini Page Layout with the Compact Layout, configured under Setup, Object Manager, Compact Layouts. The Compact Layout drives the same hover-detail popup plus the Highlights Panel on record pages, the mobile record view, and the search-result preview. Unifying these surfaces under one configuration is the main Lightning improvement.
Per-record-type variants
Both Mini Page Layouts (Classic) and Compact Layouts (Lightning) support per-record-type variants. An Opportunity record type for New Business might show Amount and Close Date; the Renewal record type might show Renewal Date and Ramp Schedule. The platform picks the right layout per record type at render time.
Migration from Classic to Lightning
Orgs cutting over from Classic to Lightning typically retire Mini Page Layouts. The Compact Layout configuration replaces them; the field-set choice often differs because the Compact Layout drives more surfaces (Highlights Panel, mobile, search) than the Mini Page Layout did. Plan a fresh design when migrating; don''t just copy field sets.
Where Mini Page Layouts persist
Orgs still operating in Salesforce Classic (a shrinking population) continue to use Mini Page Layouts. The configuration remains in Setup; Classic users still see the hover popup driven by it. Once the org switches to Lightning, the Mini Page Layout configuration becomes dead metadata.
Mobile and search consistency
Mini Page Layouts only drove the Classic hover detail. Compact Layouts drive multiple surfaces simultaneously, which is why the field selection requires more thought. A field that''s great for a hover preview may be excessive in the Highlights Panel or on a small mobile screen.
Cert exam relevance
Older Admin and Sales Cloud Consultant exams referenced Mini Page Layouts. Current exams cover Compact Layouts; Mini Page Layouts appear only in legacy context questions. Knowing that Compact Layout replaced Mini Page Layout is enough for any modern exam mention.
Migrate Mini Page Layouts to Compact Layouts
Migration is a one-time pass per object. Plan a fresh field-set design rather than copying the Mini Page Layout directly.
- Inventory existing Mini Page Layouts
Setup, Object Manager, each object, Page Layouts, find the Mini Page Layout configuration. Document the field sets per record type.
- Identify the per-object Compact Layout
Setup, Object Manager, the object, Compact Layouts. Open or create the layout.
- Pick the right field set for Lightning
The Compact Layout drives Highlights Panel, mobile, search, and hover. Pick fields that work across all these surfaces, not just the hover popup.
- Assign per record type
Use Compact Layout Record Type Assignments to map each record type to the appropriate Compact Layout.
- Verify in Lightning
Switch to Lightning Experience. Verify the Highlights Panel, hover preview, and search results all show the expected fields.
- Skip Mini Page Layout updates going forward
Once Lightning is the active UX, Mini Page Layout edits do nothing. Update Compact Layouts only.
- Mini Page Layouts are Classic-only. They do nothing in Lightning Experience.
- Compact Layout drives more surfaces than Mini Page Layout did. Picking the wrong field set affects mobile and search, not just hover.
- Migration is a one-time pass per object. Plan a fresh design rather than copying field sets blindly.
- Documentation drift is severe. Treat any Salesforce article older than 2018 referencing Mini Page Layouts as historical context.
Trust & references
Cross-checked against the following references.
- Compact LayoutsSalesforce Help
- Mini Page LayoutsSalesforce Help
Straight from the source - Salesforce's reference material on Mini Page Layout.
- Lightning ExperienceSalesforce Help
Hands-on resources to go deeper on Mini Page Layout.
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 type of data does Mini Page Layout typically work with?
Q2. What is the primary purpose of Mini Page Layout in Salesforce?
Q3. How can Mini Page Layout help improve sales performance?
Discussion
Loading discussion…