
Inspect whether you cached the entire Color Output or a particular node. In Resolve 20's documented User Cache workflow, a Color Output cache covers the complete node tree, so changing a node requires that clip output to be cached again. A node cache can target a specific processing stage.
Key Takeaways
- Cache scope determines what a later change invalidates.
- Cache the expensive stage deliberately while grading remains active.
- Verify the image as well as playback performance.
Identify the real bottleneck
A slow shot can contain noise reduction, a complex effect or several interacting processes. Note which stage is expensive and which stages you still expect to adjust.
Do not rearrange a grading graph purely to obtain a blue cache indicator. Processing order can affect the picture, so preserve the intended image pipeline while diagnosing performance.
Inspect the cache scope
Blackmagic's Resolve 20 Colorist Guide documents User Cache, a node's Node Cache > On setting and Render Cache Color Output for the complete node tree. It explains that changes to the complete cached output require recaching.
Check your chosen scope. If you are repeatedly revising later corrections while a heavy earlier stage stays unchanged, consider whether a targeted node cache suits that workflow. Use an identifiable project checkpoint before experimenting.
The aim is to reduce unnecessary recomputation, not to guarantee a particular render speed on unmeasured hardware.
Test one controlled change
Allow the selected cache to finish, then make one intended adjustment and observe which cache needs rebuilding. Compare the picture before and after, keeping the correction's purpose clear.
In an illustrative workflow, an expensive cleanup stage may stay fixed while a later creative adjustment changes. A full-output cache naturally has more downstream work to rebuild than a cache confined to the unchanged stage.
If you move nodes, inspect the actual result carefully. A faster preview is not an acceptable trade if the image processing has changed unintentionally.
Verify the working and delivery image
Play the whole shot after the cache is ready. Inspect movement and difficult details rather than accepting only a smooth static frame.
Keep export settings as a separate decision. A playback cache is part of the editing workflow; the final rendered file still needs verification. Use the preview-to-output comparison, and keep the approved version identifiable if several processing arrangements were evaluated.
Source: Blackmagic's Resolve 20 Colorist Guide, printed pages 371–374.
Related tasks
- Captions look correct in preview but move in the export: isolate a small render test
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
Sources and scope
- The Colorist Guide to DaVinci Resolve 20, User Cache: Printed371-374: downstream changes do not affect upstream node cache; User Node Cache versus complete Render Cache Color Output; full tree recaches when nodes change.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance, not a claim of hands-on testing or independent review. Report a correction.
Cover: Pignatta / Pixabay, Content License. The city photograph is an illustrative source asset; it does not show this application or a test result.