Salesforce supports a wide range of common file formats for bulk upload, including documents, images, spreadsheets, PDFs, and more. Most standard business file types work without issue, but there are restrictions around executable files and certain proprietary formats. File size limits and upload method also play a role in what you can push into Salesforce at scale. Below, we break down everything you need to know about bulk file uploads in Salesforce, from accepted formats and size caps to error handling and third-party options.
Salesforce accepts most standard business file formats for bulk upload. This includes PDFs, Word documents (.doc, .docx), Excel spreadsheets (.xls, .xlsx), PowerPoint files (.ppt, .pptx), plain text files (.txt), images (.jpg, .jpeg, .png, .gif, .bmp), and compressed archives (.zip). Audio and video formats like .mp3 and .mp4 are also supported, making it flexible enough for teams working with media assets.
For most operational teams, this covers the day-to-day document types you are already working with. Contracts, invoices, project files, and media assets all fall within the supported range. Salesforce stores these files as ContentDocument records (via Salesforce Files), which means they are searchable, shareable, and linkable to any Salesforce record.
One thing worth noting: Salesforce does not place restrictions based on file format alone for most common types. The bigger constraints tend to be around file size and upload method, which we cover in the sections below.
Yes, Salesforce blocks certain file formats for security reasons. Executable files such as .exe, .bat, .cmd, .com, .js (in some contexts), .vbs, and similar script-based formats are restricted. Salesforce also blocks files that could pose a cross-site scripting risk or execute code when opened. These restrictions apply regardless of upload method.
Beyond security-blocked formats, some proprietary or niche file types may not render previews inside Salesforce, even if the upload itself succeeds. For example, highly specialized design files or legacy database formats might upload fine but won’t display inline. You can still store and share them, but users will need to download the file to view it.
If you are working in an industry with specialized file types, such as automotive CAD files or media production formats, it is worth testing uploads before rolling out a bulk process. The file may upload successfully, but the in-platform experience might be limited.
Salesforce enforces a 2 GB maximum file size per individual file when uploading through Salesforce Files. For bulk uploads via the standard user interface, individual file size limits are lower and depend on your org configuration, but the platform-wide cap is 2 GB per file. Total storage is governed by your Salesforce edition and any additional storage you have purchased.
Here are the key size-related limits to be aware of:
For teams doing a Salesforce large file upload as part of a migration or bulk import, chunked uploading via the API is the most reliable method for files approaching the size limit. Trying to push very large files through the browser UI can result in timeouts or failed uploads, especially on slower connections.
When a file fails during bulk upload due to a format or size issue, Salesforce typically surfaces an error message at the file level rather than failing the entire batch. This means other files in the same upload queue can still succeed. The error message will usually indicate whether the issue is a blocked file type, a size violation, or a permission-related restriction.
In practice, error handling varies slightly depending on how you are uploading. Through the UI, you will see inline error indicators next to the failed files. Via the API, error responses come back as part of the HTTP response body, which your integration or middleware can parse and log.
A few practical tips for managing bulk upload errors:
Uploading via the Salesforce UI is the simpler, more accessible option. You can drag and drop files directly onto records, upload from the Files tab, or use the standard file upload component. It requires no technical setup and works for most day-to-day use cases. The trade-off is that it is less suited for high-volume or automated bulk uploads, since it relies on manual interaction and browser performance.
The Salesforce REST API and Bulk API offer significantly more control. You can automate uploads, handle large volumes programmatically, use chunked uploads for very large files, and integrate file delivery into broader data pipelines. The API is the right choice when you need to upload large files at scale or as part of an automated workflow.
The key practical differences come down to volume, automation, and file size handling. For occasional uploads of a few dozen files, the UI is perfectly adequate. For migrating thousands of documents, syncing files from an external system, or building a recurring upload process, the API is the more reliable path. Understanding your upload volume and frequency is the best way to decide which approach fits your team’s needs.
Yes, third-party tools can meaningfully extend what Salesforce does natively for bulk file uploads. Native Salesforce file management is functional but limited when it comes to advanced folder structures, automated tagging, drag-and-drop bulk upload experiences, and document workflow automation. AppExchange solutions are built specifically to fill these gaps without requiring you to leave the Salesforce environment.
Third-party tools typically add capabilities like:
For document-intensive teams in real estate, retail, media, or automotive, these additions make a real operational difference. Uploading files is only half the job. What you do with them after, how they are organized, who can find them, and how they connect to your Salesforce records is where the productivity gains actually come from. You can explore document management features that go beyond native upload functionality to see what is possible.
Cartularius is built natively into Salesforce, which means it works within the environment your team already uses every day. We extend Salesforce’s native file capabilities with a purpose-built document management layer that makes bulk uploads faster, more organized, and far less error-prone.
Here is what that looks like in practice:
Whether you are uploading contracts in bulk, organizing media assets, or managing transactional records across multiple teams, Cartularius turns file uploads from a chore into a streamlined step in your workflow. Our Document Value Management model is what drives the logic behind how files are organized and surfaced. You can check our pricing page to find the right plan for your team’s size and needs. Ready to stop fighting your files? Let’s talk.
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.