Does it delete anything from my org?

Not unless you deliberately enable it. The scan, browse, and export paths never modify your org. The optional delete workflow needs a separate operator switch on top of the write switch, and only ever touches files a finished backup verifiably captured.

Can I back up only the files on certain records?

Yes. Rather than sweeping the whole org, point the scan at an object and give it your own SOQL WHERE clause — accounts in one industry created before a date, cases closed last year, whatever picks out the set you mean. It queries the matching records, captures the record fields you nominate alongside them, and the archive holds just the files hanging off those records.

Can it delete the files once I have archived them?

Yes, as a separate and explicit step after an export finishes — never as part of the export itself. It only touches files that export verifiably captured, and they go to the Salesforce Recycle Bin rather than being destroyed, so there is roughly a fifteen-day window to change your mind. It needs its own operator switch on top of the write switch, it stays locked until you have downloaded the archive, and it asks you to type DELETE and give a reason for the audit log before it starts.

The file bytes plus a versioned manifest describing every entry (what it was called, what it was attached to, and how big it was) so the archive is still meaningful without this app.

Workspace owners and admins only. It can pull every file in the org into one archive, so it sits at the same trust bar as writing to Salesforce.

File Backup

Back up and audit your Salesforce files

Scan the org’s entire file estate — or just the files hanging off records your own SOQL picks out — browse it by record, user, library or size, then export exactly the selection you want as a ZIP with an embedded manifest. When the archive is verified, bulk-delete what you extracted in one pass. The answer to “how much of our storage is one person’s screenshots?”

Start free trial See pricing

File Backup

Choose filters, scan only the matching Salesforce Files for DevSandbox, then export a ZIP. Read-only — nothing in Salesforce is changed.

What to back up

Only matching files are read from Salesforce, so a large org scans quickly.

Files older than (days)

180

Order by

Largest first

Relationship

All files

Complete org1,284 files · 42.6 GB · scanned 2 Sep 2026, 09:12Rescan files

Complete org coverage. This backs up modern Salesforce Files (ContentDocument) only — legacy Attachments, Documents, and Salesforce CRM Content are counted in your org's file-storage total but are not included yet.

Any related object

Largest first

1,284 files · 42.6 GB

Select all 1,2843 selectedClear Create ZIP

Name	Size	Created	Related records	Relationship
Broker onboarding walkthrough 2021.mp4 MP4 · v20695f00000AbCdEAAV	412 MB	14 Mar 2021, 10:22	None	No record links
Settlement pack archive Q3 FY22.zip ZIP · v10695f00000BcDeFAAV	288 MB	02 Apr 2022, 16:05	None	No record links
NORTHWIND HOLDINGS statements 2019-2021.zip ZIP · v10695f00000CdEfGAAV	241 MB	19 Jul 2021, 09:41	NORTHWIND HOLDINGS PTY LTD +2	Record linked
Legacy CRM export (do not delete).zip ZIP · v30695f00000DeFgHAAV	196 MB	08 Nov 2019, 14:37	None	No record links
BRIGHTWATER LOGISTICS credit file.pdf PDF · v40695f00000EfGhIAAV	54.2 MB	21 Jan 2026, 11:18	BRIGHTWATER LOGISTICS PTY LTD +1	Record linked
MERIDIAN TRANSPORT asset schedule.xlsx XLSX · v20695f00000FgHiJAAV	18.6 MB	03 Feb 2026, 08:55	MERIDIAN TRANSPORT PTY LTD	Record linked
Signed guarantee — CEDAR HAULAGE.pdf PDF · v10695f00000GhIjKAAV	9.4 MB	27 Feb 2026, 15:09	CEDAR HAULAGE PTY LTD	Record linked

Load more (7 of 1,284)

Your file storage is nearly full and Salesforce will tell you the total but not what is in it. A finished scan: 1,284 files, 42.6 GB, largest first. Three of the four biggest are attached to nothing at all — a decommissioned onboarding video and two export archives, 896 MB between them — and they are the three ticked for the ZIP. The notice above states what the scan could see, because Salesforce hides files from any user without Query All Files.

What you can do

A full scan of the org’s files, recording what each one is attached to — record, user, group, library, or the org itself
Browse and filter by object, record, owner, type, and size
See which files have Salesforce-hosted bytes and which are only external links
Coverage is reported honestly: a scan tells you whether it saw the whole org or only what your user can access
Scope a backup with SOQL: pick an object, filter the records with your own WHERE clause, nominate which record fields to capture, and take the files from whatever matches
Export any selection as a ZIP with an embedded manifest describing every file in it
Exports and scans run as cancellable background jobs, with multi-gigabyte files handled without precision loss
Bulk-delete the extracted files once the archive is verified — only files the export actually captured, and only into the Recycle Bin. Off unless an operator turns it on

How it works

Scan the org

A background job inventories every file it can see and records what each is linked to.

Explore the estate

Filter by object, owner, type, or size to find the storage hogs and the orphans.

Or aim it with SOQL

Instead of the whole org, name an object and a WHERE clause. The scan queries the matching records and takes only the files attached to them.

Export a ZIP

Select what you want and download an archive with a manifest — ready for cold storage or a migration.

Then reclaim the storage

With the archive in hand, bulk-delete what it captured in one pass. Only verified files, only to the Recycle Bin, and only when you ask for it separately.

Why it's different

It tells you what it could not see

File visibility in Salesforce depends on sharing, and a backup that quietly skips what it cannot access is worse than no backup. Every scan records its coverage (whole org, or only what the connected user can reach) so an incomplete archive is labelled rather than assumed complete. The manifest travels inside the ZIP, so the archive stays readable years later.

Try asking

Find out what is actually consuming your file storage allocation
Archive files off an org you are about to decommission
Hand a client every file attached to their records
Spot files attached to records that no longer exist
Archive and then clear every attachment on cases closed more than three years ago, in two steps
Prove, for an audit, what was stored and where it went

File Backup — questions

Replacing something?

orgadmin.ai vs Gearset
The most mature comparison-and-deploy tool in the ecosystem, with git and CI. Compare when deployment is only one of the jobs you need done.

Put File Backup to work on your org

Every AI feature on your own provider key, from A$19.95 per user per month.

Start free trial See pricing

14-day free trial
No credit card required
Cancel any time

Back up and audit your Salesforce files

File Backup

What to back up

What you can do

How it works

Scan the org

Explore the estate

Or aim it with SOQL

Export a ZIP

Then reclaim the storage

It tells you what it could not see

File Backup — questions

Works even better with

Metadata Explorer

Security Review

Data Seeding

Replacing something?

Put File Backup to work on your org

Back up and audit your Salesforce files

File Backup

What to back up

What you can do

How it works

Scan the org

Explore the estate

Or aim it with SOQL

Export a ZIP

Then reclaim the storage

It tells you what it could not see

File Backup — questions

Does it delete anything from my org?

Can I back up only the files on certain records?

Can it delete the files once I have archived them?

What is in the ZIP?

Who can use it?

Works even better with

Metadata Explorer

Security Review

Data Seeding

Replacing something?

Put File Backup to work on your org