Studio online - media pool readyRender queue idle
StudioMedia poolCut and EditColour pageDeliver
PagesEditingColour gradingFusion effectsFairlight audio
Workflow
Pricing
FAQ
Performance

DaVinci Resolve slow playback: why it lags and how to fix it

Heavy footage humbles every machine eventually, and a browser adds its own variables to the list. The good news is that choppy playback has five common causes, and you can rule most of them out in a minute each.

View pricing
  • Diagnose in order: media, browser, timeline, connection
  • Proxies fix more cases than any setting
  • A few browser habits quietly cost frames every session
A stream of glowing film frames crossing a dark room, sharp on the left and stretching into long trailing streaks of light
Diagnosis

The five causes, in the order worth checking

Start with the media: long GOP 4K and 8K clips are the classic culprit. Then the browser, then the timeline, and finally the connection. Each check takes a minute and you rarely need to go past the second one.

  • Media: long GOP, 10-bit and 8K clips decode heavily in any browser
  • Proxies: if none were generated, playback is doing full decode work
  • Browser: hardware acceleration off, or a tab that has been open for days
  • Timeline: stacked effects, Fusion comps and thirty open tracks
  • Connection: playback streams from the studio; bandwidth is part of the path
The reliable fix

Generate proxies once, stay smooth all project

The proxy workflow is the fix that works for every other cause: render light copies once, cut against them, and the final render still reads the originals. On a 6K or 8K project the difference is not subtle.

  • One proxy pass makes the whole timeline playable, not just one clip
  • Proxies also cut bandwidth, which fixes the connection case too
  • Render cache covers effects heavy sections on top of proxies
Browser habits

Settings and habits that quietly cost frames

A browser is a shared stage: other tabs compete for the same GPU and memory. Most sessions that lag on good hardware are losing frames to a stale tab, an extension, or a hardware acceleration switch that never got turned back on.

  • Confirm hardware acceleration is enabled in Chrome or Edge settings
  • Close streaming tabs; video calls and a timeline do not share politely
  • Update the browser; media paths improve every few releases
  • Prefer ethernet or 5GHz during high resolution playback sessions
Timeline habits

Timeline shapes that keep playback light

Like any editor, the studio is fastest when the timeline is honest: long stacks of effects and half finished Fusion comps cost frames even on perfect hardware. Cache the complicated parts and keep the editing layer simple.

  • Drop playback resolution to half while trimming, back to full to judge
  • Render cache Fusion heavy comps rather than replaying them live
  • Disable effects not under discussion; re-enable as the review moves on
  • Keep simultaneous video tracks to what the scene actually uses
Help

Frequently asked questions

Performance questions that come up before a first render.

What are the minimum specs for smooth playback?

A recent machine with 8 GB of memory, WebGL 2 with hardware acceleration, and roughly 15 Mbps for 1080p or 50 Mbps for 4K. 16 GB and a discrete GPU mainly help the top end: 8K and Fusion.

Why is 8K so hard in a browser?

Every frame decodes at full size before it can be scaled: that is ten times the pixel work of 1080p, whatever the browser. Proxies cut it down to something any laptop can play, and delivery still renders from the originals.

Playback is fine until I open Fusion. Why?

A live composite is recomputed as you scrub; on a busy comp that is a lot of work per frame. Render cache the comp and the timeline returns to normal speed around it.

Is my connection or my laptop to blame?

A quick split test: download a large file while watching the timeline. If playback degrades in step, the path is the constraint; if it does not, the machine is. Proxies reduce both problems at once.

Keep reading

Where this fits in the workflow

The studio is one project with several pages. These are the pages that usually come before and after this one.

Proxy workflowProxy editing: cutting 6K and 8K footage without a render farm

Every heavy project has the same shape: beautiful camera files the machine cannot play. Proxies replace playback, not quality, and in a browser workflow they are the difference between a slideshow and a working timeline.

Read the page TroubleshootingDaVinci Resolve troubleshooting: the fixes for common stalls

Almost every stall has one of a short list of causes, and the order you check them in matters more than the length of the list. What follows is that order, grouped by where the trouble shows up.

Read the page System requirementsDaVinci Resolve online system requirements: what your browser needs

There is no hardware compatibility list to work through, because the studio runs in the browser. What matters is a current browser, hardware acceleration, enough memory for the timeline you open and a connection that can stream your media.

Read the page Edit pageOnline editor for multi track video editing in the browser

The Edit page is a full multi track timeline that opens in Chrome. Ingest a card, assemble on the Cut page, trim on the Edit page, and every clip, marker and speed ramp is still where you left it the next time you open the project on any machine.

Read the page
Ready when you are

Make the timeline smooth again

Run the two minute diagnosis, generate proxies where the check points, and keep the render cache on for the heavy scenes.

Read the proxy workflow
  • No install, no licence server
  • Google sign in, projects in the cloud
  • Cancel anytime
DaVinci Resolve Slow Playback | Why It Lags and How to Fix It