Know exactly what you're dealing with before you migrate or archive. Accurate file and attachment counts across any Salesforce object — with live progress, job history, and email notification.
Storage cleanups and migrations that start without a count end with surprises. Salesforce Attachment Counter answers "how many files, and where?" before you commit to a plan.
Scan files and attachments on Accounts, Contacts, Cases, Opportunities, or any custom object. Totals are reported per object, so you can see exactly where your file volume lives.
Progress streams live to your browser as the scan works through your org. No black-box batch job — you always know how far along the count is and which object it's processing.
Every count is stored with its results. Compare a count from before a migration with one after to validate that everything arrived, or track file growth over time.
Large orgs take time to scan. Kick off a count, close the tab, and get an email the moment it completes — with the results waiting in your job history.
Counting never creates, modifies, or deletes anything. Point it at production with confidence — it queries metadata and nothing else.
Counts translate directly into scope: which objects to include in a migration, how much storage an archive run will reclaim, and which worker tier fits your volume.
Before quoting a timeline for an org consolidation, run a count against the source org. Knowing you have 47,000 files on Cases and 3,000 on Accounts changes the plan — and the worker tier you need.
Considering archiving to S3? Count first. Per-object totals show where the reclaimable storage actually is, so you can project savings before configuring a single archive job.
After a migration or archive run, re-count both orgs. Matching numbers are the fastest sign-off evidence you can hand a stakeholder.
It counts files and attachments associated with records across the Salesforce objects you select — modern ContentDocument files and legacy Attachments alike — and reports totals per object with live progress while the scan runs. For background on the difference, see our ContentVersion vs. Attachment guide.
Every storage cleanup or migration project starts with the same question: how many files do we actually have, and where? An accurate count lets you scope the project, estimate storage savings, choose the right worker tier, and set a realistic timeline — before any data moves. Our guide to counting Salesforce attachments covers the manual approaches and where they fall short.
No. Counting is a read-only operation — the tool queries file and attachment metadata but never creates, modifies, or deletes records. It is safe to run against production.
Duration depends on org size and the number of objects scanned; progress streams live so you always know where the job stands. You don't have to watch it — enable the optional email notification and you'll be told the moment the count completes. Full job history keeps every past result available.
The count is step one. These tools are step two.
Once you know what you have, move it. Bulk file transfer between orgs with metadata preservation, auto-scaling parallel workers, and per-file CSV reporting.
Learn more →If the count shows storage bloat, archive inactive files to your own S3 bucket — originals removed only after each copy is verified, with archive records keeping files findable.
Learn more →Tell us about your org and what you're planning — a migration, an archive, or just an audit. We'll show you a count against a representative dataset.