Motion Blur in DaVinci Resolve: Free, Fusion and Studio Methods

Quick answer: pick the method by asking what creates the movement. If a Transform, Text+, Warp or another supported Fusion tool animates the shot, enable Motion Blur in that tool’s Settings tab. If the movement already lives inside recorded footage, the free native route is Optical Flow generating vectors for Vector Motion Blur. DaVinci Resolve Studio adds motion-estimated blur through the Color page Motion Effects palette and Resolve FX Motion Blur. And if you retime a clip with TimeSpeed in Fusion, generate fresh motion vectors after TimeSpeed, then apply Vector Motion Blur.

The tempting shortcut is an ordinary Blur or Directional Blur and the hope that it understands the shot. It won't. Those tools can soften or smear an image, but they don't estimate a separate speed and direction for every moving object. Convincing motion blur needs motion information, and Resolve gets that information in different ways depending on the job.

Choose the Motion Blur Method First

Run through this decision path before you build a single node:

• You animated position, size, angle, text or a warp inside Fusion: use the Motion Blur checkbox in the Settings tab of the tool that creates the movement.
• A car, hand, camera pan or other subject already moves in recorded footage: use Optical Flow to generate vectors for Vector Motion Blur in the free edition, or reach for a Studio motion-estimation method.
• A Fusion TimeSpeed or TimeStretcher node changed the timing: put a new Optical Flow node after the retiming node, then feed those new vectors to Vector Motion Blur.
• You only need a graphic streak or a deliberately uniform smear: Directional Blur can be exactly the right look, but it's a stylized blur, not motion analysis.
• You only need to hide or soften a face or background: follow the separate face and background blur workflow. That's a masking task, a different problem from recreating camera-like motion blur.

Getting this split right up front saves most of the wasted work. A keyframed title already carries clean parameter motion that Fusion can sample. A cyclist crossing a recorded frame carries nothing of the sort, so Resolve has to analyze neighboring frames before it can estimate that movement.

Why Blur and Directional Blur Are Different

A normal Blur spreads image detail around each pixel. It has no idea whether that pixel belongs to a parked car, a spinning wheel or the background. Push the blur up and the whole selected region just gets softer.

Directional Blur adds a chosen angle and length, and Blackmagic’s own manual pitches it for simulated motion blur and light-ray effects. That's great for speed streaks, graphic transitions and shots where one broad direction is acceptable. It still can't work out separate motion for a rider, a spinning wheel, a passing light and the camera move behind them.

Motion-aware blur needs one of two inputs:

1. Predicted parameter motion from a Fusion tool that is creating the animation.
2. Motion vectors that describe how image areas move between frames.

That's why two shots that look alike in the Viewer can need completely different tools underneath. If you're still building the composition itself, the Fusion beginner guide walks through MediaIn, MediaOut, Merge nodes and Viewer routing before you add motion processing.

Add Motion Blur to Animation Created in Fusion

When a Fusion node creates the movement, start with that node. Don't add Optical Flow.

Typical examples:

• a Transform node moving or scaling an image;
• Text+ animated across the frame;
• a supported Warp node changing geometry;
• any other tool whose Settings tab includes a Motion Blur section.

Select the node that creates the movement, open Inspector → Settings and enable Motion Blur. Per the Resolve 21.1 manual, supported motion-producing nodes use their predicted motion to render blur through a virtual camera shutter, and the checkbox reveals four controls. Quality sets the number of samples (the default of 2 means two samples on either side of the motion). Shutter Angle defaults to 100, where 360 means the shutter stays open for a whole frame. Center Bias moves the center of the blur, and Sample Spread changes how much weight each sample gets, which affects how bright the samples look. All of it is in the Fusion Motion Blur description in Blackmagic’s current reference manual.

Not every node has this control. If the Motion Blur section is missing, find the upstream tool that actually changes position or shape. A Merge may combine the layers while a Transform below it creates the movement, and the Transform is the node holding useful motion data.

For a simple animated element:

1. Build and keyframe the movement.
2. Select the motion-producing node.
3. Open the Settings tab.
4. Enable Motion Blur.
5. Set the Shutter Angle before you raise Quality.
6. Inspect the fastest part of the move, frame by frame.

Motion blur can't rescue clumsy animation timing. If the object lurches into motion or stops on an awkward frame, shape the move first in the keyframes and Curve Editor workflow, then judge the blur.

The Viewer Motion Blur button does not enable blur

The Fusion page has a global Motion Blur switch, and it's a preview control. On the Resolve Fusion page it isn't a button on the viewer toolbar: right-click the transport control area under the viewer (anywhere except the Play buttons) and it sits next to High Quality and Proxy. Blackmagic documents that turning it off temporarily disables motion blur throughout the composition and speeds up viewer rendering, but individual nodes must already have Motion Blur enabled before the switch does anything.

So if a node is set up correctly and the Viewer suddenly looks sharp, check that global Motion Blur button first. If no node has Motion Blur enabled, flipping the global button won't create any blur at all.

Add Motion Blur to Recorded Footage in the Free Edition

When the movement already exists in the pixels, use Optical Flow to calculate motion vectors and Vector Motion Blur to turn those vectors into blur.

The basic Fusion structure has one image branch and one vector branch:

MediaIn ─────────────────────────→ Vector Motion Blur (orange Image input)
   └→ Optical Flow ──────────────→ Vector Motion Blur (green Vectors input)
                                    └→ MediaOut

Vector Motion Blur needs the image plus motion-vector data. The Optical Flow node creates the Vector and BackVector channels by analyzing neighboring frames, and Vector Motion Blur then uses that movement data to blur each part of the image along its own estimated direction and distance.

Build the free workflow like this:

1. Put the clip on the timeline and keep it clear of cuts that don't belong to the shot.
2. Open the clip on the Fusion page.
3. Branch MediaIn into an Optical Flow node.
4. Add Vector Motion Blur before MediaOut.
5. Connect the unblurred image branch to Vector Motion Blur’s orange Image input.
6. Connect the Optical Flow output to Vector Motion Blur’s green Vectors input.
7. Connect Vector Motion Blur to MediaOut.
8. Start with a restrained blur amount and inspect motion boundaries, crossings and newly revealed background.

Blackmagic’s manual states that Optical Flow analyzes motion between neighboring frames for retiming and motion blur, while Vector Motion Blur accepts a 2D image, vector data and optional masks; its Scale control multiplies the vectors when you need a longer or shorter trail. The Resolve 21.1 reference manual also calls Optical Flow a non-real-time process whose cost depends on the computer, the clip’s resolution and its duration. The node’s Method menu offers an Advanced GPU-based algorithm, the same one used on other Resolve pages, and a Classic CPU-based one. For a long or heavy shot, the manual suggests saving the Optical Flow result to OpenEXR through a Saver, so the vectors aren't recalculated on every scrub.

Keep the analyzed range tight. Trimming MediaIn to the frames you need also spares Optical Flow the rest. Don't let the next shot into the same Fusion clip if the effect should stop at the cut; a hard edit hands Optical Flow two unrelated images and no truthful motion path between them. Footage that flickers should go through deflicker first, because brightness jumps confuse the analysis.

Use masks when one region fails

Vector analysis may nail the main subject and fall apart on a reflection, an edge or a crossing object. That doesn't mean you have to throw out the whole effect.

Use an effect mask to limit Vector Motion Blur to the region that benefits, or split the shot into separate branches and process only the useful area. Keep the mask soft enough to hide the seam, and check it across the full movement, not on one still frame.

A mask can't fix wrong vectors inside the selected region. All it does is keep the effect away from areas where the result looks worse.

Studio Motion Blur Methods

DaVinci Resolve Studio gives you faster routes when the goal is adding artificial blur to footage shot with a fast shutter, the kind that looks too crisp and strobing.

Color page Motion Effects

The Motion Effects palette on the Color page is Studio-only. Blackmagic describes its motion blur as an optical-flow-calculated effect for clips shot with a fast shutter, controlled by Motion Est. Type (Better or Faster), Motion Range and a Motion Blur amount from 0 to 100. It's the natural pick when the shot is already being finished on the Color page and you want motion estimation in the grading pipeline without building a Fusion vector chain.

Treat it as shot processing: isolate cuts, watch foreground and background crossings, and inspect the final graded image for edge tearing or duplicated detail.

Resolve FX Motion Blur

Resolve FX Motion Blur is Studio-only too. Blackmagic states that it uses optical-flow motion estimation and selectively applies blur based on the speed and direction of moving elements; it replicates the Color page Motion Effects controls so you can use them on other pages. Its controls cover Motion Est. Type, Motion Range, the blur amount, Blur Direction (both directions, from the previous frame or toward the next one) and Granularity, which sets how much detail goes into the blur. Its sibling, Resolve FX Motion Trails, is for a long, ghost-like exposure look, not natural blur.

This is the most direct native effect route on the pages where the FX is available. It's convenient, but it still lives or dies by motion estimation. Setting Motion Est. Type to Better can improve the motion map at a higher processing cost; it can't invent correct detail where an object was hidden in one frame and revealed in the next.

A paid third-party plugin may give you a different look or workflow, but you don't need one for the core task. Resolve already ships parameter-based Fusion blur, a free vector workflow and Studio optical-flow effects.

Put Optical Flow After TimeSpeed for Retimed Fusion Motion

Retime order matters because motion vectors describe one specific relationship between frames. Once TimeSpeed or TimeStretcher creates new frames, vectors calculated for the original timing no longer describe the output.

For a retimed Fusion clip, run the vector analysis after TimeSpeed and branch the retimed image into both required inputs:

MediaIn → TimeSpeed ─────────────────→ Vector Motion Blur (orange Image input)
                    └→ Optical Flow ─→ Vector Motion Blur (green Vectors input)
                                        └→ MediaOut

If TimeSpeed itself needs Flow interpolation, it can consume upstream Vector and BackVector channels. Blackmagic documents that TimeSpeed and TimeStretcher then destroy those incoming channels on output, because they're invalid after interpolation. A downstream Vector Motion Blur therefore needs a fresh Optical Flow analysis of the retimed result.

In practice:

1. Lock the speed decision first.
2. Confirm the retimed clip has the duration and frame cadence you intended.
3. Generate new motion vectors after the retiming node.
4. Add Vector Motion Blur from those new vectors.
5. Judge the blur at the final timing, especially around ramps and speed changes.

For Edit page retiming choices, clip duration and speed-ramp setup, use the change clip speed guide before building the Fusion branch. Tuning blur while the timing is still shifting underneath it is wasted effort.

Set Shutter Angle, Quality and Bias Without Hiding the Shot

The controls differ by method, but the same order of decisions holds.

Shutter Angle or blur amount

This sets how far motion spreads through time. Bigger values give longer blur and usually cost more render time. Start low enough that you can still tell whether the motion path is right, then add only what the shot needs.

A crisp action clip may need enough blur to calm the strobing. A title animation may want only a slight soft trail. A long streak can be a design choice, but past a point it stops reading as natural camera blur.

Quality

Quality usually changes how many samples are taken or how carefully motion is estimated. Raise it once the direction and amount already make sense. If the vectors are wrong at an occlusion, more samples just give you a smoother wrong answer.

Center Bias or blur direction

These controls move the trail relative to the current frame. Keep the blur visually attached to the object. An aggressive bias can make the subject look like it's leading or lagging its own position, which can work for a graphic trail but distracts in recorded footage.

Sample Spread and granularity

Sample Spread weights the samples, so it changes how bright they look in the trail; Granularity in the Studio effects sets how much detail goes into the blur. Treat both as refinement once the main movement reads correctly. Neither one is a substitute for a clean motion estimate.

Recognize Optical Flow Artifacts Early

Optical Flow works by estimating how image detail moves between neighboring frames, so the hard cases are predictable:

• two objects cross and trade visible edges;
• a moving object reveals background that was hidden in the previous frame;
• hair, foliage, fences or fine patterns change too fast;
• smoke, glass, reflections or low-contrast surfaces give it no stable features, and semi-transparent layers or soft defocused edges break its one-layer-per-pixel assumption;
• an object enters or leaves the frame;
• flashing lights or exposure changes alter pixel values without any physical movement;
• a cut sits inside the analyzed range.

The usual symptoms are rubbery edges, doubled contours, see-through fragments and blur running the wrong way. Existing motion blur in the footage is its own trap: the manual warns that the algorithm can't tell whether a blurred pixel belongs to the moving object or the background, and the error spreads into nearby regions. It also recommends running Optical Flow before compositing operations like a lens flare, and after any initial color matching or deflicker.

When that happens, change the problem instead of just raising quality:

• trim the clip to the actual shot boundaries;
• lower the blur amount;
• mask out the failing region;
• process foreground and background separately;
• patch or cover a small edge with a simpler composite;
• use a controlled Directional Blur when a stylized single direction is acceptable;
• leave a stubborn region sharper if the attempted blur draws more attention than the original strobing.

Check the first and last usable frames as carefully as the middle. Motion analysis has less neighboring information near the boundaries, and artifacts love to show up exactly where the clip starts or ends.

Keep the Composition Responsive

Optical Flow and motion blur are expensive because Resolve has to analyze frames and render several temporal samples. A sluggish composition doesn't automatically mean the node tree is broken.

While you build the shot:

• temporarily turn off the global Motion Blur button in the right-click menu of the Fusion transport controls;
• use Proxy or a lower preview quality when you're judging layout rather than blur detail;
• keep the Fusion range limited to the shot you need;
• don't stack several vector analyses without a clear reason;
• turn the effect back on for full-resolution edge and cadence checks.

Once the composition is stable, cache the expensive result. The Render Cache guide explains Smart and User cache choices and the red and blue status bars. If the whole timeline is still slow after caching that one effect, work through the broader slow playback diagnosis before you start endlessly lowering motion-blur quality.

Final Motion Blur Check

Watch the shot at normal speed, then step frame by frame through the fastest movement and the tricky overlaps.

Confirm that:

• the chosen method matches where the movement comes from;
• the blur follows the object, not some generic screen angle;
• stationary areas stay acceptably stable;
• foreground crossings don't tear or duplicate;
• the effect stops cleanly at shot boundaries;
• retimed footage uses vectors calculated after the timing change;
• the global Motion Blur switch and preview quality are back on before the final judgment;
• cached playback and the final render show the same intended result.

The key decision happens before any slider moves. Use a motion-producing node’s own Settings when Fusion creates the animation. Use motion vectors when the movement already exists in the image. Recalculate those vectors after any retime. Get that structure right and blur amount and quality become finishing touches, not guesses.

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.