Storage, downloads, and safe cleanup
Understand what counts toward storage, why deleting history does not free files, and how to remove resources without breaking active work or saved edits.
On this page
Read usage in Account Center
Account Center reports total storage, uploaded bytes, produced-asset bytes, resource count, and the current quota where one applies. Total usage includes retained uploads and assets across workspaces, including hidden/deleted workspaces.
Quota comes from the applicable subscription or service default. A credit-pack purchase does not upgrade storage. Use the current account display rather than a fixed allowance copied from an old guide.
An upload or operation that would exceed quota can return STORAGE_QUOTA_EXCEEDED with used, allowed, and projected bytes. A positive credit balance does not remove a storage limit.
Know what each delete action does
| Action | What happens to storage and dependencies |
|---|---|
| Delete a task/history entry | Hides that job; does not delete its uploaded sources and output files |
| Delete a workspace | Hides the workspace and requests cancellation; retained files still count |
| Restore a workspace | Restores access to retained contents, not individually deleted files |
| Delete a resource/asset | Removes its resource record from active use and attempts to delete stored bytes |
| Cancel a running task | Best-effort stop; does not itself clean up every retained resource |
Do not clear a whole workspace just to free space. Restore a hidden workspace if necessary, then review actual resources.
A safe cleanup sequence
- Download important files and their matching metadata. Verify the local copies open.
- Identify large or duplicate resources in the correct workspace.
- Wait for active generation/export to finish, or deliberately cancel it and wait for a terminal state.
- Check whether saved editor compositions or future exports still need the source video.
- Delete only the specific resources you no longer need, then refresh usage.
RESOURCE_IN_USE means an active job still references the file. Removing the task from history is not a safe workaround for that protection. A completed composition can also depend on a source even when active-job deletion protection no longer applies.
Resource deletion is not the workspace soft-delete/restore feature. There is no documented recycle-bin recovery for an individually deleted upload or output file. Do not test cleanup on the only copy of an asset.
Temporary URLs are not backups
A signed upload/download URL expires; the underlying file may still exist. Obtain a fresh authorized download link for an existing asset rather than regenerating it. Expired temporary uploads are a different lifecycle and can be removed by cleanup.
No universal permanent-retention promise follows from receiving an asset ID. Download deliverables you need to preserve. Never publish signed links in issue reports or treat their expiry as the asset's retention date.
When usage or downloads look wrong
Refresh the account view after cleanup. A failed storage-object cleanup can require support even though the logical resource has been removed; do not repeatedly attempt unrelated deletions.
For a missing file, check workspace, ownership, deletion history, and whether only the signed link expired. For missing source media in an editor, do not recreate a paid generation until you have checked retained resources.
Was this page helpful?
No search queries, code, or free text are collected. This switch controls documentation interactions only; general site analytics follow the privacy policy. Privacy policy