Have Salesforce file size limits changed in the latest release?

Salesforce file size limits have not changed in the latest 2026 releases. The core limit for files uploaded via Salesforce Files (ContentDocument) remains at 2 GB per file, a cap that has been in place for several years. Limits for other upload methods, such as attachments and Chatter posts, remain unchanged as well. Below, we break down exactly how these limits work across different storage types, why uploads sometimes still fail, and how to handle large file volumes inside Salesforce.

What are the current file size limits in Salesforce?

The current Salesforce file size limit for files uploaded through Salesforce Files is 2 GB per individual file. Files uploaded as classic Attachments are capped at 25 MB each, and files shared through Chatter posts follow the same 2 GB ceiling as Salesforce Files. These limits apply regardless of your Salesforce edition or license type.

Here is a quick overview of the limits by upload method:

• Salesforce Files (ContentDocument): 2 GB per file
• Classic Attachments: 25 MB per file
• Chatter file posts: 2 GB per file
• Documents (legacy tab): 5 MB per file
• Email attachments sent via Salesforce: 25 MB total per email

For most operational teams handling contracts, project files, or media assets, the 2 GB ceiling on Salesforce Files is generous enough for day-to-day use. The 25 MB cap on classic Attachments, however, can catch teams off guard if they are still using that older method for storing documents linked to records.

Which Salesforce release last changed file size limits?

The 2 GB limit for Salesforce Files was introduced several releases ago and has remained stable through Salesforce’s Spring, Summer, and Winter releases up to and including 2026. No recent release has modified the core file size limits. Salesforce’s release notes for 2025 and 2026 reflect improvements in performance, security, and AI features, but not changes to file upload caps.

This stability is intentional. Salesforce has focused recent development effort on expanding storage capacity options and improving file management capabilities rather than raising individual file size ceilings. If you are evaluating whether a specific release affected your org’s behavior, the most reliable place to check is the official Salesforce Release Notes for your current version, accessible directly from your org’s Help menu.

How do Salesforce file limits differ across storage types?

Salesforce uses several distinct storage mechanisms, and each one has its own file size rules. Understanding the difference between them prevents unexpected upload failures and helps teams choose the right method for each document type.

File Storage vs. Data Storage

Salesforce separates storage into two buckets: File Storage and Data Storage. File Storage covers everything uploaded as a Salesforce File, Attachment, or Document. Data Storage covers structured record data like contacts, opportunities, and custom objects. Files uploaded through Salesforce Files consume File Storage, not Data Storage, which matters when you are monitoring org limits.

Salesforce Files vs. Classic Attachments

Salesforce Files is the modern, recommended approach. It supports up to 2 GB per file, enables sharing across multiple records, and integrates with libraries and external storage. Classic Attachments are the legacy method, limited to 25 MB per file and tied to a single parent record. Salesforce has deprioritized Attachments for years, and most orgs have migrated or are in the process of migrating away from them.

Why do file uploads still fail even within the size limit?

File uploads in Salesforce can fail even when the file is technically within the size limit. The most common reasons are browser timeout thresholds, network instability, and API-specific limits that differ from the UI-based limits.

Specifically, watch out for these scenarios:

• API upload limits: When uploading files via the Salesforce API, the effective limit per request is often much lower than 2 GB, depending on the API version and method used.
• Slow or unstable connections: Large files require a sustained connection. A network interruption mid-upload will fail the request regardless of file size.
• Browser memory limits: Uploading very large files through a browser tab can exhaust the browser’s available memory, especially on older hardware.
• Org-level governor limits: Salesforce enforces governor limits on total data processed in a single transaction. A file upload that triggers complex automations can hit these limits and fail.
• Antivirus or proxy scanning: Corporate network tools that scan file content can interrupt uploads before they complete.

If uploads are failing consistently, checking the Salesforce debug logs and your network configuration is a practical first step before assuming the issue is a size limit problem.

What’s the difference between Salesforce file size limits and storage limits?

Salesforce file size limits define the maximum size of a single file you can upload. Salesforce storage limits define the total volume of data and files your entire org can hold. These are two separate constraints, and hitting one does not mean you have hit the other.

File Storage is allocated per org based on your Salesforce edition and the number of user licenses. As a baseline, most orgs receive 10 GB of File Storage plus an additional allotment per license. Data Storage is calculated separately and covers record-level data. You can purchase additional storage from Salesforce if your org approaches its limits, and the pricing is expressed per GB per month.

For document-intensive teams, the storage limit is typically the more pressing constraint over time. A single 2 GB file is technically allowed, but uploading hundreds of large files will exhaust your File Storage allocation faster than smaller, well-organized documents would. Understanding this distinction helps you plan ahead rather than react when storage warnings appear. You can explore document management features that help control storage consumption at the workflow level.

How can large file volumes be managed inside Salesforce?

Managing large file volumes inside Salesforce requires a combination of smart organization, storage hygiene, and the right tooling. The default Salesforce Files experience gives you the infrastructure, but without a deliberate approach, files accumulate quickly and become hard to find or govern.

Here are the most effective strategies:

1. Use Libraries to organize files by type or project: Salesforce Content Libraries let you group related files and control access by role, which reduces duplicate uploads and makes retrieval faster.
2. Set naming conventions and metadata standards: Consistent file names and populated metadata fields make search reliable. Without this, teams waste time hunting for documents that are technically stored but practically lost.
3. Automate file routing with Flows: Salesforce Flow can automatically attach incoming documents to the correct record based on field values, removing the manual step that leads to misplaced files.
4. Archive or delete outdated files regularly: Stale files consume storage without providing value. A periodic review process, even a simple one, keeps your org lean.
5. Integrate external storage where appropriate: For very high file volumes, connecting Salesforce to an external storage provider through a supported integration reduces pressure on your internal File Storage allocation.

Teams that build these habits early avoid the document chaos that slows operations down and makes audits painful. If you want to understand the strategic thinking behind sustainable file organization, our Document Value Management model explains the framework we use.

How Cartularius helps you manage Salesforce file organization

Cartularius is built directly inside Salesforce, which means you get structured document management without switching tools or rebuilding workflows from scratch. We designed it specifically for teams that deal with high document volumes and need clarity, not more complexity.

Here is what Cartularius brings to the table:

• Automated document routing: Files are linked to the right record automatically, based on rules you define, so nothing ends up in the wrong place.
• Duplicate detection: Cartularius flags redundant files before they pile up and inflate your storage usage.
• Real-time Office 365 collaboration: Teams can co-edit documents without creating multiple versions or email chains full of attachments.
• Storage visibility: See exactly what is consuming your File Storage and where the biggest opportunities to reclaim space are.
• Compliance-ready structure: Documents are organized and retained in a way that supports audit readiness across industries like real estate, media, and retail.

If your team is hitting storage ceilings, losing time searching for files, or dealing with version confusion, Cartularius gives you the structure to fix that inside the Salesforce environment you already use. Check our pricing options to find the plan that fits your team size and document volume.