SALESFORCE DEVELOPER LIMITS AND

ALLOCATIONS QUICK REFERENCE

Summary About This Quick Reference

Find the most critical limits
for developing Lightning This quick reference provides common limits and allocations for Salesforce and does not cover all limits
Platform applications. and allocations. It might contain limits or allocations that don’t apply to your Salesforce org. Stated limits
aren’t a promise that the specified resource is available at its limit in all circumstances. Load, performance,
and other system issues can prevent some limits from being reached.
This guide doesn’t include limits or allocations for:
• User interface elements in the Salesforce application
• Field lengths of Salesforce objects
• Desktop integration clients
• Your Salesforce contract
Information for specific feature limits, such as the number of total and active rules in your org for Visual
Workflow, are also in Salesforce Help; see the topics for using that feature. For allocations per edition, see
Salesforce Features and Edition Allocations. Contractual limits might also apply, as per your Salesforce
contract.

Apex Governor Limits

Read up on Apex limits details in Execution Governors and Limits
Because Apex runs in a multitenant environment, the Apex runtime engine strictly enforces limits to
ensure that runaway Apex code or processes don’t monopolize shared resources.

Per-Transaction Apex Limits

These limits count for each Apex transaction. For Batch Apex, these limits are reset for each execution of
a batch of records in the execute method.
This table lists limits for synchronous Apex and asynchronous Apex (Batch Apex and future methods)
when they’re different. Otherwise, this table lists only one limit that applies to both synchronous and
asynchronous Apex.

Description Synchronous Asynchronous

Limit Limit
Total number of SOQL queries issued1 100 200

Total number of records retrieved by SOQL queries 50,000

Total number of records retrieved by 10,000

Database.getQueryLocator

Total number of SOSL queries issued 20

Last updated: January 15, 2018

Salesforce Developer Limits and Allocations Quick Reference Apex Governor Limits

Description Synchronous Asynchronous

Limit Limit
Total number of records retrieved by a single SOSL query 2,000

Total number of DML statements issued2 150

Total number of records processed as a result of DML statements, 10,000

Approval.process, or database.emptyRecycleBin

Total stack depth for any Apex invocation that recursively fires triggers 16
due to insert, update, or delete statements3

Total number of callouts (HTTP requests or Web services calls) in a 100

transaction

Maximum cumulative timeout for all callouts (HTTP requests or Web 120 seconds
services calls) in a transaction

Maximum number of methods with the future annotation allowed 50

per Apex invocation

Maximum number of Apex jobs added to the queue with 50

System.enqueueJob

Total number of sendEmail methods allowed 10

Total heap size4 6 MB 12 MB

Maximum CPU time on the Salesforce servers5 10,000 60,000

milliseconds milliseconds

Maximum execution time for each Apex transaction 10 minutes

Maximum number of push notification method calls allowed per Apex 10

transaction

Maximum number of push notifications that can be sent in each push 2,000
notification method call

Per-Transaction Certified Managed Package Limits

Certified managed packages—managed packages that have passed the security review for
AppExchange—get their own set of limits for most per-transaction limits. Certified managed packages
are developed by Salesforce ISV Partners, are installed in your org from Lightning Platform AppExchange,
and have unique namespaces.
There’s no limit on the number of certified namespaces that can be invoked in a single transaction.
However, the number of operations that can be performed in each namespace must not exceed the
per-transaction limits. There’s also a limit on the cumulative number of operations that can be made across
namespaces in a transaction. This cumulative limit is 11 times the per-namespace limit. For example, if
the per-namespace limit for SOQL queries is 100, a single transaction can perform up to 1,100 SOQL
queries. In this case, the cumulative limit is 11 times the per-namespace limit of 100. These queries can
be performed across an unlimited number of namespaces, as long as any one namespace doesn't have

2
Salesforce Developer Limits and Allocations Quick Reference Apex Governor Limits

more than 100 queries. The cumulative limit doesn’t affect limits that are shared across all namespaces,
such as the limit on maximum CPU time.

Note: These cross-namespace limits apply only to namespaces in certified managed packages.
Namespaces in packages that are not certified don’t have their own separate governor limits. The
resources they use continue to count against the same governor limits used by your org's custom
code.
This table lists the cumulative cross-namespace limits.

Description Cumulative
Cross-Namespace
Limit
Total number of SOQL queries issued 1,100

Total number of records retrieved by Database.getQueryLocator 110,000

Total number of SOSL queries issued 220

Total number of DML statements issued 1,650

Total number of callouts (HTTP requests or Web services calls) in a transaction 1,100

Total number of sendEmail methods allowed 110

Force.com Platform Apex Limits

The limits in this table aren’t specific to an Apex transaction and are enforced by the Force.com platform.

Description Limit
The maximum number of asynchronous Apex method executions (batch 250,000 or the number
Apex, future methods, Queueable Apex, and scheduled Apex) per a 24-hour of user licenses in your
period1 org multiplied by 200,
whichever is greater

Number of synchronous concurrent transactions for long-running transactions 10

that last longer than 5 seconds for each org.2

Maximum number of Apex classes scheduled concurrently 100. In Developer Edition

orgs the limit is 5.

Maximum number of batch Apex jobs in the Apex flex queue that are in 100
Holding status

Maximum number of batch Apex jobs queued or active concurrently3 5

Maximum number of batch Apex job start method concurrent executions4 1

Maximum number of batch jobs that can be submitted in a running test 5

Maximum number of test classes that can be queued per 24-hour period The greater of 500 or 10
(production orgs other than Developer Edition)5 multiplied by the

3
Salesforce Developer Limits and Allocations Quick Reference Apex Governor Limits

Description Limit
number of test classes in
the org

Maximum number of test classes that can be queued per 24-hour period The greater of 500 or 20
(sandbox and Developer Edition orgs)5 multiplied by the
number of test classes in
the org

Maximum number of query cursors open concurrently per user6 50

Maximum number of query cursors open concurrently per user for the Batch 15
Apex start method

Maximum number of query cursors open concurrently per user for the Batch 5
Apex execute and finish methods

Static Apex Limits

Description Limit
Default timeout of callouts (HTTP requests or Web services calls) in a 10 seconds
transaction

Maximum size of callout request or response (HTTP request or Web services 6 MB for synchronous
call)1 Apex or 12 MB for
asynchronous Apex

Maximum SOQL query run time before Salesforce cancels the transaction 120 seconds

Maximum number of class and trigger code units in a deployment of Apex 5,000

For loop list batch size 200

Maximum number of records returned for a Batch Apex query in 50 million

Database.QueryLocator

Size-Specific Apex Limits

Description Limit
Maximum number of characters for a class 1 million

Maximum number of characters for a trigger 1 million

Maximum amount of code used by all Apex code in an org1 3 MB

Method size limit 2 65,535 bytecode

instructions in compiled
form

4
Salesforce Developer Limits and Allocations Quick Reference API Request Limits and Allocations

Push Notification Limits

The maximum push notifications allowed for each mobile app associated with your Salesforce org depends
on the type of app.

Mobile application type Maximum notifications per app per day

Provided by Salesforce (for example, Salesforce1) 50,000

Developed by your company for internal employee 35,000

use

Installed from the AppExchange 5,000

API Request Limits and Allocations

Concurrent API Request Limits

Here are the allocations for various types of orgs for concurrent requests (calls) with a duration of 20
seconds or longer:

Org Type Limit

Developer Edition and Trial orgs 5

Production orgs and Sandbox 25

The following table lists the allocations for the total API requests (calls) per 24-hour period for an org.

Salesforce Edition API Calls Per License Type Total Calls Per 24-Hour
Period
Developer Edition N/A 15,000

• Enterprise Edition • Salesforce: 1,000 15,000 + (number of licenses X

calls per license type), up to a
• Professional Edition with • Salesforce Platform: 1,000
maximum of 1,000,000
API access enabled • Force.com - One App: 200
• Customer Community: 0
• Customer Community Login:
0
• Customer Community Plus:
200
• Customer Community Plus
Login: 10
• Partner Community: 200
• Partner Community Login: 10

5
Salesforce Developer Limits and Allocations Quick Reference API Request Limits and Allocations

Salesforce Edition API Calls Per License Type Total Calls Per 24-Hour
Period
• Employee Apps Starter: 1000
per member for Enterprise
Edition orgs
• Employee Apps Plus: 1000 per
member for Enterprise Edition
orgs

• Unlimited Edition • Salesforce: 5,000 15,000 + (number of licenses X

calls per license type)
• Performance Edition • Salesforce Platform: 5,000
• Force.com - One App: 200
• Customer Community: 0
• Customer Community Login:
0
• Customer Community Plus:
200
• Customer Community Plus
Login: 10
• Partner Community: 200
• Partner Community Login: 10
• Employee Apps Starter: 5000
per member for Unlimited and
Performance Edition orgs
• Employee Apps Plus: 5000 per
member for Unlimited and
Performance Edition orgs

Sandbox N/A 5,000,000

Increasing Total API Request Allocations

The calculation of the API request amounts based on user licenses is designed to allow sufficient capacity
for your org based on your number of users. If you need a higher amount and you don’t want to purchase
extra user licenses or upgrade to Performance Edition, you can purchase extra API calls. For information,
contact your account representative.
Before you purchase more API calls, perform due diligence of your API usage. Client applications, whether
it is your own enterprise applications or partner applications, that make calls to the API can often be
optimized to use fewer API calls to do the same work. If you use a partner product, consult with the vendor
to verify that the product makes optimal use of the API. A product that makes inefficient use of the API
incurs unnecessary costs for your company.

6
Salesforce Developer Limits and Allocations Quick Reference Chatter REST API Limits

Chatter REST API Limits

Limits protect shared resources. These are the limits for consumers of Chatter REST API.
Chatter REST API requests are subject to rate limiting. Chatter REST API has a different rate limit than other
Salesforce APIs. Chatter REST API has a per user, per application, per hour rate limit. When you exceed the
rate limit, all Chatter REST API resources return a 503 Service Unavailable error code.
For applications using a session ID from Force.com, the rate limit is per user, per hour—there isn't a
separate bucket for applications. All applications the user accesses with a session ID use this general quota.
To take advantage of the per user, per application, per hour limit, use OAuth tokens.

Note: Load, performance, and other system issues can prevent some limits from being reached.
Limits can change without notice. Applications should make efficient use of available requests and
gracefully handle the 503 error code.

Bulk API Allocations

Bulk API Allocation Limit Description
Batch Allocation You can submit up to 10,000 batches per rolling 24-hour period. You
can’t create batches associated with a job that is more than 24 hours
old. If a batch is submitted to a closed job, the batch will not be created,
however it will still count against the batch allocation as a submitted
batch.

Batch lifespan Batches and jobs that are older than seven days are removed from the
queue regardless of job status. The seven days are measured from the
youngest batch associated with a job, or the age of the job if there are
no batches. You can’t create batches associated with a job that is more
than 24 hours old.

Batch size • Batches for data loads can consist of a single CSV, XML, or JSON
file that is no larger than 10 MB.
• A batch can contain a maximum of 10,000 records.
• A batch can contain a maximum of 10,000,000 characters for all
the data in a batch.
• A field can contain a maximum of 32,000 characters.
• A record can contain a maximum of 5,000 fields.
• A record can contain a maximum of 400,000 characters for all its
fields.
• A batch must contain some content or an error occurs.

Batch processing time Batches are processed in chunks. The chunk size depends on the API
version. In API version 20.0 and earlier, the chunk size is 100 records.
In API version 21.0 and later, the chunk size is 200 records. There’s a
5-minute limit for processing each chunk. Also, if it takes longer than
10 minutes to process a whole batch, the Bulk API places the remainder
of the batch back in the queue for later processing. If the Bulk API

7
Salesforce Developer Limits and Allocations Quick Reference API Query Cursor Limits

Bulk API Allocation Limit Description

continues to exceed the 10-minute limit on subsequent attempts, the
batch is placed back in the queue and reprocessed up to 10 times
before the batch is permanently marked as failed.

Binary content • The length of any file name can’t exceed 512 bytes.
• A zip file can’t exceed 10 MB.
• The total size of the unzipped content can’t exceed 20 MB.
• A maximum of 1,000 files can be contained in a zip file. Directories
don’t count toward this total.

Bulk query number of attempts 15 attempts at 10 minutes each to process the batch. There is also a
to query 2-minute limit on the time to process the query. If more than 15
attempts are made for the query, an error message of “Tried more than
fifteen times” is returned. If the query takes more than 2 minutes to
process, a QUERY_TIMEOUT error is returned.

Bulk query number of retrieved 15 files. If the query needs to return more than 15 files, add filters to
files the query to return less data. Bulk batch sizes are not used for bulk
queries.

Bulk query results lifespan 7 days.

Bulk query retrieved file size 1 GB

Job open time The maximum time that a job can remain open is 24 hours. The Bulk
API doesn't support clients that, for example, post one batch every
hour for many hours.

API Query Cursor Limits

A user can have up to 10 query cursors open at a time. If 10 QueryLocator cursors are open when a
client application, logged in as the same user, attempts to open a new one, then the oldest of the 10
cursors is released. If the client application attempts to open the released query cursor, an error results.

SOAP API Call Limits

API Name API Limit Limit Description
create() Maximum Your client application can add up to 200 records in a single
number of create() call. If a create request exceeds 200 objects, then
records created the entire operation fails.

describeSObjects() Maximum The describeSObjects() call is limited to a maximum

number of of 100 objects returned.
objects
returned

8
Salesforce Developer Limits and Allocations Quick Reference SOAP API Call Limits

API Name API Limit Limit Description

emptyRecycleBin() Maximum Your org can have up to 5,000 records per license in the
number of Recycle Bin at any one time. For example, if your org has five
records in the user licenses, 25,000 records can be stored in the Recycle Bin.
Recycle Bin If your org reaches its Recycle Bin limit, Salesforce automatically
removes the oldest records, as long as they have been in the
recycle bin for at least two hours.

getDeleted() Limits for • If your getDeleted() call returns more than 600,000
returned records and the user is a system administrator, an
records exception EXCEEDED_ID_LIMIT is returned.
• If your getDeleted() call returns more than 20,000
records and the user is not a system administrator, an
exception OPERATION_TOO_LARGE is returned. Note that
this error is returned when more than 20,000 records
across the organization have been deleted, not just the
records viewable by the user.

login() Login request The login request size is limited to 10 KB.

size limit

login() Maximum calls The limit is 3600 calls to login() per user per hour.
per user Exceeding this limit results in a “Login Rate Exceeded” error.

merge() Merge request • Up to 200 merge requests can be made in a single SOAP
limits call.
• Up to three records can be merged in a single request,
including the master record. This limit is the same as the
limit enforced by the Salesforce user interface. To merge
more than 3 records, do a successive merge.
• External ID fields cannot be used with merge().

update() Maximum Your client application can change up to 200 records in a

number of single update() call. If an update request exceeds 200
records records, the entire operation fails.
updated

query() and Batch size WSC clients can set the batch size by calling
queryMore() limits setQueryOptions() on the connection object. C# client
applications can change this setting by specifying the batch
size in the call QueryOptions portion of the SOAP header
before invoking the query() call. The maximum batch size
is 2,000 records. However this setting is only a suggestion.
There is no guarantee that the requested batch size will be
the actual batch size. This is done to maximize performance.
The batch size will be no more than 200 if the SOQL statement
selects two or more custom fields of type long text. This is to
prevent large SOAP messages from being returned.

9
Salesforce Developer Limits and Allocations Quick Reference Metadata Limits

Metadata Limits
The following limits apply to the Force.com IDE, the Ant Migration Tool, and the Metadata API.

Limit Description
Retrieving and You can deploy or retrieve up to 10,000 files at once and the maximum size
deploying metadata of the deployed or retrieved .zip file is 39 MB. Note the following:
• If using the Ant Migration Tool to deploy an unzipped folder, all files in
the folder are compressed first. The maximum size of uncompressed
components in an unzipped folder is 400 MB or less depending on the
compression ratio. If the files have a high compression ratio, you can
migrate a total of approximately 400 MB because the compressed size
would be under 39 MB. However, if the components can't be compressed
much, like binary static resources, you can migrate less than 400 MB.
• Metadata API base-64 encodes components after they’re compressed.
The resulting .zip file can't exceed 50 MB, which is the limit for SOAP
messages. Base-64 encoding increases the size of the payload, so your
compressed payload can't exceed approximately 39 MB before encoding.

Change sets Inbound and outbound change sets can have up to 10,000 files of metadata.

SOQL and SOSL Limits

Feature Limit Limit Description
SOQL statements Maximum length of By default, 20,000 characters.
SOQL statements
Note: Long, complex SOQL statements, such as
statements that contain many formula fields, can
sometimes result in a
QUERY_TOO_COMPLICATED error. The error
occurs because the statement is expanded
internally when processed by Salesforce, even
though the original SOQL statement is under the
20,000 character limit. To avoid this, reduce the
complexity of your SOQL statement.

SOQL WHERE Maximum length of 4,000 characters.

clause SOQL WHERE clause

SOSL statements Maximum length of By default, 20,000 characters. This limit is tied to the SOQL
SOSL statements statement character limit defined for your org.

SOSL search query Maximum length of If the SearchQuery string is longer than 10,000
strings SearchQuery characters, no result rows are returned. If
string SearchQuery is longer than 4,000 characters, any
logical operators are removed. For example, the AND

10
Salesforce Developer Limits and Allocations Quick Reference Visualforce Limits

Feature Limit Limit Description

operator in a statement with a SearchQuery that’s
4,001 characters will default to the OR operator, which
could return more results than expected.

SOSL query results Maximum rows 2,000 results total (API version 28.0 and later), unless you
returned specify custom limits in the query. Previous API versions
return 200 results.

Relationship queries Relationship query • No more than 35 child-to-parent relationships can

limits be specified in a query. A custom object allows up
to 25 relationships, so you can reference all the
child-to-parent relationships for a custom object in
one query.
• No more than 20 parent-to-child relationships can
be specified in a query.
• In each specified relationship, no more than five
levels can be specified in a child-to-parent
relationship. For example,
Contact.Account.Owner.FirstName
(three levels).
• In each specified relationship, only one level of
parent-to-child relationship can be specified in a
query. For example, if the FROM clause specifies
Account, the SELECT clause can specify only the
Contact or other objects at that level. It could not
specify a child object of Contact.

FOR VIEW and FOR Maximum The RecentlyViewed object is updated every time the
REFERENCE RecentlyViewed records logged-in user views or references a record. It is also
allowed updated when records are retrieved using the FOR
VIEW or FOR REFERENCE clause in a SOQL query.
To ensure that the most recent data is available,
RecentlyViewed data is periodically truncated down to
200 records per object. RecentlyViewed data is retained
for 90 days, after which it is removed on a periodic basis.

OFFSET clause Maximum number of The maximum offset is 2,000 rows. Requesting an offset
rows skipped by greater than 2,000 results in a
OFFSET NUMBER_OUTSIDE_VALID_RANGE error.

Visualforce Limits
Limit Value
Maximum response size for a Visualforce page Less than 15 MB

11
Salesforce Developer Limits and Allocations Quick Reference Visualforce Limits

Limit Value
Maximum view state size in a Visualforce page 135 KB

Maximum size of a Visualforce email template 1 MB

Maximum file size for a file uploaded using a Visualforce page 10 MB

Maximum size of HTML response before rendering, when Visualforce page Less than 15 MB
is rendered as PDF

Maximum PDF file size for a Visualforce page rendered as a PDF 60 MB

Maximum total size of all images included in a Visualforce page rendered 30 MB

as a PDF

Maximum request size of a JavaScript remoting call 4 MB

Maximum response size of a JavaScript remoting call 15 MB

Default timeout for a JavaScript remoting call 30,000 milliseconds (30

seconds)

Maximum timeout for a JavaScript remoting call 120,000 milliseconds (120

seconds)

Maximum rows retrieved by queries for a single Visualforce page request 50,000

Maximum rows retrieved by queries for a single Visualforce page request 1,000,000
in read-only mode

Maximum collection items that can be iterated in an iteration component 1,000

such as <apex:pageBlockTable> and <apex:repeat>

Maximum collection items that can be iterated in an iteration component 10,000

such as <apex:pageBlockTable> and <apex:repeat> in
read-only mode

Maximum field sets that can be displayed on a single Visualforce page. 50

Maximum records that can be handled by StandardSetController 10,000

12