The standard Salesforce file size limit for uploaded documents is 2 GB per file when using Salesforce Files (the modern content storage system). This applies to most standard upload methods in Lightning Experience. However, the limit varies depending on how you upload, which Salesforce edition you use, and whether you are working through the UI, API, or a third-party tool. The sections below break down each scenario so you know exactly what to expect.
Salesforce does not apply different size limits based on file type. Whether you are uploading a PDF contract, a video file, a spreadsheet, or a ZIP archive, the same 2 GB per-file ceiling applies across the board in Salesforce Files. What does vary is how certain file types behave after upload, particularly around previewing and rendering inside Salesforce.
For example, Salesforce can generate in-browser previews for common document formats like PDFs and Office files, but large media files such as high-resolution video or audio may upload successfully while offering no native preview. This is worth knowing if your team relies on in-platform previews as part of a review or approval workflow. The upload itself will complete, but the experience afterward may differ.
If your team works with legacy Salesforce features like Attachments or Documents (the older storage objects), the file size limit drops significantly to 25 MB per file. These older objects are still present in many orgs but are not recommended for new document workflows.
When a file exceeds the applicable Salesforce file size limit, the upload fails, and Salesforce returns an error message. The file is not partially saved or queued. The upload simply stops, and the user needs to either compress the file, split it, or find an alternative upload method before trying again.
This can be a real friction point for teams working with large assets like video files, high-resolution images, or bundled project archives. The error message itself is usually straightforward, but without context, users may not immediately understand why the upload failed or what the actual limit is.
There is also a subtler issue: even if a file falls under the 2 GB limit, it may still fail if your org has hit its overall file storage quota. Salesforce allocates storage at the org level, and once that pool is exhausted, new uploads are blocked regardless of individual file size. Monitoring your org’s storage usage regularly is a good habit, especially in document-heavy operations.
Salesforce allocates file storage at the org level, and the base amount you receive depends on your edition. Essentials and Professional editions typically receive a smaller storage pool, while Enterprise and Unlimited editions come with a more generous baseline. Salesforce calculates storage as a per-user allocation that adds up across your licensed seats.
Here is a general breakdown of how storage is structured:
Additional storage can be purchased if your org runs out. Salesforce also offers a Content Deliveries feature and external storage integrations to help orgs manage large volumes without consuming their primary storage quota. Understanding your edition’s limits is an important step before scaling up document workflows.
For files that approach or exceed Salesforce’s upload limits, the most reliable approach is to use chunked uploading via the Salesforce API, which breaks large files into smaller segments and reassembles them after transfer. This method handles files that would otherwise time out or fail through the standard browser-based interface.
For users who prefer not to work with APIs directly, there are a few practical alternatives:
For teams that regularly work with large files, a drag-and-drop upload experience built on top of Salesforce can make a significant difference. Dragging files directly into a record view is faster and more intuitive than navigating file dialogs, especially when processing high volumes of documents.
When uploading files through the Salesforce REST or SOAP API, the effective limit depends on the method used. Standard API calls support files up to 2 GB, but this requires multipart upload handling. Simpler API requests that embed file content directly in the request body are typically capped at much lower thresholds, often around 50 MB.
For bulk file operations, Salesforce’s Bulk API is designed for high-volume data, not binary file content, so it is not suitable for uploading large documents directly. Teams handling bulk file uploads typically rely on custom integrations or middleware that manages chunked transfers and error handling at scale.
It is also worth noting that API rate limits and governor limits in Salesforce can affect large upload jobs. If your integration is uploading dozens of large files in quick succession, you may hit execution time limits or heap size limits depending on how the logic is structured. Designing bulk upload workflows with retry logic and batch sizing in mind helps avoid these issues.
Third-party document management tools built on Salesforce can extend or work around native file size constraints in several ways. Some tools route large files to external storage systems like SharePoint or Amazon S3 while keeping the file reference visible inside Salesforce. Others implement their own chunked upload logic to handle files that would otherwise fail through the standard interface.
The key advantage of a well-designed third-party tool is that it abstracts the complexity away from the end user. Instead of knowing whether a file is 500 MB or 1.8 GB and adjusting behavior accordingly, users simply upload the file and the tool handles the rest. This is particularly valuable in fast-moving operational environments where users should not need to think about infrastructure constraints.
Some tools also add features like duplicate detection, automatic tagging, version control, and folder-based organization, which address problems that go beyond file size alone. When evaluating options, it is worth looking at how a tool handles both the technical limits and the broader document workflow experience.
You should reconsider your Salesforce document storage strategy when your org is consistently hitting storage limits, when users are regularly encountering upload failures, or when your document volumes have grown significantly since your original setup. These are signs that the default configuration is no longer aligned with how your team actually works in 2026.
Other signals that it is time to reassess include:
A document storage strategy review does not have to be a major project. Starting with an audit of what is currently stored, how it is organized, and what the actual usage patterns are will give you a clear picture of where the gaps are. From there, decisions about additional storage, external integrations, or a more structured document management approach become much easier to make.
Managing file size limits, storage quotas, and bulk uploads inside Salesforce gets much easier when you have the right layer on top of it. That is exactly what we built Cartularius to do. Rather than working around Salesforce’s native constraints manually, Cartularius gives your team a structured, intuitive document management environment that lives entirely inside Salesforce.
Here is what that looks like in practice:
If your team is running into file size issues, storage limits, or just general document chaos inside Salesforce, we would love to show you how Cartularius handles it. Explore our pricing or see all features 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.