Skip to main content
An asset’s place in your library, its underlying media file, and its generation’s request data have different lifetimes. Choose the operation that matches what you want to remove.

​
Library actions

The library does not offer a Trash or restore workflow. Check your selection before deleting assets.

​
File lifetime

Media files follow the storage lifetime applied to them. Enabling Assets, placing a file in a collection, or sharing a collection does not itself extend a file’s lifetime. If a file expires, it can no longer be downloaded or reused as a reference. A saved entity or recorded generation relationship does not preserve an expired file. Download a copy before expiry when you need to keep the media outside fal. See Data retention and storage for CDN lifecycle controls and request-payload retention. For work created in Agent, also see Agent retention.

​
Delete generation files and request data

To delete a completed generation’s stored request payloads and associated CDN output files, use Delete request payloads. Input files are not deleted by that operation because they can be used by other requests. Do not use the library’s delete action as a substitute for deleting generation files or revoking access to a URL. See File access controls to manage file access.

​
Shares and downloaded copies

Stopping a collection share revokes that viewing link. It does not remove files already downloaded by recipients. A share’s expiry is separate from file expiry.