Clean-up and Retention Best Practices
Maintain a usable library without losing critical assets.
Updated 2026-02-08
Overview
Regular library cleanup helps teams maintain speed while preserving high-value output history. Define retention policies before launch operations scale up.
Expected Result
Follow the full sequence in order to avoid retries and preserve generation quality.
Step-by-Step
- Archive campaign-complete outputs outside active workspace.
- Tag high-performing visuals for easy future reuse.
- Review stored outputs periodically and remove low-value duplicates.
Placeholder: retention policy template
image placeholder
Replace with recommended archive strategy visual.
Need More Help?
Use the Contact Support button on this article to send your issue with article context attached.
Was this article helpful?
Still blocked?
Open Support with this article context pre-filled. Response time: 24 to 48 hours.
Contact Support