Use source alternatives when decoding the camera files is the problem; use render caching when repeated timeline processing is the problem. Proxy media, optimized media and render cache are related workflow aids, but they are not interchangeable backups.
On this page
Three questions before changing a setting
| Workflow aid | Question to ask | What must remain protected |
|---|---|---|
| Proxy media | Would an easier working copy of the source improve editing or handoff? | Originals and the source-to-proxy relationship |
| Optimized media | Would media generated for this editing environment improve source handling? | Originals and the project configuration |
| Render cache | Would pre-rendering a processed timeline section avoid repeating expensive work? | Originals, project data and reproducible effects settings |
The current Resolve manual is the authority for generation settings, storage paths and playback/export choices. Use the manual matching your installed version; an older tutorial may use names or assumptions that have since changed.
Identify the bottleneck
- Duplicate the project and play one original clip without a grade or effect chain.
- Try a short generated working-copy sample and compare normal playback and scrubbing.
- Return to the originals and add the grade or processing that normally causes the slowdown.
- Test caching on that section. Note whether the improvement occurs only after the cache has finished.
- Record where generated files are stored and how much capacity is left.
Make a cleanup plan
Generated media can occupy substantial storage. Keep it separate from source originals wherever the application allows. Before deleting a cache or optimized asset, confirm that it is regenerable and that you have retained the source files and project settings. Close or pause jobs that are actively writing to the path being cleaned.
Finish using the intended media
A smooth timeline is an editing convenience, not a delivery check. Inspect the export options for the media and cache choices in your Resolve version. Export a short segment, reopen it and compare fine detail, color and audio with the expected source workflow.
For a collaborator, document whether you are sending originals, proxy files, project data or all three. Do not assume a generated cache is a portable substitute for camera originals. See storage planning and project handoff.
Sources and scope
This is a documentary guide and a proposed decision method, not a hands-on software benchmark. Sources were checked on October 6, 2026. Menus and capabilities can change with the application version, edition, operating system and hardware.