Does Salesforce support drag and drop upload for all file types?

Salesforce supports drag-and-drop file uploads for most common file types, including PDFs, Word documents, Excel spreadsheets, images, and plain text files. There is no strict restriction on file format for the drag-and-drop feature itself, but your org’s settings, file size limits, and storage quotas can all affect whether an upload actually completes. If you work with large files or high volumes of documents, those limits matter more than the file type. This article walks through the practical details: size limits, common upload failures, versioning behavior, and when native Salesforce uploads stop being enough.

Which file types can you actually drag and drop into Salesforce?

Salesforce Files supports drag-and-drop uploads for virtually any file type, including PDFs, DOCX, XLSX, PPTX, JPEG, PNG, MP4, ZIP, and CSV files. There is no built-in file type blocklist for the drag-and-drop interface in standard Salesforce Files. What determines whether a file uploads successfully is less about format and more about file size, your org’s content delivery settings, and any restrictions your administrator has configured.

That said, a few edge cases are worth knowing about. Executable files like EXE or BAT formats may be blocked depending on your org’s security settings. Some older Salesforce environments using the legacy Attachments system have more restrictive type handling. And if your organization uses Salesforce Shield or enhanced security policies, certain MIME types may be flagged or rejected at the platform level.

For most day-to-day operational documents, contracts, media assets, project files, and transactional records, drag-and-drop works reliably across all major formats.

Are there file size or storage limits on Salesforce uploads?

Yes, Salesforce enforces file size limits on uploads. For Salesforce Files, the maximum file size for a single upload is 2 GB. For the older Attachments system, the limit drops to 25 MB per file. Storage limits also apply at the org level, and exceeding them will prevent any new files from uploading regardless of individual file size.

Here is a quick breakdown of the key limits to be aware of:

• Salesforce Files (Content): Up to 2 GB per file
• Attachments (legacy): Up to 25 MB per file
• Org file storage: Starts at 10 GB for most editions, with additional storage purchasable
• Daily API upload limits: Apply when uploading programmatically, not through the UI
• Chatter file sharing: Limited to 2 GB per file, same as Salesforce Files

For teams doing bulk file uploads or handling large media assets, hitting the org storage ceiling is a real operational risk. Storage fills up faster than most teams expect, especially when duplicate files accumulate over time. Monitoring your storage usage in Setup is something ops teams should do regularly, not just when something breaks.

Why do some files fail to upload in Salesforce even when dragged in?

Files fail to upload in Salesforce for several reasons that have nothing to do with the drag-and-drop action itself. The most common causes are exceeding the file size limit, hitting the org’s total storage cap, browser compatibility issues, or network timeouts during a Salesforce large file upload. Permissions and sharing settings can also silently block an upload without a clear error message.

If you are troubleshooting a failed upload, work through these common causes in order:

1. Check the file size against the 2 GB limit for Salesforce Files or 25 MB for Attachments
2. Check org storage in Setup under Company Information to confirm you have not hit your limit
3. Try a different browser, as some Chromium-based browsers handle large drag-and-drop operations more reliably than others
4. Check your user permissions to confirm you have “Create” access on the Files or Attachments object for that record
5. Disable browser extensions that intercept file operations, such as download managers or security plugins
6. Test with a smaller file of the same type to isolate whether the issue is size-related or format-related

If uploads fail consistently across multiple users, the issue is almost always org-level storage or an administrator-configured restriction rather than a user-side problem.

How does Salesforce handle file versioning after a drag-and-drop upload?

Salesforce Files supports automatic versioning. When you drag and drop a file onto an existing file record, Salesforce creates a new version rather than overwriting the original. Each version is stored with a version number, timestamp, and the name of the user who uploaded it. You can view and restore previous versions directly from the file detail page.

This versioning behavior applies specifically to Salesforce Files. If you are using the older Attachments system, versioning is not supported natively. Uploading a file with the same name as an existing attachment creates a separate record, not a new version of the original.

For teams managing contracts, project documents, or any file that goes through multiple rounds of review, the versioning capability in Salesforce Files is genuinely useful. It gives you a clear audit trail without any manual effort. The limitation is that version management at scale, across hundreds of records, can become difficult to track without additional tooling.

What’s the difference between Salesforce Files, Attachments, and Documents?

Salesforce has three distinct file storage systems, and they behave differently. Salesforce Files is the modern system, supporting versioning, sharing, and large file uploads up to 2 GB. Attachments is a legacy system tied directly to specific records, with a 25 MB limit and no versioning. Documents is an older system used to store static files like logos or templates in folder-based libraries, not linked to records.

In practical terms:

• Salesforce Files is what you should use for most operational documents. It integrates with Chatter, supports version history, and handles the largest file sizes.
• Attachments still appears on older page layouts and some custom objects. It works, but it is limited, and Salesforce has been steering users away from it for years.
• Documents is best suited for internal reference files that do not need to be linked to individual records, such as branded templates or standard operating procedures stored at the org level.

If your team is still uploading files through the Attachments component on record pages, it is worth asking your Salesforce admin whether a migration to Salesforce Files makes sense. The document management features available in the Files system are significantly more capable.

When should you use a dedicated document management tool instead of native Salesforce uploads?

Native Salesforce file storage works well for simple use cases, but it starts to show limitations when your team handles high document volumes, needs structured folder organization, requires bulk file uploads, or depends on consistent file naming and metadata tagging. If you are spending time hunting for files, dealing with duplicates, or managing documents across multiple records manually, native uploads are no longer enough.

Specific signals that you have outgrown native Salesforce document handling include:

• Files are hard to find because there is no folder structure or consistent naming convention
• Duplicate files accumulate because team members upload the same document multiple times
• You need to upload large files or batches of files regularly, and the process is slow or unreliable
• Document workflows, approvals, or version reviews happen outside Salesforce in email or shared drives
• Compliance or audit requirements demand structured metadata, retention policies, or access controls beyond what native Files provides

For teams in document-intensive industries like real estate, media, automotive, or retail, these pain points tend to appear early. The volume of contracts, project files, and transactional records simply outpaces what a basic upload interface can manage. Understanding the document value model behind a structured approach helps clarify where the gaps are and what a better system looks like.

How Cartularius helps with Salesforce file uploads and document management

We built Cartularius specifically for teams that have hit the ceiling on native Salesforce document handling. It installs directly from AppExchange and runs natively inside Salesforce, so there is no platform switching, no new login, and no steep learning curve. Here is what it adds on top of what Salesforce provides out of the box:

• Structured folder organization that mirrors familiar file systems like Windows File Explorer, so your team knows exactly where documents live
• Bulk file upload support that handles large batches without the reliability issues you run into with drag and drop on native record pages
• Automatic duplicate detection to stop the same file from being uploaded multiple times across different records
• Metadata tagging and consistent naming conventions enforced at the point of upload, not after the fact
• Version control and audit trails built into the workflow, not bolted on manually
• Office 365 integration for real-time collaboration on documents without leaving Salesforce

If your team is dealing with scattered files, slow retrieval, or document workflows that live outside Salesforce, we can help you fix that quickly. Cartularius is ready to use in minutes after installation, and the interface is familiar enough that adoption happens without a training program. Check our pricing options to find the right fit for your team, or explore what the platform does in full detail on our features page.