Storage & API Calculator
Enter the number of user licenses and pick a Salesforce edition once — the same inputs drive Data Storage, File Storage and the daily API request allocation. Every extra user license adds to all three pools.
The per-license values come from the Data Storage, File Storage and API Request Limits pages.
One set of inputs drives all three calculators — change the license count once and Data Storage, File Storage and API requests all update together.
Note: Results are an estimate of the base org allocation plus per-license allocation. Storage excludes purchased add-on blocks; API totals exclude purchased API Call Add-Ons — both are added on top of the figures shown here. The API allocation uses the formula
100k + (licenses × calls per license) + add-ons; Developer orgs get a flat 15k calls/24h.
Integration limits
Storage is only half of the sizing story — the limits below are the ones that most often shape an integration design at the CTA Review Board. Values are for Unlimited/Performance editions unless noted; most have an add-on to raise them.
| Area | Limit | Source |
|---|---|---|
| Apex callouts | 100 callouts per transaction; 120 s cumulative timeout | Apex governor limits |
| Apex callout payload | 6 MB heap (sync) / 12 MB (async) caps response size you can hold | Apex governor limits |
| Platform Events | 50k delivered events / 24 h; 250k published / hour | Platform Events |
| Change Data Capture | 50k delivered notifications / 24 h; no publishing limit | Change Data Capture |
| CometD subscribers | 2k concurrent clients (hard limit) | Platform Events |
| Salesforce Connect | 200 external objects/org; 100k rows retrieved / hour; OData callouts 20k / hour | Salesforce Connect |
| Web-to-Lead / Web-to-Case | 500 leads & 5,000 cases per 24 h; 50k combined queue | Feature limits |
| Outbound email | 5,000 external addresses per day | Feature limits |
Tip: When a requirement exceeds one of these limits, that is your cue to move from real-time callouts to an asynchronous or batch pattern (Bulk API, Platform Events, middleware) — see Integration patterns.