Talk to Expert

Salesforce Supported File Types, Limits & Best Practices

Share this Article:

Salesforce file storage limits
AI-Powered Reading

Explore This Article with AI

Get an instant summary, ask questions, or go deeper-open this page in your favourite AI tool in one click.

Thank you for reading this post, don't forget to subscribe!

Understanding Salesforce file storage limits is essential for avoiding upload errors, storage issues, and compliance problems in your org. However, every admin eventually encounters an unexpected upload error or a storage limit. Understanding Salesforce-supported file types, size limits, and best practices is crucial for maintaining a stable and compliant organisation.

 

Salesforce File Storage Limits: Supported File Types and Storage Rules

Understanding exactly which file types Salesforce supports is crucial. Let’s look at the details.

Salesforce Files — built on ContentDocument and ContentVersion — accepts virtually every mainstream business format. This includes documents (.pdf, .docx, .xlsx, .pptx, .txt), images (.jpg, .png, .gif, .svg), audio and video (.mp3, .mp4, .mov), compressed files (.zip, .rar), and web formats (.html, .xml, .json). However, Salesforce permanently blocks executable and script-based formats for security reasons — including .exe, .bat, .vbs, .msi, .scr, and standalone .js files. This blocklist is enforced at the platform level and cannot be overridden by any admin, developer, or AppExchange app..

Salesforce File Upload Limits Explained

Salesforce Files (ContentVersion) — UI & API 2 GB per file
Classic Attachments (Attachment object) 25 MB per file
Documents Object 5 MB per file
EmailMessage Attachments 25 MB total per email

Org Storage Limits

Salesforce allocates file storage based on your edition. Enterprise Edition organisations receive a 10 GB base plus 2 GB per-user license. When your org hits its storage ceiling, all uploads fail — including those triggered by Flows and Apex. Monitor usage under Setup → Company Information. When approaching Salesforce file upload limits, org storage monitoring becomes critical for avoiding system failures.

Best Practices for Salesforce File Management

Use Validation Rules on ContentVersion to restrict unwanted file types and reduce storage bloat. Run regular SOQL audits on ContentDocumentLink to identify and delete orphaned files that are not linked to any record. For orgs approaching storage limits, export and archive old files before deleting them to maintain a clean backup.

Bulk Export Any Salesforce File Type with Files Downloader

When exporting files from Salesforce, most native tools provide only file names or metadata rather than the files themselves. In these scenarios, Files Downloader offers an effective solution. Built entirely on the Salesforce platform, Files Downloader gives admins a point-and-click way to pull thousands of files off any standard or custom object — all in their native formats. Whether you need contracts saved as PDFs, customer photos stored as JPEGs, or financial data in Excel, every file arrives exactly as it was originally saved, packaged inside a structured ZIP folder alongside a CSV report that maps each file to its source record.

What makes it different from generic export tools is where the processing happens — inside your org, not on a third-party server. That means your security policies stay intact, your data never crosses an unfamiliar network boundary, and your compliance posture remains untouched throughout the entire export process. Understanding Salesforce file upload limits helps admins manage storage proactively and avoid unexpected upload failures.

[Book a Free Demo] | [View Pricing] | [Install on AppExchange]

Table of Contents

Salesforce supports a wide range of file types including documents (PDF, DOCX, XLSX, PPTX), images (JPG, PNG, GIF, SVG), audio and video files (MP3, MP4, MOV), compressed files (ZIP, RAR), and web formats (HTML, XML, JSON). However, Salesforce permanently blocks executable and script-based file types like EXE, BAT, VBS, MSI, and standalone JS files for security reasons. These restrictions are enforced at the platform level and cannot be overridden.

Salesforce Files (ContentVersion) supports up to 2 GB per file when uploaded via UI or API. Classic Attachments are limited to 25 MB per file, the Documents object allows up to 5 MB per file, and EmailMessage attachments have a 25 MB total limit per email. Exceeding these Salesforce file size limits will result in upload failures.

Salesforce Enterprise Edition organisations receive a base file storage of 10 GB plus an additional 2 GB per user license. When your org reaches its storage limit, all file uploads fail - including those triggered by Flows and Apex automations. You can monitor your current storage usage under Setup → Company Information.

Key Salesforce file management best practices include using Validation Rules on ContentVersion to restrict unwanted file types, running regular SOQL audits on ContentDocumentLink to identify and remove orphaned files, and exporting or archiving old files before deletion to maintain a clean backup. These steps help reduce storage bloat and keep your org performing efficiently.

To bulk export Salesforce files while preserving their original formats, tools like Files Downloader provide a point-and-click solution built entirely on the Salesforce platform. It allows admins to download thousands of files from any standard or custom object, packaged in a structured ZIP folder with a CSV report mapping each file to its source record — without sending data to any third-party server, keeping your security and compliance policies intact.

Setup → Quick Find → Salesforce Files → General Settings → Edit → Check "Skip triggers execution and validation rules on asset files" → Save