Salesforce File Size Limits: Workarounds for Large File Storage and Sharing

The Salesforce file size limit caps standard uploads at two gigabytes per file via the web interface and restricts email attachments to twenty-five megabytes, creating an operational bottleneck for teams handling large enterprise media, CAD models, software builds, or client deliverables.

When a field engineer attempts to upload a multi-gigabyte equipment inspection video or a sales representative attaches an uncompressed design portfolio to an opportunity record, Salesforce immediately halts the transaction with an upload error. Salesforce is architected primarily as a relational transaction database rather than an unstructured object repository. To maintain consistent performance across millions of concurrent database transactions, the platform places hard operational ceilings on file sizes.

These restrictions differ substantially depending on which upload pathway, interface, or programmatic API you use. For example, standard Salesforce Files in Lightning Experience support individual files up to two gigabytes, whereas legacy Notes and Attachments limit files to twenty-five megabytes. If your users interact with records through Chatter feeds, the ceiling remains two gigabytes, but if your systems transmit files through the SOAP API, base64 encoding overhead restricts the practical payload to roughly thirty-eight megabytes.

Understanding these boundaries is essential for systems architects and Salesforce administrators. The following comparison outlines verified Salesforce file size limits across primary upload channels and interfaces:

Each of these limits addresses a specific layer of the Salesforce technology stack. Knowing which limit applies to your integration or business process prevents failed uploads, unhandled exceptions, and user frustration.

• AirDrop File Size Limit: Does Apple Cap Transfers and How to Send Large FilesAirDrop has no built-in file size limit, allowing users to send files of any size as long as both Apple devices have...
• SharePoint File Size Limit: Upload Limits, Sync Constraints, and Best PracticesThe official SharePoint file size limit in SharePoint Online and Microsoft 365 is 250 GB per individual file. However,...
• Telegram File Size Limit: Upload Limits for Free and PremiumThe Telegram file size limit allows standard accounts to send individual files up to 2 GB in size, while Telegram...
• How to Use Temporary File Storage for Secure Short-Term SharingTemporary file storage hosts your files for a limited time, automatically deleting them after a set period or number of...
• Cloud Transfer: 5 Ways to Move Files Between Cloud Storage ServicesA direct cloud transfer moves files between storage providers over data center connections instead of routing gigabytes...
• How to Find the Fastest Business File Sharing: Best Methods for 2026Guide to business file sharing: Finding the fast way to share business files isn't just about bandwidth. It's about how...

More on this subject: File Sharing (156 guides)

Salesforce restricts file sizes not out of oversight, but as a deliberate architectural choice. Understanding the underlying technical and economic factors explains why attempting to turn Salesforce into an enterprise document repository leads to compounding issues.

First, Salesforce relies on a multi-tenant architecture where thousands of business instances share underlying compute, memory, and database resources. If individual users were permitted to stream massive raw video files directly into the relational database cluster, shared database buffer pools and input-output operations would degrade performance for neighboring organizations. Strict upload ceilings protect overall platform stability and ensure predictable query response times across standard CRM transactions.

Second, Salesforce enforces a strict separation between Data Storage and File Storage:

• Data Storage: Covers database records including Accounts, Contacts, Leads, Opportunities, and Custom Objects. Most standard CRM records consume an allocated two kilobytes of data storage regardless of the number of populated text fields.
• File Storage: Covers binary assets stored in Salesforce Files, ContentVersion records, Chatter feeds, email attachments, and Document records. File storage is metered on actual byte volume.

Every Salesforce edition provides a baseline file storage allocation, typically ten gigabytes per organization for Enterprise and Unlimited editions, supplemented by an additional two gigabytes per licensed user. For an organization with fifty Enterprise licenses, the total baseline file allocation is one hundred and ten gigabytes:

Base Allocation: 10 GB
User Licenses:   50 users x 2 GB = 100 GB
Total Storage:   110 GB

While standard baseline allocations are sufficient for basic PDF contracts and spreadsheet attachments, capacity evaporates quickly when teams handle multimedia files, scanned medical records, engineering schematics, or software installation packages. Storing thirty high-resolution video demonstrations or CAD packages consumes the entire storage allotment of the company.

Third, the financial cost of expanding native Salesforce storage is exceptionally high compared to modern cloud storage. Storing large documents and files directly within Salesforce records rapidly consumes file storage allocations, leading to unexpected overage expenses. Purchasing additional storage blocks directly from Salesforce typically costs hundreds of dollars per gigabyte annually. By comparison, specialized cloud workspace providers offer terabytes of high-performance storage at a fraction of that expenditure. Relying on native Salesforce storage for large enterprise assets creates an unnecessary recurring cost center.

Fourth, custom application development inside Salesforce is constrained by Apex governor limits. The Apex runtime engine restricts synchronous transactions to an Apex heap ceiling of six megabytes and asynchronous executions to twelve megabytes. When custom code attempts to inspect, transform, or upload a large file in memory, the execution immediately terminates with a System.LimitException: Apex heap size too large runtime error. This fundamental memory ceiling makes direct large-file manipulation impossible within native server-side Apex.

When organizations must keep files within Salesforce and cannot immediately adopt external storage, administrators and developers use several technical workarounds to maximize platform capacity and prevent upload timeouts.

Implementing the Lightning File Upload Component

In modern Lightning Experience, the standard lightning-file-upload component is the recommended interface mechanism for record-level uploads. Unlike custom Visualforce file inputs or custom Apex controllers, lightning-file-upload bypasses the Apex heap ceiling entirely.

The component streams binary data directly from the user's browser to the Salesforce Content server, creating a ContentVersion record and linking it to the target record-id automatically:

<template>
    <lightning-card title="Upload Project Assets" icon-name="custom:custom19">
        <div class="slds-m-around_medium">
            <lightning-file-upload
                label="Attach Large Document"
                name="fileUploader"
                accept={acceptedFormats}
                record-id={recordId}
                onuploadfinished={handleUploadFinished}
                multiple>
            </lightning-file-upload>
        </div>
    </lightning-card>
</template>

import { LightningElement, api } from 'lightning/element';
import { ShowToastEvent } from 'lightning/platformShowToastEvent';

export default class ProjectFileUploader extends LightningElement {
    @api recordId;
    get acceptedFormats() {
        return ['.pdf', '.png', '.jpg', '.jpeg', '.zip', '.mp4'];
    }
    handleUploadFinished(event) {
        const uploadedFiles = event.detail.files;
        const toast = new ShowToastEvent({
            title: 'Success',
            message: `${uploadedFiles.length} file(s) attached successfully to record.`,
            variant: 'success'
        });
        this.dispatchEvent(toast);
    }
}

Because the binary stream never enters Apex execution memory, lightning-file-upload successfully handles large files up to the two-gigabyte platform cap without exceeding memory limits.

Requesting Administrative Limit Increases

For specific legacy features, Salesforce administrators can request temporary or permanent limit increases by opening a ticket with Salesforce Support:

• Notes & Attachments: The default twenty-five-megabyte limit can be raised up to sixty-five megabytes upon administrative request with an approved business justification.
• Salesforce Knowledge: Article attachments default to five or ten megabytes, with support-approved increases up to twenty-five megabytes.

However, support cannot increase hard infrastructure ceilings. The standard limits for Chatter feeds, REST API ContentVersion records, and Email-to-Case messages are hardcoded platform boundaries that cannot be raised by logging a support ticket.

Splitting Multi-Gigabyte Archives

When project teams must deliver datasets or media libraries that exceed standard platform limits and cannot use external links, manual archive splitting serves as a fallback. Administrators and developers can compress large directories into multi-part archive volumes from the local command line.

On macOS and Linux workstations, you can package a multi-gigabyte directory into sequential archive volumes:

tar -cvf - /path/to/project-assets | split -b 1800m - project_assets.tar.part_
ls -lh project_assets.tar.part_*

The recipient downloads the split files from the Salesforce record and reassembles them using standard terminal utilities:

cat project_assets.tar.part_* | tar -xvf -

While functional for technical teams, archive splitting introduces manual friction and poor user experience for non-technical business users.

The most scalable and cost-effective approach for enterprise Salesforce teams is offloading large files to an external cloud workspace. Rather than consuming expensive Salesforce file storage or fighting two-gigabyte upload ceilings, organizations store assets in external systems and surface them inside Salesforce through structured metadata and secure share links.

Organizations typically evaluate three main external storage models:

1. Raw Object Storage (Amazon S3 or Google Cloud Storage): Storing files in raw object buckets is inexpensive on a per-gigabyte basis. However, raw buckets lack native end-user interfaces. Developers must build custom upload widgets, manage time-limited signed URL generation, implement token authentication, and maintain file preview components inside Salesforce.
2. Enterprise Document Repositories (SharePoint or Box): Integrating Salesforce with SharePoint via tools like sFiles or Files Connect allows users to view files from within records. While functional for corporate intranet files, these integrations often create rigid permission structures, require separate user licensing, and complicate external file collection from clients or partners.
3. Dedicated Intelligent Cloud Workspaces: Modern workspace platforms like Fast.io offer a comprehensive environment for teams and automated systems to collaborate on files without CRM storage overhead.

Fast.io provides persistent workspaces that integrate directly into enterprise workflows. Key technical capabilities include:

• Chunked Resumable Uploads: Fast.io handles massive files using chunked upload sessions. If an upload experiences an intermittent network interruption, transmission resumes from the last completed chunk rather than restarting from the beginning.
• Branded Share Links (Send, Receive, and Exchange): Instead of uploading files directly to Salesforce records, teams generate branded sharing options. Senders configure custom expiration dates, password protection, and per-recipient access controls. Receive links let external clients upload large files directly into an organized workspace folder without logging into Salesforce or dealing with email attachment caps.
• Per-File Version History: Every file keeps a full version history. When team members or automated systems update a proposal or technical drawing, Fast.io preserves prior versions so they can be restored at any time, and recipients always see the current version.
• Hybrid Search Engine: Fast.io indexes document contents upon arrival, combining exact full-text keyword matching with semantic retrieval. Users can locate clauses, contract figures, or metadata attributes across thousands of documents in seconds.
• Metadata Views: For structured document processing, Metadata Views turn unstructured documents into queryable databases. By describing fields in natural language, AI establishes a typed schema (such as Text, Integer, Date, or JSON) and automatically extracts key data from incoming PDFs, invoices, and contracts. Teams can review details on Metadata Views to see how document processing operates without manual OCR configuration.
• Collaborative Notes: Team members and agents can keep shared markdown notes directly beside workspace files, indexed for AI grounding, keeping context attached to project assets.

Fast.io includes workspace storage with each plan and meters AI work in credits. Monthly plans start with a 14-day free trial that requires a credit card. Paid subscriptions on the pricing plans include Starter at $9.99 a month (250 GB), Business at $49.99 a month (5 TB), and Enterprise at $199.99 a month (25 TB), providing dedicated workspace storage that eliminates Salesforce storage overage costs.

Store and Share Large Files Beyond Salesforce Limits

Create shared workspaces with branded links, chunked uploads for large assets, and per-file version history. Monthly plans start with a 14-day free trial (credit card required).

Start 14-Day Trial

Integrating external workspace storage with Salesforce does not require rebuilding your CRM data model. Technical teams implement three practical architectural patterns to connect large files to Salesforce records.

Pattern 1: Custom Workspace Link Fields

The simplest and most resilient integration pattern involves storing an external workspace link directly on standard or custom Salesforce objects (such as Account, Opportunity, or Case).

1. Navigate to Setup > Object Manager > Opportunity > Fields & Relationships.
2. Create a new custom field of type URL, named Workspace_Folder_URL__c (label: "Workspace Assets").
3. Add the field to the standard Lightning Record Page layout.
4. Place the generated Fast.io share link in the field.

Sales representatives and support agents click the link to open the external workspace in a separate browser tab, where they can view high-resolution previews, stream video files, or download assets without burdening Salesforce storage.

Pattern 2: Automating Workspace Creation via Flow and REST API

For automated operations, organizations use Salesforce Flow to generate external workspace folders and share links automatically when records reach specific lifecycle stages.

When an Opportunity stage changes to 'Closed Won' or a high-priority Case is created, a Record-Triggered Flow initiates an HTTP Callout to the Fast.io REST API:

Record Trigger (Opportunity = 'Closed Won')
      |
      v
HTTP Callout to Fast.io API
POST /current/workspace/{workspace_id}/create/fileshare/
      |
      v
Receive Share URL and Access ID
      |
      v
Update Record: Opportunity.Workspace_Folder_URL__c = Share URL

The Fast.io REST API lives at https://api.fast.io/current/. The endpoint returns a durable share link that the Flow stores back on the triggering Opportunity record, establishing an organized workspace folder without manual user intervention.

Pattern 3: Link-Based Email Delivery for Large Attachments

Salesforce limits outbound emails to a twenty-five-megabyte ceiling for the entire message, including message text, MIME headers, and base64 encoding overhead. In practice, any file larger than roughly fifteen to eighteen megabytes will fail to send through Salesforce email authoring tools.

Instead of attaching raw files to outbound emails, sales and service teams embed secure workspace share links into their email templates:

<p>Dear {!Contact.FirstName},</p>
<p>Thank you for reviewing our proposal. Because the architectural rendering and technical documentation package exceeds standard email attachment limits, you can review and download the full deliverable directly via our secure workspace portal:</p>
<p><a href="{!Opportunity.Workspace_Folder_URL__c}">Access Project Deliverables Portal</a></p>
<p>This link provides high-speed streaming for video files and instant document previews in your browser.</p>

This pattern provides two major advantages:

1. Bypasses Email Caps: Senders can share multi-gigabyte deliverables or entire project packages without worrying about corporate mail server attachment rejection.
2. Access Control: The sender can revoke access, set expiration dates, or require passwords on the share link at any time.

Offloading large files to external workspaces requires structured governance to maintain enterprise data security, audit compliance, and clean records management.

Scoping Permissions and Access Boundaries

When external workspaces store confidential client proposals, engineering blueprints, or financial audits, access controls must mirror enterprise security requirements.

Fast.io provides granular access controls configured across multiple structural tiers:

• Organization Level: Controls high-level administrative settings, billing, and member access.
• Workspace Level: Segregates assets by client account, internal department, or project engagement.
• Share Level: Grants external guests targeted access to specific folders via Send, Receive, or Exchange shares, with optional password protection and automated link expiration.

Data Protection and Audit Logging

Enterprise data protection requires verification of encryption standards and operational audit trails. In Fast.io, files are encrypted in transit with modern TLS protocols and encrypted at rest. The platform operates on cloud infrastructure partners, including Google Cloud Platform and Cloudflare, that are certified to industry-leading security standards.

For regulatory compliance and operational accountability, Fast.io maintains a detailed activity log. File uploads, renames, permission modifications, and share creation are recorded with timestamps and user identities. If a dispute arises regarding who revised a contract deliverable, administrators can inspect the activity log to verify the change history.

Streamlining External Client Intake

Collecting files from external clients is often where Salesforce workflows experience severe friction. For example, in legal case intake or insurance claims processing, clients frequently need to submit dozens of high-resolution photos, scanned records, or video evidence. Forcing clients to register for an Experience Cloud portal often results in high drop-off rates, while email submissions fail due to attachment limits.

Using a Fast.io Receive share link, organizations create a branded, secure drop-box where clients drag and drop files from any web browser without creating an account or installing software. The uploaded files flow directly into the corresponding workspace folder, leaving Salesforce storage untouched while updating the relevant CRM records through automated activity polling. This ensures client onboarding remains rapid, secure, and free from storage bottlenecks.