---
schema_version: "1"
id: cdcb3b76c8bf7409e9155343e16592ce87df6a8d7b32427d3363db8394b7368b
title: Handle Larger Datasets with Increased Apex Heap Limits
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/264-0-0/rn_apex_heap_limit.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_apex_heap_limit.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 03be01b96fc5a3d9ffecbb93a4912f611cde3453eb49f8368cc58839a14fc3e1
description: Handle larger datasets and perform more complex operations without hitting heap constraints. Increased Apex heap limits reduce the chance of encountering runtime limit errors that interrupt business processes. The Apex heap limit for synchronous transactions increases from 6 MB to 10 MB, and the limit for asynchronous transactions increases from 12 MB to 25 MB.
products:
  - Cross Cloud
release: "264"
---
# Handle Larger Datasets with Increased Apex Heap Limits

Handle larger datasets and perform more complex operations without hitting heap constraints. Increased Apex heap limits reduce the chance of encountering runtime limit errors that interrupt business processes. The Apex heap limit for synchronous transactions increases from 6 MB to 10 MB, and the limit for asynchronous transactions increases from 12 MB to 25 MB.

**Where:** This change applies to Lightning Experience and Salesforce Classic in all editions that run custom Apex or managed Apex.

**When:** Increased Apex heap limits are enabled automatically in all orgs according to the Winter ’27 release schedule. To get the major release upgrade date for your instance, go to [Trust Status](https://status.salesforce.com/), search for your instance, and click the maintenance tab.

**How:** To confirm your org’s Apex heap limits, use the [`Limits.getLimitHeapSize()`](https://developer.salesforce.com/docs/atlas.en-us.apexref.meta/apexref/apex_methods_system_limits.htm#apex_System_Limits_getLimitHeapSize) method.

If you plan to deploy features built in Winter ’27 nonproduction orgs to Summer ’26 production orgs, you can temporarily restrict nonproduction orgs to the older Apex heap limits. In a sandbox, Developer Edition, or scratch org, from Setup, enter and select **Apex Settings** in the Quick Find box. Then select **Enforce the Summer ’26 Apex heap limit**. With this setting enabled, the nonproduction org uses the lower Apex heap limits, so that you can verify that transactions succeed in Summer ’26 production environments.

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-release-notes-salesforce_release_notes-264-0-0-production-enus/550ba85b-db1a-4608-9cd4-9a65ec96e1fa/images/icon_important.png)

Important This setting is available only in Winter ’27 nonproduction orgs. In Spring ’27, the higher Apex heap limits are enforced globally regardless of the setting status.

![The “Enforce the Summer ’26 Apex heap limit” setting on the Apex Settings page in Setup.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-release-notes-salesforce_release_notes-264-0-0-production-enus/550ba85b-db1a-4608-9cd4-9a65ec96e1fa/salesforce_release_notes/images/rn_264_apex_heap_limit.png)

#### See Also

- [_Apex Developer Guide_: Execution and Governor Limits](https://developer.salesforce.com/docs/atlas.en-us.264.0.apexcode.meta/apexcode/apex_gov_limits.htm)