File
A File in Salesforce is the modern, user-facing name for content stored through the Salesforce Files framework — internally represented by the ContentDocument and ContentVersion objects.
Definition
A File in Salesforce is the modern, user-facing name for content stored through the Salesforce Files framework — internally represented by the ContentDocument and ContentVersion objects. Each File is a ContentDocument record that points to one or more ContentVersion records (one per uploaded version), allowing version history, in-place updates, and previews. Files are linked to records through the ContentDocumentLink junction object, which means a single File can be shared with many records, many users, and many groups, each with its own access level (Viewer, Collaborator, or Owner). Files also support libraries (Workspace), folder hierarchies, follow notifications, sharing settings inherited from the parent record, in-browser previews for common formats (PDF, Office, images), external sync via Salesforce Files Connect (SharePoint, Box, Google Drive), and integration into Chatter posts, Email Messages, Cases, Knowledge Articles, and Experience Cloud sites. Files replaced the legacy Attachment object as the recommended way to store any file uploaded into Salesforce.
In plain English
“A File in Salesforce is any document, image, or other file you upload — like a PDF contract, a customer photo, a slide deck. Unlike the older Attachment feature, one File can be linked to many records (so you don't store ten copies of the same contract on ten Opportunities), supports version history, and shows a preview without making you download it.”
Worked example
A solutions consultant uploads a 4 MB pricing PDF named "2026_pricing.pdf" through the Files tab in Salesforce. Behind the scenes, Salesforce creates one ContentDocument record (the File) and one ContentVersion record holding the actual binary. She then attaches the same File to three open Opportunities by clicking "Attach File" on each Opportunity — Salesforce creates three ContentDocumentLink records pointing the single File at the three records. A month later she replaces the PDF with a 2027 version by uploading directly to the existing File — Salesforce creates a second ContentVersion under the same ContentDocument, preserving the prior version. All three Opportunities now show the new file, no re-attachment needed, and version 1 remains accessible from the version history.
Why File matters
The Files data model has three layers: ContentDocument (the parent record that represents the File as users see it), ContentVersion (one row per uploaded or replaced version, holding the actual binary in VersionData), and ContentDocumentLink (the junction connecting a File to a record, user, or library). When inserting a File via API, you create a ContentVersion — Salesforce automatically generates the parent ContentDocument and links it through ContentDocumentLink. Querying Files for a specific record requires joining through ContentDocumentLink with LinkedEntityId set to the record Id.
File sharing is governed by a combination of the parent record's sharing model and the explicit ContentDocumentLink access level. A File linked to a record with ShareType = 'V' (Viewer), 'C' (Collaborator), or 'I' (Inferred — inherits from parent) determines what each user can do. A File can be marked Private (visible only to its owner), or set to Internal Use, External Use, or Allow public access — each tier expands or restricts visibility through Experience Cloud sites and Public Links. This flexibility is powerful but routinely confuses admins migrating from the simpler Attachment model.
Files count against File Storage like Attachments do, but with one subtle benefit: sharing the same File across many records does not multiply storage — only the ContentVersion binary counts once, regardless of how many ContentDocumentLink records reference it. This is one of the best reasons to migrate from Attachments to Files at scale. ContentVersion supports binaries up to 2 GB (depending on edition), with chunked uploads via the Bulk API for files over the standard REST limit.
How organizations use File
Maintains a single library of current sales collateral (decks, one-pagers, ROI calculators) as Files, with controlled sharing to all sales reps through Library Membership. When a deck is updated, every rep sees the new version automatically — no need to re-distribute by email.
Receives screenshots, log files, and attached documents from customers as part of Cases through Email-to-Case (Enhanced Email). Each attachment lands as a File linked to the Email Message and visible in the Case Feed, with previews rendered in-browser so agents don't have to download every screenshot.
Stores project blueprints in SharePoint but exposes them as External Files inside Salesforce on each Account and Project record. Users see and search the files natively in Salesforce; the binary lives in SharePoint, governed by the existing IT permission model.
Trust & references
Straight from the source — Salesforce's reference material on File.
- Salesforce Files OverviewSalesforce
Discussion
Loading discussion…