Organize workspaces, tasks, and assets

Three things with different lifecycles

A completed task can produce several assets. A failed task can still have a usable source video or other partial outputs. Removing a history entry is not the same as deleting every file associated with it.

Organize before creating

Use Studio's workspace controls to create, rename, switch, or delete a workspace. Choose descriptive names for projects or experiments. This is organization within your account, not a shared-team permission system.

A job started in one workspace does not become a different job when you switch the visible workspace. If a result seems missing, return to the original workspace and refresh the library before starting another paid operation.

Reuse sources and name results

Compatible owned resources can be selected as inputs without uploading the same local file again. A completed generation's video can be the source of multiple exports. An Advanced Editor composition references the source video; it does not contain an independent copy of every frame.

Use clear resource display names to distinguish sources, previews, and final outputs. Download the files you need to retain, not merely their temporary URLs. Keep matching texture and metadata files together.

Public API/MCP callers should persist task and asset IDs privately. Do not assume that a displayed name is an API identifier or that the first returned output is the desired file.

Delete and restore a workspace deliberately

Deleting a workspace hides it and requests cancellation of active work in it. Queued jobs can be cancelled promptly; running jobs follow best-effort cancellation. Deletion does not guarantee zero charges.

Use the workspace restore control to select a deleted workspace. Restoring makes its retained contents accessible again; it does not automatically resume cancelled jobs, recover individually deleted files, or undo completed spending.

Workspace deletion is not a storage cleanup operation: uploads and assets continue to count until the resources themselves are deleted. If you hid a workspace while trying to free space, restore it first and review its resources.

Before removing source files

Download important assets, check active jobs, and check compositions or later exports that may still need a source. A resource can be protected while an active job uses it, but completed editing recipes can still depend on it afterward.

See storage and cleanup for the difference between deleting a task and deleting files. If you need help locating a result, report a task ID and time privately to support; never post signed links or credentials in a public report.