Why Cycles renders are noisy
Cycles is a path tracer. For every pixel it sends out random light paths, follows them as they bounce around the scene, and averages the results. Each path is a sample. With few samples, neighbouring pixels get noticeably different random results, and you see grain. As samples increase, the average settles and the noise fades. Our explainer on ray tracing vs rasterization vs path tracing covers the theory.
Noise is worst wherever light is hard to find:
- Small or distant light sources, which few random paths happen to hit.
- Interiors lit through windows, where most light arrives indirectly after several bounces.
- Glossy and glass surfaces reflecting or refracting bright, small sources.
- Volumes like fog and smoke.
- Caustics, light focused through glass or off mirrors.
There are really three ways to reduce noise: take more samples, clean up the result with a denoiser, or make light easier to find. The best results usually combine all three. Work through the steps below roughly in order.
Step 1: Set samples and adaptive sampling sensibly
In Render Properties → Sampling → Render:
- Noise Threshold (adaptive sampling). When enabled, Cycles stops sampling pixels once they’re clean enough and spends the effort on noisy areas. Lower values give cleaner images but take longer. The default, 0.01 in recent versions, is quite strict. Many artists use something like 0.02–0.05 with denoising, and tighten it if detail suffers.
- Max Samples. The ceiling per pixel. With adaptive sampling on, this mainly caps the hardest areas. Raise it if noise persists in specific regions.
- Min Samples. The minimum before adaptive sampling can stop. Leaving it at automatic is usually fine. Raise it if small, bright details get missed.
- Time Limit. Optionally caps render time per frame, which is handy for previews.
Doubling samples reduces noise much less than you might hope: noise falls roughly with the square root of the sample count. So it often makes more sense to fix the source of the noise (Step 3) than to keep adding samples.
Step 2: Turn on denoising
Denoisers analyse the noisy image and smooth it while trying to preserve edges and texture detail. In Render Properties → Sampling → Render → Denoise:
- OpenImageDenoise (OIDN), from Intel, is a high-quality AI denoiser. It runs on the CPU and, in recent Blender versions, on supported GPUs. It’s usually the best choice for final renders.
- OptiX, from NVIDIA, runs on NVIDIA RTX GPUs. It’s very fast, which makes it great for the viewport, though for final frames many artists find OIDN preserves fine detail slightly better.
Key settings:
- Passes: “Albedo and Normal” gives the denoiser extra information about surface colours and shapes. That helps it keep textures and edges crisp, and it’s usually worth enabling.
- Prefilter: “Accurate” cleans the albedo and normal passes too, which helps in scenes with noisy textures or depth of field.
- Viewport denoising is a separate setting under Sampling → Viewport. Turning it on gives a much clearer interactive preview.
Don’t over-rely on the denoiser. With very few samples, denoisers smear detail, make textures look painterly, and produce blotches. Give them a reasonable starting image. For more control, you can enable the Denoising Data passes and use the Denoise node in the compositor.
Step 3: Fix the lighting that causes the noise
This step often makes the biggest difference, because it makes light easier for Cycles to find.
- Use bigger lights. A large area light is found by many more random paths than a tiny point light. If you want sharp shadows, keep lights small; otherwise, larger lights mean cleaner renders.
- Add light portals for interiors. Placing an area light at each window and enabling Portal in its settings tells Cycles to send more sky-light samples through the openings. This can noticeably reduce interior noise from HDRI or sky lighting.
- Don’t rely only on light through small gaps. If a room is lit mainly by sun through a narrow opening, consider adding a soft fill light inside, the way a photographer would.
- Watch emissive meshes. Glowing materials can light a scene, but small, bright emitters are noisy. In recent versions, the material’s Emission Sampling setting controls whether Cycles samples them as lights; leave it on for emitters that light the scene and off for decorative glows.
- Check the Light Tree. Under Sampling → Lights, the light tree helps Cycles choose which lights to sample. It’s very effective in scenes with many lights; with only one or two, test whether turning it off changes noise or speed.
- Let the world HDRI importance-sample. In World Properties, the sampling setting should usually stay on Auto so Cycles favours the bright parts of the HDRI, such as the sun.
Step 4: Tame fireflies
Fireflies are isolated, very bright pixels that the denoiser struggles to remove. They usually come from rare light paths, like a diffuse bounce that happens to hit a tiny bright light via a glossy surface. Fixes, in Render Properties → Light Paths:
- Clamping → Indirect. Limits the brightness of any single indirect sample. Values in the low single digits up to around 10 are common starting points. Too low will dull reflections and bounce light. The default indirect clamp is 10 in recent versions.
- Clamping → Direct. Usually left at 0 (off). Clamping direct light more easily changes the look.
- Caustics → Filter Glossy. Blurs glossy reflections slightly for indirect paths, which reduces fireflies from shiny surfaces. A value around 1 is the default; raise it modestly if fireflies persist.
- Caustics → Reflective / Refractive. Disabling these removes caustic light paths entirely. That’s a big noise reduction in scenes with glass and metal, at the cost of losing real caustic effects, which many scenes don’t need.
Clamping and Filter Glossy make the render slightly less physically accurate. That’s normally an acceptable trade, but compare before and after on important shots.
Step 5: Adjust light paths
Under Render Properties → Light Paths → Max Bounces:
- Fewer bounces generally make rendering faster and can reduce noise from long, unlikely paths, but they also darken interiors and can turn glass black if transmission bounces run out.
- Transmission and Transparent bounces need to be high enough for the number of glass layers or overlapping transparent surfaces (such as leaves with alpha) in your scene.
- Fast GI Approximation replaces later diffuse bounces with an ambient-occlusion-based approximation. It’s faster and often less noisy in interiors, but less accurate.
Our guide on how to render faster in Blender covers bounce settings from a speed point of view.
Special cases
- Volumes: Noise in fog or smoke can be reduced by increasing volume samples per material, adjusting the step rate under Render → Volumes, or using a simpler volume setup (for example, a world volume replaced by a mist pass in compositing).
- Glass: Make sure transmission bounces are sufficient. For windows, simple thin glass setups (or light-path tricks that let shadow rays pass through) can greatly reduce noise compared with fully solid refractive glass.
- Subsurface scattering: Skin and wax can be noisy at low samples; check that the scale or radius is realistic for your scene units.
- Dark interiors: Increasing exposure in post brightens noise along with everything else. Get light levels right in the scene where possible.
Noise in animations
Animated renders add problems that stills don’t have:
- Static noise pattern. By default, the random pattern can be identical every frame, which looks like dirt on the lens as the camera moves. Under Sampling → Advanced, enable the clock icon next to Seed to animate the seed so noise changes per frame and reads more like film grain.
- Denoiser flicker. Because each frame is denoised independently, small differences can cause shimmering or “boiling”, especially in dark or low-sample areas. The main fix is more samples, often a stricter noise threshold, so the denoiser has less to invent. Some external tools offer temporal denoising, which uses neighbouring frames; check compatibility with your pipeline.
- Test with a short sequence. Render 20–50 frames and play them back at full speed before committing to the full animation.
Quick troubleshooting checklist
| Symptom | Likely cause | Try |
|---|---|---|
| Grain everywhere | Too few samples / no denoiser | Enable OIDN with Albedo + Normal; lower noise threshold |
| Grain mainly in interior | Light entering through small openings | Add portals at windows; bigger or extra lights |
| Bright single-pixel dots | Fireflies from rare paths | Indirect clamp; Filter Glossy; disable caustics |
| Smeary, painterly textures | Denoiser working with too little data | More samples; Accurate prefilter; denoise passes |
| Noisy fog | Volume sampling | Increase volume samples; adjust step rate |
| Black glass | Not enough transmission bounces | Increase transmission / total bounces |
| Noise “stuck” to screen in animation | Static seed | Animate seed |
| Shimmering in animation | Per-frame denoising | Increase samples; test short sequences |
If Cycles still can’t hit your time and quality targets, check whether your scene could work in EEVEE instead; see Cycles vs EEVEE. Faster hardware also helps, as covered in GPU vs CPU rendering.