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?”

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
  • Running totals on each org’s Overview: how many files, and how many gigabytes, have been downloaded and deleted
  • Every past backup on its own History page
  • 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

1

Scan the org

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

2

Explore the estate

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

3

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.

4

Export a ZIP

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

5

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

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.

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.

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, plus any member an admin gives the File Backup permission on the Members page. It can pull every file in the org into one archive, so it is never on by default for members, and an admin can take it away at any time.

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$14.99 per user per month.

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