Search for a Salesforce export tool and you will find a dozen products that all claim to do the same thing. Try them on files and eleven of them fall over. The reason is simple and it is not marketing: exporting records and exporting binaries are two different engineering problems, and almost every tool on the market solves the first one. If your 2026 project involves attachments, documents, notes or images, that distinction decides whether you finish on time — or discover on cutover weekend that you exported a spreadsheet full of URLs.
This article is written by the team behind SFDC File Exporter, so treat the recommendation accordingly. What we can do is show our work: the criteria, how every major option scores against them, and the specific places our own tool is not the answer. Judge it on that.
Why File Export Got Harder in 2026, Not Easier
Three things converged, and together they explain why so many teams are shopping for a file export tool this year specifically.
- Org consolidation is at an all-time high. Mergers and cost reviews have teams collapsing three or four orgs into one. Records migrate with standard tooling. Files do not — and they are usually the largest single line item in storage.
- Storage costs became a board-level line. Salesforce file storage is expensive at scale, and the standard remedy is to export older content to cheaper storage and delete it from the org. That remedy requires an export you can actually verify.
- Retention rules got teeth. Under GDPR, HIPAA and an expanding set of regional regimes, "we think we exported everything" is not a defensible position. Auditors ask for evidence, which means a job log, not a folder.
The Trap Almost Everyone Falls Into
The single most common failure in Salesforce export projects is assuming that a record export includes the files attached to those records. It does not.
ContentVersion or Attachment with Data Loader and it will succeed. Open the CSV and VersionData and Body contain API URLs, not file content. You have exported a description of your files. The failure is silent — no error, no warning, just a green tick and a folder that is missing everything that mattered.Teams typically discover this after the source org has been decommissioned. We wrote up this and the other recurring failures in common Salesforce export mistakes.
Seven Criteria That Separate the Tools
These are the questions that actually predict whether an export succeeds. Score any candidate against them, ours included.
- Does it retrieve real binaries? Not URLs, not manifests — actual files on your disk.
- Does it preserve the parent record? 40,000 files called
Invoice.pdfin one folder is not an export, it is a puzzle. - Does it cover every content type? Salesforce Files and classic Attachments are different objects. Documents, Classic Notes, Enhanced Notes, rich text images and static resources are five more. A tool that only names ContentDocument silently skips the rest.
- Can you run it on demand? The native Data Export Service runs weekly at best — useless for a cutover on a fixed date.
- Where does the data physically land? Your disk, or a vendor's server?
- Can you prove the run was complete? A job history you can reconcile against org counts — or nothing.
- Who has to operate it in a year? A script is fine until its author leaves.
How Every Option Scores
An honest read of the field as it stands in 2026:
| Tool | Exports real files? | Where it falls short |
|---|---|---|
| Data Loader | No | Records only. Returns API URLs for file bodies. Excellent at the job it is designed for — CSV rows. |
| Data Export Service (native) | Partially | Weekly at best on Enterprise/Unlimited/Performance, monthly on Professional/Developer. Delivers ZIPs you match back to records by hand. Cannot be triggered for a deadline. |
| Salesforce CLI / custom scripts | Yes, if you build it | Weeks of developer time, then a permanent maintenance dependency. Becomes unowned the moment its author changes role. |
| Workbench | Not at scale | Fine for spot checks and a handful of records. Not built for bulk retrieval. |
| Cloud backup suites | Yes | Your files are staged on vendor infrastructure, and pricing is a recurring subscription sized for full-org backup — heavy if you only need file export. |
| SFDC File Exporter | Yes — purpose-built | Not a record-export tool. Pair it with Data Loader when you also need object rows as CSV. |
The full breakdown lives in Best Salesforce Data Export Tools in 2026, and the decision framework in how to choose a Salesforce data export tool.
Why SFDC File Exporter Wins on Files
Against the seven criteria, point by point:
| Criterion | SFDC File Exporter |
|---|---|
| 1. Real binaries | Yes — actual files written to your disk, not URLs |
| 2. Parent-record context | Output organised by object and record, so every file keeps its origin |
| 3. Content coverage | Files, Attachments, Documents, Classic Notes, Enhanced Notes, rich text field images, static resources |
| 4. On demand | Run instantly, or set scheduled exports |
| 5. Data residency | Salesforce → your machine. No vendor server in the path. Security architecture |
| 6. Completeness proof | Job history recording every success and failure |
| 7. Operator | Desktop UI an admin can run — no scripting, no developer dependency |
Two more things that matter in practice: there is no AppExchange package, so nothing is deployed into your org and no admin approval cycle is needed; and scoping is flexible — export by object, by list view, by a CSV of record IDs, or by a SOQL filter, which is how large migrations get split into batches that verify independently.
What Users Actually Report
From verified reviews on this site:
"The only tool I have found that works! Simple to use and faultless."
"We just migrated 3 Salesforce Orgs into one. The SFDC File Exporter was key to exporting files and attachments from each Org by date."
"Aside from the Salesforce Data Export, this is the easiest tool available to download attachments/files from Salesforce.com."
The Build-vs-Buy Maths
Every team considering a custom script should price it honestly. A Salesforce developer runs $80–$150/hour, and the API integration alone is typically two to four weeks — before retries, pagination, error handling, and the maintenance that follows forever. That is a $5,000–$20,000+ commitment for something you then own.
Against that, the licensing:
| Plan | Price | What you get |
|---|---|---|
| Free | $0 | Up to 50 files per export, basic object filter, sandbox & production. No license key needed. |
| 1 Month Pro | $49 | Unlimited exports, advanced filtering, SOQL & CSV scoping, scheduled exports |
| 3 Months Pro | $99 | As above, plus priority email support |
| 6 Months Pro | $124 | As above |
| 1 Year Pro | $149 | Best value — all Pro features for a full year |
| Agency / Team | $199 | 5 machine seats, multi-instance support, dedicated support channel |
These are one-time license purchases, not subscriptions. A single migration that would have cost a developer a fortnight is covered by the $149 annual license — roughly one hour of developer time. See full pricing for the complete comparison.
Try It Before You Pay — On Your Own Org
You do not have to take any of the above on faith, and you should not have to. The sequence we would suggest:
- Download the free version — Windows, macOS or Linux. No license key, no sign-up wall.
- Connect to a sandbox and export 50 files from a real object.
- Open the output folder. Check the files are real, that they opened, and that you can tell which record each came from.
- Open the job history and reconcile the count against your org.
- If it did what you needed, buy a license and lift the limit. If it did not, you have lost fifteen minutes.
That is the whole argument. A tool that survives step 3 on your own data is worth more than any comparison table — this one included.
Frequently Asked Questions
What is the best tool to export files from Salesforce in 2026?
For file and attachment export specifically, SFDC File Exporter. It handles the binary class that record-export tools cannot: Files, Attachments, Documents, both Note types, rich text images and static resources — organised by parent record, written to your own machine, with an auditable job history and no AppExchange package. For object rows as CSV, Data Loader or the Data Export Service remains correct.
Can Data Loader export Salesforce files and attachments?
No. It exports records, not binaries. VersionData and Body come back as API URLs, so you get a CSV describing your files rather than the files themselves.
Is SFDC File Exporter free?
Yes — a free tier with no license key, exporting up to 50 files per run with basic object filtering on both sandbox and production. Pro licenses are one-time purchases from $49 and remove the limit while adding advanced filtering, SOQL and CSV scoping, and scheduled exports.
Does it need to be installed in my Salesforce org?
No. It is a desktop app connecting over the Salesforce API — no package, no deployment, no admin approval, and no org storage consumed.
Where does my data go?
From Salesforce straight to your machine. No vendor server stages your files, which is what makes it workable under GDPR, HIPAA or client confidentiality terms. Details in the security architecture.
How long does a large export take?
It depends on total file size, your connection and your org's API limits rather than record count alone. Parallel transfers plus scoping by object, list view, CSV of IDs or SOQL filter let you split a large export into batches that finish and verify independently.
The Bottom Line
If your 2026 project is records-only, use Data Loader and stop reading. If it involves files, attachments, documents or notes — and if you will be asked to prove the export was complete — the field narrows to tools built for binaries, and that is a much shorter list.
SFDC File Exporter is free to download, exports 50 files before it asks for anything, runs on Windows, macOS and Linux, installs nothing in your org, and keeps your data on your own machine. Fifteen minutes on a sandbox will tell you more than the rest of this page. Licenses start at $49, one-time.