DaVinci Resolve’s built-in video noise reduction sits on the Color page, in the Motion Effects palette, and the native Temporal and Spatial controls are Studio features. I'd start with Temporal Noise Reduction. It compares neighboring frames, so it can tell random noise apart from stable image detail. Add restrained Spatial Noise Reduction only when noise is still sitting inside individual frames.
This page is about visible picture noise: colored speckles, crawling shadows, coarse low-light texture and unstable grain. For hiss, hum or room sound, go to the separate Fairlight background-noise guide. Video NR and audio cleanup are different systems.
| What you see | First response | Main risk |
|---|---|---|
| Random noise changes from frame to frame | Start with Temporal NR | Ghosting or trails around movement |
| Fine noise remains within each frame | Add restrained Spatial NR | Soft texture, waxy skin or unstable edges |
| Noise is limited to one dark area or color range | Use a tracked window or qualifier | A visible correction boundary |
| Audio hiss, hum or rumble | Move to Fairlight | Treating the wrong problem |
Identify the Noise Before Changing Controls
Noise reduction repairs a problem. It can't stand in for correct exposure or color management. Before you touch a control, play a representative moving section at roughly the size your audience will watch it. Include a face, hair, fabric, foliage, text or something else with real fine detail. Those areas give away excessive processing much faster than a flat wall does.
Separate the problem into the closest category:
- Luma noise: unstable brightness texture, often most obvious in shadows and flat surfaces.
- Chroma noise: colored red, green or blue speckles that can distract even when the image does not look heavily grainy.
- Banding or fixed-pattern structure: repeating lines or broad tonal steps that general denoising may soften without truly repairing.
- Compression artifacts: block edges and mosquito noise. They come from limited encoding information, and they look different from ordinary sensor noise.
- Intentional film grain: a chosen texture that belongs to the look. Remove it and you've changed the finish. No capture problem got fixed.
If the noise only shows up after you lift the shadows, the grade is exposing a weakness that was already in the source. If a log or HDR clip is interpreted incorrectly, fix that transform first. The RCM and CST guide covers that decision. While you judge the cleanup, switch off strong sharpening, added grain and texture effects, so no other node exaggerates what the NR node is trying to remove.
Add a Dedicated Noise-Reduction Node
Open the Color page, create a serial node for noise reduction, then open the Motion Effects palette. With cleanup in its own node, a bypass comparison takes one click, and the repair settings stay apart from the balance and the look. The nodes guide explains how serial nodes pass the image from left to right.

Blackmagic's Studio page lists Temporal NR and AI Spatial NR, and it counts AI UltraNR among the extra Resolve FX. The manual marks the whole Motion Effects palette as Resolve Studio only. If the controls are missing, check the installed edition before you hunt for a hidden preference. The Free-version feature guide and Free versus Studio comparison explain the wider edition boundary.
Use Temporal Noise Reduction First
Temporal NR averages several frames. That makes it good against random sensor noise, and it also means Resolve has to tell noise apart from movement. Its motion estimation tries to leave moving subjects out of the averaging so they don't smear. Build the first pass on a moving section. A convenient still frame will flatter it.
- Keep the treatment on a separate, bypassable node.
- Start with a low Number of Frames (the menu runs from 0 to 5) and restrained thresholds.
- Play through the fastest or most detailed movement in the shot.
- Compare a noisy shadow with a moving edge and a textured subject.
- Push further only while the leftover noise distracts more than the detail you're losing.
More frames can calm a stable background and make motion harder to read at the same time. The manual notes that a value of 1 may work better on fast-moving images, and every extra frame costs a lot of processing. A turning face, a hand crossing dark clothing, hair against the sky or a branch moving in low light will show you the tradeoff quickly.
Luma Threshold and Chroma Threshold start out ganged, so one slider moves both. Unlink them when colored speckles are the bigger problem, because chroma usually takes more cleanup than luma before artifacts show. Motion Est. Type (Faster, Better or None) and Motion Range (Small, Medium or Large) tell Resolve how much movement to expect. Motion Threshold, at 50 by default, decides how much of the moving image stays out of the averaging. Match them to the shot.

Watch for ghosting, smearing and crawling edges. Ghosting leaves a soft echo behind movement. Smearing wipes out the crisp transition around a moving object. Crawling edges make hair, foliage or small type shimmer from frame to frame. When one of these appears, back off the temporal processing, or lower Motion Threshold so more of the movement is excluded.
Add Spatial Noise Reduction Only for What Remains
Spatial NR works inside a single frame. It cleans up residue that Temporal NR leaves behind, and it still reaches areas in motion, where neighboring frames differ too much for a stable temporal result. Its weakness is just as direct: smoothing neighboring pixels can take real texture away along with the noise.
The Mode menu offers Faster, Better, Enhanced and UltraNR. Blackmagic's own procedure recommends Enhanced for the best results and Faster when you need real-time playback. Better can't unlink the Luma and Chroma thresholds. Raise the linked thresholds slowly and leave Radius at Small or Medium unless detail starts to look chunky or aliased. Then inspect skin, hair, fabric weave, brick, leaves, small highlights and fine type, which vanish first when spatial cleanup is too strong.
Push spatial cleanup too far and you get a waxy, painted surface. Broad shapes stay sharp while pores, fibers and natural surface variation disappear. Smoother isn't automatically better. Leave some texture whenever removing it would make the shot look synthetic. If the settings are right but the result feels too processed, raise NR Blend to mix some of the untreated image back in.
UltraNR is the AI-based choice in the Spatial NR Mode menu, and the Resolve FX noise reduction effect offers it too. Click Analyze and it samples a flat area of the frame to set its luma and chroma levels. Turn on Show Patch to see that sample box, and drag it to a cleaner flat area if Resolve picked a poor spot. No mode rescues every noisy clip, so the same motion and detail checks apply.
Choose Node Order by the Visible Problem
A useful starting structure puts a dedicated NR node near the beginning of the grade, before the main balance and look. Later corrections get a cleaner signal. Blackmagic's manual describes the tradeoff: noise reduction at the start of the tree tends to look smoother with slightly softer edges, while a separate node at the end keeps edges visibly sharper and leaves the result a little less smooth.
A source transform, an exposure correction or a creative look can change which noise you see. If the grade lifts shadows hard, compare the early NR node with a later placement on the actual shot. Keep whichever version removes the distraction with the least damage to edges and texture.

When the noise sits in one part of the frame, limit the NR node with a Power Window or an HSL qualifier. The manual suggests exactly this for shadows and background regions, so faces and better-lit areas stay untouched. Soften the selection edge and track it if the subject moves. A hard or drifting mask can leave a halo that's more noticeable than the original noise.
Judge Noise Reduction in Motion
A paused frame is fine for checking texture. Playback shows the failures a still image hides, so review the correction through:
- a face turning or a hand moving across the frame;
- hair, grass, leaves, fabric or another fine repeating texture;
- small lights against a dark background;
- an edge crossing a flat area;
- a fast pan, focus change or exposure change;
- the cut into and out of the corrected shot.
If the subject softens only while it moves, look at the temporal pass first. Reduce the spatial pass when fine texture disappears in every frame. If an artifact appears only at a shot boundary, check the neighboring clip and the node structure before you change the whole correction.
Troubleshoot Common Noise-Reduction Failures
The image looks plastic. Reduce Spatial NR or raise NR Blend, then inspect skin, hair and fabric at the delivery size. A bit of leftover texture almost always beats a painted surface.
Moving objects leave trails. Drop the Number of Frames, lower Motion Threshold, or try Better motion estimation with a larger Motion Range. Check the fastest movement during playback with the NR node bypassed and enabled.
Edges crawl after denoise. Look at fine contrast boundaries and lower the treatment. If detail looks chunky or aliased under heavy Spatial NR, a larger Radius can help. Also check whether sharpening or a later look node is exaggerating the remaining pattern.
Noise remains in one region. Put a restrained tracked window or qualifier on that area and leave the whole-frame correction alone. Watch the selection edge while the shot moves.
The controls are unavailable. Check the installed edition. The Motion Effects palette is Studio only, and this guide follows the control names in the DaVinci Resolve 21.1 manual.
The viewer looks clean but the export does not. Render a short proof at the delivery resolution and inspect it in motion. If contrast or gamma also changes, use the export color and gamma guide to separate a display or color-management problem from denoising.
Manage Performance Without Changing the Creative Decision
Temporal analysis and higher-quality spatial processing can slow playback. The manual is blunt about the cost: more frames dramatically increase render time, and larger Radius settings and the Enhanced mode are processor intensive. The real cost depends on source format, resolution, hardware and the rest of the node tree.
If playback is too slow to judge motion, use the Render Cache workflow for the affected clips or work through the slow-playback checklist. Caching won't make the NR settings any better. It gives Resolve time to prepare frames, so you can review those settings at a useful playback rate.
How Much Noise Reduction Slows Resolve in Published Tests
In published Resolve Studio tests, adding native noise reduction made a color-corrected export take about four times as long, and UltraNR runs took six to thirteen times as long. On the one-minute UHD RAW timeline from postPerspective’s RTX 4070 Ti review and four other reviews, Resolve NR took a median 4.3 times the color-only export time across seven Resolve 18 machines, or 83 extra seconds for one minute of footage. In the PugetBench results database, a single two-frame Temporal NR pass averaged 71 fps on an RTX 5090 and 15 fps on an M4 Pro, and three stacked passes ran at about 31% of the single-pass speed.
| Test | Result | Published results |
|---|---|---|
| Resolve NR added to a color-corrected one-minute UHD RAW timeline, Resolve 18 | Median 4.3x the color-only export time (2.5x to 7.9x), or 83 extra seconds (33 to 124) | 7 machines in 5 postPerspective reviews: RTX 4070 Ti, RTX 4070 SUPER, RTX 4090, Radeon PRO W7800 and W7900, RTX A6000, ZBook Fury 16 G10 |
| Same timeline on an RTX 5090, Resolve 19.1.1 | 1.8x (28 to 51 seconds) | 1: postPerspective |
| Neat Video instead of Resolve NR, same timeline and machine | Median 1.9x Resolve NR’s time (1.3x to 2.8x) on the 7 Resolve 18 machines; 1.6x with Neat Video 6 on the RTX 5090 | 8 machines from the same postPerspective reviews |
| UltraNR added to the same timeline | 12.9x the color-only time on an RTX 3500 Ada laptop (Resolve 19.0.1), 8.6x on an RTX PRO 2000 Blackwell laptop (20.1.1), 5.8x on an RTX PRO 6000 Blackwell desktop (21.0 beta) | 3 postPerspective reviews: ZBook Fury 16 G11, ZBook X G1i, Z4 G6i |
| UltraNR vs Neat Video, same machine | 1.4x and 2.6x Neat Video’s time on the two laptops, 0.6x on the RTX PRO 6000 desktop | Same 3 postPerspective reviews |
| Temporal NR, 2 frames, Better, average fps | RTX 5090 71, RTX 4090 51, RTX 5080 48, RTX 5070 Ti 43, RX 9070 XT 41, RTX 5070 37, M4 Max 30, RTX 5060 Ti 24, M4 Pro 15 | PugetBench database, 13 to 602 uploads per GPU: RTX 5090 and 5080, RTX 4090, RTX 5070 Ti and 5060 Ti, RTX 5070 and RX 9070 XT, M4 Max and M4 Pro |
| Three stacked Temporal NR nodes vs one, same GPU | Median 31% of the single-node fps (30.6% to 32.4%) | 7 GPUs in the PugetBench database |
| Spatial NR, Better, vs Temporal NR, 2 frames, same GPU | Median 1.4x the Temporal fps (0.8x on the RX 9070 XT to 1.7x on the RTX 4090) | 7 GPUs in the PugetBench database |
Method: the postPerspective rows come from one reviewer’s one-minute UHD timeline of ARRI RAW, Blackmagic RAW, RED RAW and Sony a7S III clips, timed at the H.265 export, with proxies and caching off where the reviews describe the setup. Only the RTX A6000 review lists its Resolve NR settings, two-frame Temporal NR with Faster motion estimation plus Better Spatial NR, so the NR load may differ between reviews. Every multiple divides two exports from the same machine, so no figure mixes hardware or Resolve versions. One more UltraNR run, on an HP ZBook Fury G1i 18-inch with Resolve 20.2.2, is left out because its color-only export took longer than its Neat Video export. The database figures average user uploads to PugetBench for DaVinci Resolve 2.0 and 2.1 on Resolve 20.0 to 21.1, where each effect runs on a UHD DNxHR LB clip exported to HD on mixed systems. The two ratio rows divide averages from the same GPU and leave out any GPU with fewer than 10 uploads for a test.
My verdict: I’d start with Temporal NR at two frames and add frames, Spatial NR or UltraNR only on shots that still show noise, because each step costs real render time. Resolve NR already took a median 4.3 times the color-only export on postPerspective’s timeline, UltraNR took 5.8 to 12.9 times, and three stacked Temporal nodes left seven database GPUs at about 31% of their single-node speed. On a tight deadline I’d keep Resolve’s built-in NR ahead of Neat Video, since Neat took longer on all eight machines in those reviews. UltraNR is the one I’d check per machine: it beat Neat Video only on the RTX PRO 6000 desktop running the Resolve 21 beta and took 1.4 and 2.6 times Neat’s time on the two laptops.
What to Do in DaVinci Resolve Free
DaVinci Resolve Free doesn't include the native Temporal and Spatial NR controls covered here. In the Free edition, make the source easier to grade: correct the input color space, don't lift shadows further than the image supports, cut unnecessary sharpening and use targeted color work so the noisy region doesn't dominate.
Controlled softening on a qualified area can hide distracting texture. It still isn't motion-aware noise reduction, and I wouldn't call it an equivalent. If low-light cleanup comes up on most of your projects, compare the cost and workflow of Studio with an external denoising tool. Compatibility, render handoff and licensing matter as much as a short visual demo.
Video Noise Reduction Checklist
- Confirm the problem is picture noise. Hiss and hum belong in Fairlight.
- Fix color-management and exposure interpretation before judging the source.
- Decide whether you are seeing luma noise, chroma noise, banding, compression or intentional grain.
- Use a dedicated serial node and compare it with bypass.
- Start with restrained Temporal NR and review real movement.
- Add Spatial NR only for frame-level noise that remains.
- Inspect faces, hands, hair, fabric, foliage, text and moving edges.
- Back off at the first sign of ghosting, waxy texture, smearing or crawling edges.
- Render a short proof when the correction matters to the final delivery.
- Use caching when playback performance prevents a fair motion check.
For feature availability, check Blackmagic's Color page overview, Studio feature page and What’s New page. What holds up stays simple: identify the noise, use temporal information only while motion stays natural, add spatial cleanup only where it earns its place, and judge the result while the footage moves.
