A Salesforce storage governor limit is a hard cap that Salesforce enforces on the amount of data and files your organization can store within its platform. Unlike soft warnings, these limits are enforced at the platform level, meaning Salesforce will block new records or file uploads once your organization reaches its allocated threshold. Understanding how these limits work is essential for any team that relies on Salesforce to manage documents, contracts, or operational records at scale. The sections below break down exactly how storage is calculated, what counts toward your limits, and what your options are when you start running out of room.
Salesforce calculates storage against governor limits by dividing your total allocation into two separate buckets: data storage and file storage. Each bucket has its own cap, and the two are tracked independently. Hitting the limit in either category triggers the same result: Salesforce blocks further additions until space is freed or more storage is purchased.
Data storage covers all structured records in your org, including accounts, contacts, leads, opportunities, cases, and custom object records. File storage covers unstructured content such as attachments, Salesforce Files (ContentDocument), and documents stored in the Documents tab. Because these two pools are calculated separately, an organization can be over its file storage limit while still having plenty of data storage remaining, and vice versa.
Salesforce calculates total storage at the organization level, not the user level. Your entire org shares a single pool, which means one team uploading large files can affect every other user in the system.
Both structured records and unstructured files count toward Salesforce storage limits, but they are tracked in different pools. Data storage includes every record in your org, while file storage includes all uploaded content regardless of where it is stored within Salesforce.
The following content types count toward data storage:
The following content types count toward file storage:
One area that surprises many teams is that every version of a file counts separately. If your team uploads ten revisions of a contract, each version occupies its own space in file storage. This versioning behavior can cause file storage to grow far faster than expected, particularly in document-intensive environments like real estate or media operations.
When you hit a Salesforce storage governor limit, the platform enforces a hard stop. Users will be unable to create new records (if the data storage limit is reached) or upload new files (if the file storage limit is reached). Salesforce does not automatically archive or delete content to make room. The block remains in place until storage is freed or additional capacity is purchased.
In practice, hitting the limit creates immediate operational disruption. Sales reps cannot log new leads, support agents cannot create cases, and project teams cannot upload contracts or deliverables. For fast-paced operations teams managing high document volumes, even a brief storage block can cause measurable delays and frustration across the entire organization.
Salesforce does provide warning notifications before you reach the hard limit, but these alerts are easy to overlook in busy environments without a dedicated administrator monitoring storage health regularly.
Salesforce includes a baseline amount of data storage and file storage with every edition, but the exact allocation depends on your license type and the number of users in your org. For most Enterprise and Unlimited Edition customers, Salesforce provides 10 GB of file storage per org plus an additional 2 GB per user license. Data storage typically starts at 10 GB per org, with 20 MB added per user license.
For smaller organizations on lower-tier editions, the default allocations are significantly more limited. A small team on a Professional Edition license may find themselves approaching file storage limits relatively quickly if they are regularly uploading contracts, media assets, or project documentation.
It is worth noting that these defaults have not scaled proportionally with how teams actually use Salesforce today. In 2026, document volumes in most industries are substantially higher than when these baseline allocations were originally set, making proactive storage management more important than ever.
You can check your current Salesforce storage usage through the Setup menu. Navigate to Setup, then search for “Storage Usage” in the Quick Find box. The Storage Usage page displays a clear breakdown of both data storage and file storage, showing your total allocation, how much is used, and how much remains.
Here is a step-by-step path to find your storage usage:
The object-level breakdown is particularly useful because it helps you identify where storage is being consumed most heavily. For example, if ContentDocument records are consuming 80% of your file storage, that signals a clear opportunity to offload or archive those files.
The most effective ways to free up Salesforce storage space are to delete unused records and attachments, archive old files to an external storage system, remove duplicate content, and clean up outdated data that no longer serves an active business purpose.
Practical steps that deliver the most impact include:
For teams managing document workflow automation at scale, reactive cleanup is rarely enough. Building a regular storage audit into your operational cadence prevents limits from becoming a crisis.
Whether to buy more Salesforce storage or use an external solution depends on your volume, growth trajectory, and budget. Purchasing additional Salesforce storage is straightforward but can become expensive quickly, especially for organizations with large or rapidly growing document repositories. External storage solutions are typically more cost-effective at scale and offer greater flexibility.
Salesforce charges for additional storage in fixed increments, and the per-gigabyte cost is considerably higher than cloud storage alternatives like Amazon S3. For organizations storing a moderate number of records with occasional file uploads, buying additional Salesforce storage may be the simplest path. However, for document-intensive operations in industries like real estate, retail, or media, the math often favors an external approach as volumes grow.
The key question to ask is whether your storage needs are stable or growing. If your document volume is increasing year over year, investing in a scalable external storage architecture will almost always deliver better long-term value than repeatedly purchasing Salesforce storage add-ons.
Cartularius is purpose-built to solve the storage challenge that operational teams face inside Salesforce. Rather than forcing you to choose between paying for expensive Salesforce storage or managing a complex external system, we provide a seamless bridge between the two. Here is what that looks like in practice:
If your team is approaching Salesforce storage limits or simply wants a smarter long-term approach to document management, explore our pricing options to find the right fit for your organization.
Install Cartularius now and experience the best Salesforce document management solution and enjoy clean and structured data and optimized processes, risk-free for 30 days.