DaVinci Resolve Render Cache: Smart vs User Guide

Quick answer: choose Playback > Render Cache > Smart when you want Resolve to identify expensive clips and effects automatically. Choose User when you want deliberate control over the clips, Color nodes and effects that get cached. A red cache bar means the range is waiting to be cached; blue means the cached result is ready. Wait for blue, then replay the same range before deciding whether cache solved the problem.

Render Cache creates temporary working media with processor-heavy operations already calculated. Resolve can play that media instead of rebuilding the live effect, grade or composition on every frame. It's useful for a difficult section of a timeline. It isn't a replacement for good source-media handling, and it doesn't prove that every playback problem is a cache problem.

If the whole timeline is slow before you add effects, start with the slow-playback diagnostic. If you need lightweight files that travel between workstations, use the Proxy Media workflow. This guide stays on one job: controlling Resolve 21's render cache without turning the project into a pile of mystery files.

The 60-second Render Cache setup

1. Open the timeline and mark a short range that fails consistently.
2. Choose Playback > Render Cache > Smart.
3. Play the range once, or stop working long enough for background caching to begin.
4. Watch the thin cache indicator along the bottom of the timeline ruler.
5. When the relevant red section turns blue, replay exactly the same range.

That's a test, not a permanent configuration. If Smart caches far more than you need, or misses the one operation that's actually expensive, choose Playback > Render Cache > User and flag the relevant clip, node or filter yourself. On the Edit and Color pages, Option-R cycles through Off, Smart and User, but the menu is easier to verify when you are learning the system.

Smart vs User: choose by control, not by computer speed

My practical rule is simple: start with Smart for one repeatable range. If the result is useful but the behavior is too broad, move to User and cache only the expensive boundary. Don't switch modes while comparing different ranges; you'll not know whether the mode or the content changed the result.

In File > Project Settings > Master Settings, the Optimized Media and Render Cache group includes automatic User-mode options for transitions, composites and Fusion effects. The current DaVinci Resolve 21 Reference Manual identifies automatic Fusion-effect caching as enabled by default. Check the actual boxes in your project instead of relying on a preset you remember from another timeline.

The three cache levels Resolve manages

The menu makes Render Cache look like one switch. Underneath, Resolve manages three different cache levels. Choosing the correct level matters because it determines which work is baked into the temporary media and which work remains live and editable.

Fusion Output Cache: before the Color page

Fusion Output Cache is the pre-Color cache. In Smart mode, Resolve can use it for processor-intensive source formats such as H.264, H.265 and supported camera-raw media, for speed effects, and for clips that contain Fusion work. In User mode, select one or more clips in the Edit timeline or Color-page thumbnail timeline, right-click, then choose Render Cache Fusion Output > On.

Use this level when the expensive work happens before the grade. It's also the first manual target when a Fusion composition is the clear playback boundary. If the clip is still difficult after its Fusion Output cache is blue, the remaining cost may be in an Edit-page filter, the Color graph, a layer above it, storage, or another part of the playback chain.

Node Cache and Color Output: inside the grade

On the Color page, right-click a node and choose Node Cache > On. Resolve caches that node together with the upstream nodes feeding it. This is the precise choice for an expensive early operation such as temporal noise reduction: cache the costly foundation, then keep the downstream look adjustments live.

Render Cache Color Output isn't a fourth independent level. It uses the Node Cache to store the whole Color-page output for a clip. Right-click the clip in the Edit timeline or Color thumbnail timeline and enable Render Cache Color Output. This is useful when the entire grade is finished enough to bake temporarily. Any change that affects the grade can require the whole result to be cached again.

Sequence Cache: Edit-page timeline work

Sequence Cache handles timeline operations such as transitions, opacity changes, adjustment layers, composite modes and speed or retime effects. You don't flag Sequence Cache clip by clip. Smart mode handles it automatically. In User mode, the project-level transition and composite checkboxes decide which categories can cache automatically; tracks that should stay live can be excluded from caching from the track-header context menu.

Edit-page Resolve FX and OFX filters have their own manual control. Right-click the clip, open Render Cache OFX Filter, and select the expensive filter. That's more predictable than baking every operation on the clip when only one filter misses real time.

What the red and blue cache bars actually tell you

The thin indicator along the bottom of the timeline ruler is a status signal:

• Red: this part of the timeline is marked to be cached.
• Blue: Resolve has cached this part of the timeline.
• No bar: the range may not be marked for cache at the current mode and item settings, or it doesn't need the type of caching you expected.

Resolve can build cache while you play a red range. It can also begin after the project has been idle for the number of seconds set under Master Settings. The interval is configurable, so “wait five seconds” isn't a universal instruction.

A blue bar isn't permanent. Change an upstream operation and the old cached result is no longer valid; Resolve turns the affected range back into work that must be calculated. That rebuild is normal. A cache that repeatedly invalidates without a relevant edit is a different problem and should be tested with one change at a time.

Set cache format and location before a large project

Open File > Project Settings > Master Settings. The two settings that matter most are separated on the page:

• Render Cache Format is in the Optimized Media and Render Cache group.
• Cache files location is in Working Folders.

Choose a cache format that the editing machine can decode smoothly and the cache drive can sustain. The available codec list varies by operating system. ProRes and DNxHR families are common working choices; the correct tier depends on whether the cache is only for editorial playback or may be used in a finishing or delivery path.

For HDR, alpha or out-of-bounds image data, a casually chosen lightweight format can be the wrong compromise. Blackmagic lists 16-bit float, ProRes 4444 or 4444 XQ, and DNxHR 444 among the formats appropriate when that signal must be preserved. Those are not automatic recommendations for every offline edit. They trade more storage and throughput for a higher-fidelity working result.

The cache location defaults to the first scratch disk listed under Preferences > System > Media Storage. If no scratch disk is configured, Resolve can fall back to the system disk. Use a fast, consistently mounted volume with enough free space. A fast codec written to a full, sleeping or disconnected drive is still a broken cache workflow.

Render Cache not working: test in this order

Don't start by deleting every cache file. First prove which gate is failing.

1. Verify the global mode. Playback > Render Cache must be Smart or User, not Off.
2. Verify the target. In User mode, set the intended Fusion Output, node or OFX filter to On. For Sequence Cache behavior, inspect the project-level User Mode checkboxes.
3. Trigger the cache. Play the red range or leave Resolve idle long enough for the configured background interval.
4. Watch the same range. If no red bar appears, the item isn't being targeted the way you think. If red appears but never progresses, continue to storage and processing checks.
5. Check the working folder. Confirm that Cache files location exists, is writable, remains mounted and has free space.
6. Run a scoped reset. Select the problem clip and choose Playback > Delete Render Cache > Selected Clips. Let only that range rebuild.
7. Compare cache Off. If live playback is better, the chosen cache format, drive or target is adding overhead. Do not assume that more caching must be faster.
8. Leave the cache topic when the evidence does. A blue range that still cannot play smoothly points to another bottleneck. Return to the broader playback test sequence instead of rebuilding the same cache again.

If a cache command is missing, greyed out or appears disabled, check the selection before changing preferences. Fusion Output and Color Output controls apply to clips selected in the Edit timeline or the Color-page thumbnail timeline; Node Cache applies to a selected Color node. Sequence Cache has no manual clip command because Resolve controls that level automatically. A Media Pool clip or an unrelated page won't expose the same context menu.

If cached media appears offline, test the selected clip with cache Off, then clear and rebuild only that clip. If the original source is also offline, cache cleanup won't repair the media path; use the Media Offline relinking checks. If the problem occurs only in the Deliver queue with an error message, follow the Render Failed diagnostic and keep the cache test scoped to the failing range.

Clear cache without treating every file as disposable

Render Cache is persistent. Closing the project does not remove it. Under Playback > Delete Render Cache, Resolve 21 offers three useful scopes:

• Selected Clips rebuilds only the clips you have selected. Use it for one stale or suspect result.
• Unused removes cache data that no longer corresponds to current timeline clips or effects. Use it for routine space recovery.
• All resets the current project's entire render cache. Use it only when the scope really is the whole project or the other two choices can't isolate the problem.

Playback > Manage Render Cache opens the Cache Manager for projects across accessible project libraries. The current manual warns that clearing selected cache there has no warning dialog or undo. Read the project and library columns twice before clicking the destructive button.

For ongoing maintenance, Preferences > User > Cache Management can delete local cache older than a chosen number of days. That is useful on a constrained scratch drive, but it isn't a substitute for choosing the right working folder or keeping active project cache available.

Should you use cached images for export?

In the Deliver page's Video settings, Use Render Cached Images can write from cached media instead of calculating the effects again. This may save render time, but it also makes the cache format part of the output-quality chain. If the cache was created in a lightweight editorial format, contains stale frames or was never checked at delivery quality, leave the option off and render from the live source and effects.

Use cached images only when you deliberately chose a suitable cache format, the complete delivery range is blue, and you have inspected the result. A successful timeline playback test is not automatically a mastering decision.

Where Render Cache belongs in the workflow

Render Cache is strongest when a timeline is already organized and one processing stage can't meet real time. It's project-managed, replaceable working media tied to the current computed result. Proxy Media is portable and tied to source clips. Optimized Media helps Resolve use easier-to-decode source media on the workstation. Timeline Proxy Resolution changes working resolution without generating those files.

Those tools can work together, but they shouldn't be switched on as a ritual. Pick the tool that matches the boundary you can prove. The DaVinci Resolve workflow hub organizes the next steps by job; the Resolve troubleshooting hub is the better route when the symptom is wider than cache.

DaVinci Resolve Render Cache FAQ

Should I use Smart or User Render Cache?

Use Smart for an automatic first test or when many different effects need help. Use User when most of the timeline already plays in real time and you want to cache specific clips, nodes or filters. Remember that project settings can still automate transitions, composites and Fusion effects in User mode.

Why does the red cache bar never turn blue?

Check that Render Cache is Smart or User, verify the item-level cache target, play the range or wait for the configured background interval, and confirm that the cache drive exists, is writable and has free space. Then delete cache for Selected Clips and rebuild one range.

Why did a blue cache bar turn red again?

Resolve invalidates cached media when an upstream operation changes. A grade, Fusion composition, filter, retime or timeline edit can require the affected result to be rebuilt. That's normal when the edit actually changed the cached processing path.

Where does DaVinci Resolve store render cache files?

The project uses the Cache files location under Project Settings > Master Settings > Working Folders. Its default comes from the first scratch disk in Preferences > System > Media Storage; without a configured scratch disk, Resolve can use the system disk.

Can I safely delete Render Cache?

Yes. Render Cache is generated working media, not the camera originals. Delete Selected Clips for a scoped rebuild, Unused for routine cleanup, or All for a complete current-project reset. Resolve must calculate deleted cache again when it is needed.

Is Render Cache the same as Proxy Media?

No. Render Cache stores computed timeline, Fusion and Color results for playback. Proxy Media creates linked, portable versions of source clips for easier editing and handoff. Use the dedicated proxy workflow when files need to move or be relinked.

Does Render Cache change export quality?

Ordinary cached playback does not force the Deliver page to use cache. If you enable Use Render Cached Images, the chosen cache format becomes part of the output path. Use a suitable high-quality format and inspect the cached range before relying on it for delivery.

Jason Miller I run DaVinci Resolve Club as an independent publication: hands-on edits, color grading breakdowns, Fairlight sessions, Fusion tests, and honest notes on where Resolve gets in the way.