Salesforce sets a maximum limit on the number of custom fields you can create per object, and that limit depends on your org's edition. This article covers the provisioned limits by edition, the hard limits for high-volume objects like Account and Case, and how AppExchange managed package fields factor into those limits.
This article answers the question: why can't I create more custom fields on an object, and what are my options once I hit the limit? The maximum number of custom fields per object is controlled by your Salesforce edition and can't be increased by Support directly.
| Edition | Max Custom Fields per Object |
|---|---|
| Personal Edition | 5 |
| Contact Manager | 25 |
| Group Edition | 100 |
| Essentials Edition | 100 |
| Professional Edition | 100 |
| Enterprise Edition | 500 |
| Unlimited Edition | 800 |
| Performance Edition | 800 |
| Developer Edition | 500 |
Additional fields can be added beyond edition-specific limits, provided they come from a certified managed package on the AppExchange (Salesforce's marketplace for pre-built apps and add-ons). These additional fields can be installed up to the maximum hard limit per object.
For example, in Enterprise Edition you can create up to 500 custom fields per object and install an additional 400 fields from an AppExchange-certified managed package. In Unlimited Edition, you can create up to 800 custom fields per object and install an additional 100 fields from a certified managed package.
The following objects have a maximum hard limit of 900 custom fields:
The following object has a maximum hard limit of 50 custom fields:
All other objects not listed above have a maximum hard limit of 800 custom fields.
This limit can't be increased by Support. It can only be increased by upgrading editions. You can also delete unused fields to stay within the limit.
005223994

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.