Clean up unused storage

Global administrators use Admin → Dashboard → Maintenance → Asset GC to inspect and clean up eligible unused storage.

Inspect a scan

1. Open the Asset GC card.
2. Read the displayed minimum age.
3. Select Scan GC and wait for Scanning to finish.
4. Read Asset GC scan, its state, counts, estimated size, and notices.
5. Check Eligible before, minimum age, and run date.

Scan GC inspects candidates without performing the cleanup deletions. It records a scan result. Not checked means this card has no result yet; that does not establish that storage is clean.

The main asset pass examines up to 100 candidates with the dashboard's default request. Other cleanup stages are also bounded. Counts describe this run, not a complete inventory of all unused storage.

Run cleanup

1. Review the current scan if you need an estimate.
2. Select Run GC Now when you intend to apply cleanup.
3. Wait for Running to finish.
4. Read Asset GC run, deletion/archive counts, reclaimed-size estimates, and any deferred-work notice.
5. Investigate repeated failures or unexpected results before another run.

Run GC Now acts immediately without a confirmation dialog. A prior scan is optional, and the run evaluates current candidates rather than approving a frozen list from that scan.

Cleanup can remove eligible stored assets, clean temporary raw import packages, archive stale authoring images, and remove unused AI-search data. It has no Undo control here.

Understand protections and limits

Assets must satisfy age, current-reference, processing, and lifecycle checks. An old file is not automatically garbage: references or active work can protect it, and physical asset deletion requires its prior archive/delete transition. Files in ordinary use are not selected simply because they are old.

AI-search cleanup can be deferred while ingestion or a search-profile change is active. Read the displayed notice rather than treating a deferred stage as completed.

The garbage badge counts eligible assets; it does not combine every kind of cleanup. Stale-image, raw-package, and AI-search counts describe separate work. A successful run does not establish that every possible item was removed or that every pending physical deletion finished immediately.

Repeated runs can encounter the same protected candidates. A zero count is not proof that the entire storage collection has no reclaimable data.

Recover from a problem

Read any Operations error alongside the returned GC result. Cleanup can complete even if the subsequent health refresh fails. Overview Refresh does not retrieve a new GC result or rerun cleanup. If the outcome is unclear, retain the run date and counts for support before repeating a deletion.

For personal storage limits, first review Usage and the relevant content's deletion options. This global maintenance tool does not promise a particular account will gain a stated amount of capacity.