How to Export Salesforce Static Resources
To export Salesforce static resources—the CSS, JavaScript, images, and zip archives that support your Visualforce pages, Lightning components, and Apex code—you need the Metadata API, not a file export tool. Static resources are a metadata component type, retrieved and deployed through Salesforce CLI or the Metadata API, the same way Apex classes, flows, and object definitions are. This is different from exporting the files and attachments tied to your business records (accounts, cases, and opportunities), which uses a completely separate tool and workflow.
Thank you for reading this post, don't forget to subscribe!How to Actually Export Salesforce Static Resources
A few native and CLI-based paths handle static resource export:
- Salesforce CLI—the standard way to pull static resources from an org into a local project, ideal for version control, code review, or migrating between orgs.
- Workbench—a free, browser-based tool that lets admins and developers browse and retrieve individual static resources without setting up the CLI, useful for one-off retrievals.
- Change Sets—for moving static resources between connected orgs (e.g., sandbox to production) as part of a broader metadata deployment, though limited to same-org-family transfers.
- Third-party DevOps platforms (Gearset, Copado)—for teams managing static resources as part of a larger CI/CD pipeline, with version diffing and rollback support.
If your goal is genuinely retrieving or backing up static resources as deployable metadata, this is the layer to use—a file export tool, including ours, doesn’t retrieve metadata API components.
Where File Export Tools Fit In: Business Record Attachments
Separately from static resources, most Salesforce orgs also accumulate a large volume of files and attachments tied to actual business records—contracts on opportunities, images on cases, and compliance documents on accounts. This is where native Salesforce export tools like the Weekly Data Export Service create real friction and where a purpose-built file exporter like Files Downloader is actually built to help.
Native exports force an all-or-nothing download, strip original file names in favor of unreadable ContentVersion IDs, and disconnect files from the records they belong to—turning a routine backup or audit request into a manual reconciliation project.
How to Bulk Export Salesforce Files and Attachments
Once static resources and record attachments are treated as the separate things they are, here’s the workflow for the attachment side with files downloaded:
1. Filter with list views or SOQL. Select records using standard or custom list views across Accounts, Opportunities, Cases, or custom objects, or run a custom SOQL query export against ContentVersion for more precise targeting.
2. Export with folder structure and metadata intact. Files retain their original names, folder hierarchy, owner, object type, and record association — no manual re-mapping needed afterward.
3. Run a one-click bulk download. No external scripts or developer tools are required—files export directly from the Salesforce UI you already use.
Static Resources vs. Business Record Attachments
| Salesforce Static Resources | files downloader | |
|---|---|---|
| What it covers | CSS, JS, images for Apex/Visualforce/Lightning | Files/attachments on business records |
| Retrieved via | Salesforce CLI, Metadata API, Workbench | List views or SOQL Query Export |
| Use case | Code deployment, version control | Audits, migrations, storage cleanup |
| Best For | Developers, release management | Admins, data teams, compliance |
Because the file export runs natively within Salesforce and respects existing permission sets and sharing rules, exporting business record attachments doesn’t introduce a separate compliance risk into your audit or migration process.