Treat cache as generated working data, not as a substitute for originals or project backups. Rebuild it when a repeatable problem plausibly involves generated assets; do not start troubleshooting by deleting every media-related folder.
On this page
Identify the folder before touching it
| Asset | Normally requires preservation | Question before removal |
|---|---|---|
| Camera original | Yes | Is this the only usable recording? |
| Project or library data | Yes | Can the edit be rebuilt from another verified copy? |
| Generated cache or previews | Usually regenerable | Are source media and generating settings retained? |
| Proxy or optimized media | Depends on handoff | Are collaborators relying on these as their working media? |
The label on a folder is not sufficient proof. Check the application’s current storage settings and the actual path. If several projects share a cache location, an aggressive cleanup can force regeneration in projects you did not intend to touch.
Use a bounded rebuild
- Save a new project version and verify the originals are online.
- Record the symptom and identify a short sequence that reproduces it.
- Inspect the cache path and available disk space.
- Close the application or stop active jobs before using its documented cache-cleanup controls.
- Reopen the project and let the necessary assets regenerate.
- Repeat the same sequence and compare the original symptom.
Know what the result means
If the problem goes away, retain your notes: it may have involved stale generated data or an unavailable path. If it persists, investigate the source clip, effect chain, driver or project state next. A cache rebuild that merely frees space does not prove that the media itself was damaged.
Do not confuse cleanup with performance tuning
Deleting useful render previews can make the next playback or export slower until they are rebuilt. Moving cache storage may help a particular workload, but it also requires a reliable location with enough capacity. Make that change independently from codec and effect changes so its effect is interpretable.
Document your cleanup policy, including what can be regenerated and what must be backed up. See proxies, optimized media and render cache and project recovery.
Sources and scope
This guide proposes a repeatable method, not a measured performance result. Sources checked October 6, 2026.