Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
Compare

Record Type vs Page Layout

Business process variant vs field arrangement

All comparisons

Record Type

VS

Page Layout

Record Type

A record type is a Salesforce configuration that lets a single object (Account, Opportunity, Case, or any custom object) behave like multiple variants, each with its own page layout, picklist values, and business process. The same Account object can serve as a B2B customer, a partner, or a personal-account household by switching record types, and the user sees a different form and stage flow for each variant without the data living in separate tables. Record types are the layer that connects three pieces of customization: which fields show up on the page (page layout assignment), which picklist values are available (picklist value filtering), and what stage or status sequence applies (business process selection). Profiles and permission sets control which record types each user can see and create. A single object can host dozens of record types, but most production orgs settle on three to five per object before the maintenance cost overtakes the flexibility benefit.

Page Layout

A Page Layout in Salesforce is the configuration record that controls how a specific record type appears in the Salesforce UI. The Page Layout decides which fields show up on the record detail page, what order those fields appear in, which sections group them, which fields are required versus read-only, which related lists render below the detail section, and which buttons and quick actions surface on the page. Every record type on every object has a Page Layout assignment per Profile, and the combination of Profile and Record Type decides which Page Layout a given user sees when they open a given record. Page Layouts are the original UI customization mechanism in Salesforce. The platform shipped with them in the early Classic UI, and most enterprise orgs accumulated dozens of them over the years: one per major Profile per Record Type per object. The proliferation is part of the design (different users need different views) and part of the maintenance pain (a new field requires touching every Page Layout that should display it). In Lightning Experience, the Page Layout still exists but has been mostly supplemented by Lightning Record Pages, which are a separate configuration layer that can override or augment what the Page Layout produces.

Key Differences

DimensionRecord TypePage Layout
PurposeDefine different business processes per objectArrange fields, sections, and related lists on a page
Picklist ValuesControls which picklist values are availableNo control over picklist values
AssignmentAssigned to profilesAssigned to profiles per record type
Data SegmentationSegments records by type or processNo data segmentation
ReportsCan filter reports by record typeNo impact on reporting

When to use Record Type

When you need different business processes, picklist values, or page layouts per record category.

When to use Page Layout

When you need to control which fields and sections users see on a record page.