Is there any limit on the creation of record types?

Yes — Salesforce imposes limits on Record Types per object. The exact ceilings depend on the Salesforce edition and have changed over time, so always confirm against the current Salesforce limits documentation. The widely-cited number is 200 Record Types per object in Unlimited Edition, with lower caps in Professional and Enterprise. There are also business limits driven by what makes practical sense.

Standard limits (current Salesforce documentation)

These numbers reflect Salesforce’s published per-object limits and are subject to change. Salesforce sometimes raises caps for specific customers via Support, but the platform default is what governs admin work day-to-day.

What counts toward the limit

The count is per object. So:

• Account can have 200 Record Types
• Opportunity can have 200 Record Types
• Each custom object can have 200 Record Types
• These are independent — they don’t share a pool

Inactive Record Types still count toward the limit. Deleted Record Types don’t (after they’re fully purged).

Practical guidance — most orgs don’t need anywhere near this

In practice, you should treat the 200 cap as effectively unreachable. If you’re approaching it, your data model is wrong. Healthy orgs typically have:

• 2-6 Record Types per business-critical object (Account, Opportunity, Case, Lead)
• 0-2 for most custom objects

Each Record Type adds maintenance overhead: a page layout per profile assignment, picklist configuration, picklist value filtering, validation rule complexity. The cost compounds.

Signs you have too many Record Types

• You can’t remember what each Record Type is for
• Multiple Record Types differ only in one field’s value
• New Record Types are created instead of adjusting an existing one
• Reports group by Record Type and show very small distributions per category
• Onboarding new admins takes forever because of “which Record Type do I pick”

When you see these signs, consider consolidating — most “I need a new Record Type” requests are really “I need a different picklist value” or “I need a slightly different page layout for one team,” which can be solved without proliferating Record Types.

Picklist value limits also apply

Each Record Type also has limits on picklist values — though this is more about the underlying picklist definition than the Record Type itself. A picklist field generally has 1,000 values, and a global value set has 1,000 active values. Record Types can filter from these but can’t exceed them.

Limits adjacent to Record Types

When you create Record Types, you also touch other limits:

A heavy Record Type strategy compounds page-layout count quickly. If you have 10 Record Types × 5 Profiles, you may need 50 layout assignments to manage.

Hard limits vs governance

Salesforce’s hard cap is the technical ceiling. Most teams hit governance limits long before — i.e., your CoE or release-management process refuses to approve another Record Type because the model is sprawling. Treat the 200 limit as a footnote and govern based on practicality.

Person Accounts caveat

Person Accounts (when enabled) consume one of Account’s Record Types implicitly — the “Person Account” Record Type. This counts against the Account limit. Plan accordingly.

Confirming current limits

Always confirm against the active Salesforce Limits Quick Reference or Setup → System Overview:

• Limits shift between releases (mostly upward, rarely downward)
• Specific orgs may have negotiated higher caps
• Edition upgrades retroactively raise limits for existing data (you don’t lose Record Types when downgrading, but you may exceed the new cap)

Bottom line

Yes there’s a limit — 200 Record Types per object in most editions today, 3 in Professional. But practical limits (page layouts, picklist complexity, admin overhead) usually constrain you long before the platform does. Use Record Types deliberately, not prolifically.

Verified against: Salesforce Help — Salesforce Limits and Record Types. Last reviewed 2026-05-17.