If DaVinci Resolve still plays slowly with proxies and Smart Cache enabled, verify that the affected clip actually uses its proxy, then check which effects have finished caching. Test the same short section after each change to isolate the remaining workload.
This guide targets a Mac editor trying to restore usable timeline playback. Menu instructions follow the July 2026 DaVinci Resolve 21 Reference Manual. Supporting training examples are explicitly from Resolve 20, the edition currently offered on Blackmagic Design’s training page. Consult the manual matching your installed version if labels differ. Resolve 21 Reference Manual, official training books.
Establish a repeatable playback test
Choose a 10–20-second section that consistently stutters. Note its timeline frame rate, the viewer’s playback FPS, the affected clips and the cache indicators. Use this section throughout the diagnosis; changing the test material makes results harder to compare.
Resolve’s viewer shows playback FPS and a GPU status indicator. Also check Show All Video Frames in the Edit viewer’s options menu: when processing falls short, enabling it allows slower playback to show every frame; disabling it prioritizes audio while permitting dropped video frames. Neither setting removes the underlying workload. Resolve 21 Reference Manual, chapter 8, page 199.
For normal editing, test with Show All Video Frames disabled, but assess visible motion as well as the displayed FPS. Record three observations: whether the section maintains the intended pace, whether motion skips and whether audio remains continuous. Repeat the section twice without editing between passes.
Verify that the slow clip is actually using proxy media
Prefer Proxies is a preference, not proof that every clip has a usable proxy. Resolve falls back to original media when a clip has no proxy available. That makes a single unprepared clip a useful place to investigate when playback slows only at one cut. Resolve 21 Reference Manual, chapter 8, page 219.
- Choose Playback > Proxy Handling > Prefer Proxies.
- Switch the Media Pool to List view. Right-click a column heading and enable Proxy and Proxy Media Path.
- Inspect the source clip responsible for the slow section. Check its proxy resolution, location and proxy status badge.
- If the proxy has moved, right-click the source clip and choose Link Proxy Media, then select the matching proxy file or directory.
The Editor’s Guide documents these columns and the PXY status display. It also explains an easy source of confusion: ordinary clip resolution and codec information continue to describe the camera original even when proxy playback is selected. Use the proxy-specific indicators to verify the switch. The Editor’s Guide to DaVinci Resolve 20, lesson 6, pages 330–332.
For a missing proxy, generate one for the affected clip before processing the whole project. In Project Settings > Master Settings, select the proxy resolution and format; then right-click the Media Pool clip and choose Generate Proxy Media. The manual identifies ProRes LT and DNxHR LB as examples of easily editable, low-bandwidth formats. Treat the format choice as a test for your media and Mac, rather than a universal prescription. Resolve 21 Reference Manual, chapter 8, pages 213–214 and 221.
Replay the section. If the same clip becomes smooth after its proxy is linked or regenerated, you have a practical fix for that clip. If nothing changes, continue with cache coverage before generating more media.
Check what Smart Cache has actually rendered
Smart Cache does not mean the entire timeline has already been rendered. In the Edit timeline, red cache indicators mean pending work; blue indicators mean cached frames. Background caching begins after a configurable period of inactivity when enabled in Project Settings. Changes to cached material can require it to be cached again. Resolve 21 Reference Manual, chapter 8, pages 205–209.
Choose Playback > Render Cache > Smart, stop making adjustments and let the affected range finish caching. Then replay it without changing effects, grades or timing. This separates the cost of building the cache from the performance of playing the completed result.
For Fusion work, Blackmagic’s training guide specifically instructs editors to return to the Edit page, enable Smart Cache and wait for the indicator to turn blue before reviewing playback. It also conditions smooth playback on a sufficiently fast cache drive. Evaluate the editing result there before treating slow playback inside the Fusion workspace as the same problem. The Visual Effects Guide to DaVinci Resolve 20, page 29.
If the slow operation remains uncached, select the appropriate control rather than changing cache modes at random:
| Where the expensive work occurs | Documented cache control |
|---|---|
| Fusion output or source processing | Right-click the timeline clip: Render Cache Fusion Output > On |
| A Color page node and its upstream processing | Right-click the node: Node Cache > On |
| The clip’s complete Color page grade | Right-click the timeline clip: Render Cache Color Output |
| An OFX filter applied in the Edit page | Right-click the clip: Render Cache OFX Filter, then select the filter |
These controls target different stages of processing. In particular, the manual says Edit page OFX filter caching requires manual selection in both Smart and User modes. A cached Fusion output also precedes Color page processing, so that cache alone does not establish that the complete grade is rendered. Resolve 21 Reference Manual, chapter 8, pages 206–211.
Use one controlled comparison to choose the next fix
The following decision aid is a diagnostic inference from the documented separation between proxy media, timeline resolution and cache stages. It is not a benchmark. Change one condition, replay the same range and restore the setting before the next comparison.
| Observation | What it suggests | Next useful action |
|---|---|---|
| Linking the missing proxy improves the affected clip | Its original-media playback path was contributing to the slowdown | Check other slow clips for the same proxy gap |
| Playback improves only after the relevant cache completes | The cached processing stage was contributing | Finish caching before reviewing that effect |
| Half-resolution timeline playback improves an uncached section | Reduced image-processing work helps | Use reduced working resolution while editing |
| The relevant cache is complete but playback remains poor | Cache coverage, storage or another live workload still needs investigation | Check the cache location and audio processing separately |
For the resolution comparison, choose Playback > Timeline Proxy Resolution > Half Resolution. This reduces working resolution on the fly; it does not create or relink proxy files. The two features are independent. The manual also warns that this resolution control does not solve raw debayering limitations; format-specific Camera Raw > Decode Quality controls are the supported alternative where available. Resolve 21 Reference Manual, chapter 8, pages 200–201.
For example, imagine an illustrative timeline containing a plain clip, a Fusion title and a clip with an Edit page OFX filter. If the plain clip plays smoothly, avoid rebuilding every proxy immediately. Test the title after its Fusion cache completes, then explicitly cache the OFX filter. Different responses point to different processing stages without requiring invented performance thresholds.
Investigate the cache drive when completed cache still stutters
Open Project Settings > Master Settings and inspect Cache files location and Render Cache Format. Check the actual destination rather than assuming it is the same drive as your proxies. Blackmagic documents that higher-quality cache formats place greater demands on storage throughput and capacity. Resolve 21 Reference Manual, chapter 8, page 208.
A useful controlled test is to rebuild a small affected section on another available fast local volume. Keep its effects and cache format unchanged initially. Improvement would implicate the previous storage path, although it would not identify whether the drive, connection or competing activity caused the limitation.
If you subsequently test a lighter cache format, retain the image properties your work requires. The manual distinguishes formats that preserve alpha channels and out-of-range highlight data; choosing a smaller cache solely for speed can change what you see during grading. Resolve 21 Reference Manual, chapter 8, pages 206–208.
If a selected clip needs a clean cache rebuild, use Playback > Delete Render Cache > Selected Clips, then wait for it to cache again. This discards generated cache for that selection and requires regeneration. It is a targeted test, not a reason to clear every project’s cache. Resolve 21 Reference Manual, chapter 8, page 211.
Check Fairlight processing and competing Mac workloads
When picture playback is acceptable but audio breaks up, test audio processing separately. Temporarily bypass one suspect plugin using its bypass control, replay the section and restore it afterward. For an audio clip with plugin effects, right-click it and choose Cache Audio Effects. The Resolve manual describes this as a nondestructive clip-level operation that can recache after parameter changes; it should not be assumed to render every track or bus processor. Resolve 21 Reference Manual, chapter 180, pages 4087–4088.
The Fairlight training guide demonstrates plugin bypass and clip caching. If you use its Voice Isolation example, preserve the edition boundary: Voice Isolation is a Studio feature. The diagnostic sequence does not require adding that effect. The Fairlight Audio Guide to DaVinci Resolve 20, lesson 6, Resolve 21 Reference Manual, chapter 181.
On the Mac, open Activity Monitor > Memory during the same playback test. Watch Memory Pressure and Swap Used rather than judging performance from the Memory Used total alone. Apple defines Memory Pressure using several factors, including swap rate and cached memory; cached files can occupy otherwise unused memory productively. View memory usage in Activity Monitor on Mac.
You can also choose Window > GPU History to observe GPU activity while the test runs. Use it as supporting context alongside your controlled comparisons, rather than treating a busy graph as proof of a particular faulty effect. View GPU activity in Activity Monitor on Mac.
In Resolve 21, inspect the bottom-toolbar Background Tasks pop-up if proxy generation or another background render is still running. The manual warns that background rendering can consume substantial resources and documents Pause background renders on foreground activity in Background Tasks preferences. Compare playback after those tasks finish or pause. This setting is distinct from the idle background caching controls. Resolve 21 Reference Manual, chapter 4, pages 110–111.
Finish by replaying the original test range with all intended effects restored, proxies verified and the relevant cache complete. Keep the smallest change that produces a repeatable improvement. A specific finding—such as one missing proxy, one uncached filter or a slower cache destination—gives you a usable editing workflow and a clear starting point if playback slows again.
Sources
- DaVinci Resolve 21 Reference Manual — Blackmagic Design.
- DaVinci Resolve — Training — Blackmagic Design.
- The Editor’s Guide to DaVinci Resolve 20 — Blackmagic Design.
- The Visual Effects Guide to DaVinci Resolve 20 — Blackmagic Design.
- The Fairlight Audio Guide to DaVinci Resolve 20 — Blackmagic Design.
- View memory usage in Activity Monitor on Mac — Apple.
- View GPU activity in Activity Monitor on Mac — Apple.