Salesforce file storage is the quieter cousin of data storage in the platform contract — and frequently the larger surprise at renewal. While data storage growth is at least visible to the operating team, file storage growth happens below the line of typical attention: PDFs attached to opportunities, screenshots dropped into case comments, contracts uploaded to accounts, presentations shared into Chatter, and the steady accumulation of email attachments captured into Salesforce by activity logging. The per-GB economics are gentler than data storage, but the volumes are typically larger, and the growth trajectory is steeper.
This guide breaks down how Salesforce file storage is priced, what the included allowances cover, where the consumption actually accumulates across the three legacy/modern storage models, and what operating and architectural moves contain the spend.
Salesforce file storage is the umbrella category that covers three distinct historical storage models still present in mature orgs: classic Attachments (the legacy Notes & Attachments model), Files (the modern Salesforce Files / ContentVersion model), and Content (the original Salesforce CRM Content model). All three count toward the file storage allowance. New uploads default to the Files model in the modern UI, but legacy Attachments persist indefinitely in older records, and Content can persist in environments that historically used the CRM Content workflows.
The actual byte count of each uploaded file is what counts toward storage — unlike data storage, file storage is not abstracted to a fixed per-record allocation. A 5 MB PDF counts as 5 MB. A 50 MB video counts as 50 MB. The implication is that file storage consumption is directly driven by the size and frequency of uploads rather than by record counts.
| Edition | Base file storage | Per-user incremental |
|---|---|---|
| Enterprise Edition | 10 GB org-wide | 2 GB per user license |
| Unlimited Edition | 10 GB org-wide | 2 GB per user license |
| Performance Edition | 10 GB org-wide | 2 GB per user license |
| Professional Edition | 10 GB org-wide | 612 MB per user license |
A 1,000-user Enterprise Edition environment receives 10 GB + (1,000 × 2 GB) = 2,010 GB of included file storage. The included allowance is generally more generous than the included data storage allowance, which is why file storage is often invisible until the environment crosses the allowance threshold and triggers add-on purchases. The crossover typically happens between years three and five of a mature deployment if no archival discipline is in place.
Incremental file storage above the included allowance is sold at list rates that typically run between $250 and $400 per GB per year. Negotiated rates after discount typically land in the $100 to $200 per GB per year band for mid-size enterprises. The per-GB economics are materially better than data storage, but the larger absolute volumes mean the category can still produce six- or seven-figure annual line items at enterprise scale.
The negotiation discipline applied to data storage applies equally to file storage: lock the rate at the master agreement, negotiate growth allowances that scale with user counts, and prevent reactive purchasing during the term.
Five upload categories drive most file storage growth in mature environments.
Email attachments captured via activity logging. When Einstein Activity Capture or Salesforce Inbox logs emails into Salesforce, the attachments come with them. A single sales rep with active email logging can produce 5 to 15 GB of email attachments annually. Multiplied across the organization, this is frequently the largest single file storage consumer.
Customer-supplied documents in Service and Sales workflows. Cases with screenshot attachments, opportunities with proposal PDFs, accounts with contract uploads — the volume varies by use case but the trajectory is consistently upward across the contract term.
Marketing assets in Marketing Cloud integrations. Image libraries, brochure PDFs, video assets, and similar marketing collateral synchronized into Salesforce produce high-volume file storage consumption that frequently grows uncontrolled.
Document generation outputs. Quote PDFs, order confirmations, generated reports, and similar dynamically produced documents accumulate as historical records of generation events. Each generation event produces a stored artifact unless retention is explicitly enforced.
Chatter and Experience Cloud uploads. Internal collaboration and community uploads accumulate across the contract term, frequently without explicit retention policies because the uploads happen across many users and many contexts.
The single largest file storage line in recent advisory work was activity-logged email attachments — 1.2 TB accumulated over 30 months in a single sales organization. The intervention was a retention policy that purged email attachments older than 18 months and excluded specified file types (images embedded in signatures) at logging time. The intervention recovered 780 GB.
500+ engagements · $420M+ in client savings · 34% average reduction.
Contact Us →The highest-leverage intervention is a retention policy enforced at the point of upload or at the point of activity capture. Email attachment retention can be defined as part of the Einstein Activity Capture configuration. Case attachment retention can be defined as part of case closure workflows. Document generation output retention can be defined as part of the generation pipeline. The retention defines a maximum age beyond which the file is moved to an external archive or deleted entirely.
The Salesforce Files connector model supports linking to externally hosted files (in SharePoint, Google Drive, S3, Box, or similar systems) without storing the file content in Salesforce. The link appears in Salesforce as a file reference, but the storage cost lives in the external system. For high-volume use cases — marketing assets, document generation outputs, large customer-supplied uploads — the external storage model is an order of magnitude cheaper than primary Salesforce file storage.
The simplest practice that contains file storage growth is a quarterly review that aggregates consumption by upload source: email logging, case attachments, opportunity uploads, marketing synchronization, document generation, Chatter. The review identifies high-growth sources before they breach the included allowance and supports targeted intervention before reactive add-on purchases are required.
The three historical file storage models (Attachments, Files, Content) carry different operational characteristics that affect both the storage consumption pattern and the operational workflow. Understanding the differences supports better intervention decisions.
Classic Attachments are the legacy model still present in older records. Each attachment is stored against a single parent record without the version control, sharing model, or collaboration features of the modern Files model. Mature environments frequently have substantial Attachment volumes that are no longer being added to but persist as historical record attachments. The migration path to Files exists but is rarely executed at scale because the migration is operationally invisible and the cost-benefit is modest in isolation.
Salesforce Files is the modern model. Files support versioning, broad sharing across multiple records, Chatter-based collaboration, and the broader workflow features that the platform has built around the ContentVersion data model. New uploads default to this model. The vast majority of new file storage consumption in modern environments lands in Files rather than Attachments.
Salesforce CRM Content is the original collaborative content model, less commonly used in modern deployments but still present in environments that adopted it during its peak. Content libraries persist with their own permission structures and metadata, which can complicate migration to a unified Files model.
Four negotiation moves consistently produce results on the file storage line at contract events.
Lock the per-GB rate at the master agreement. The rate is materially negotiable at signing and materially less negotiable mid-term.
Negotiate growth allowances that scale with user growth. An allowance that grows with user counts prevents the recurring negotiation cycle as the organization expands.
Bundle file storage into multi-product agreements. File storage frequently negotiates well when bundled with other product purchases at a master contract event, because the line is small enough that the vendor will concede on it to support the larger transaction.
Maintain price protection across the contract term. Lock the negotiated rate against list price increases for the contract term.
The clearest indicator of mature file storage discipline is the use of external storage references for high-volume use cases and a quarterly review of file storage consumption by upload source. Enterprises with both consistently keep file storage growth sub-linear relative to user growth.
File storage is a category that rewards operating discipline more than contract leverage. The per-GB economics are gentler than data storage, but the volumes are larger and the growth trajectory is steeper. The contract negotiation can lock the rate and the growth allowance, but the long-run cost trajectory is driven primarily by the upload patterns of the operating environment.
Enterprises that combine contract discipline at the master agreement with operating discipline at the upload layer — retention policies, external storage references for high-volume use cases, and quarterly consumption review — consistently keep file storage growth at sustainable rates across multiple budget cycles. Enterprises that rely only on contract negotiation without operating discipline consistently encounter reactive add-on purchases mid-term and substantial line increases at renewal.
The aggregate financial impact of file storage discipline is modest in any single budget cycle but compounds materially across a five-year horizon. Within the broader engagement portfolio that has produced $420M+ in client savings across 500+ engagements, file storage optimization regularly contributes to the 34 percent average reduction in total Salesforce spend, particularly in environments with high activity capture volumes or marketing-synchronization use cases.
One field-tested negotiation tactic per month. No vendor pitches.
Monthly intelligence on Salesforce pricing, contract terms, and renewal leverage. Built for buyers.