Reducing Noise in Blender Cycles: A Sampling and Denoising Guide

What will you learn in this guide?

There are two main ways to reduce noise in Cycles: take more samples from the scene and use denoising to clean up the resulting noise. The first method can increase render time; the second aims to produce a clean image with fewer samples, but details may look softer if additional passes are not used. This guide explains how to evaluate sample counts, what Adaptive Sampling does, which denoising options are available, and how to use the Denoise node in the Compositor.

The goal is not to recommend a single ideal value for every scene. In interiors, light coming through small openings, surface textures and fine edges can all affect how noise appears. Settings should therefore be considered in light of the balance between image quality and render time.

Requirements and limitations

You need a scene prepared in Cycles in Blender, along with a render result. To denoise through the Compositor, you can enable the “Denoising Data” pass in the Cycles View Layer to output Denoising Albedo and Denoising Normal data. The manuals do not specify a required Blender version or hardware requirement, so you should not assume that a particular version or setup is required.

The GPU denoising option uses additional GPU memory. If this becomes an issue in large scenes, GPU denoising can be disabled. Path guiding is available only for CPU rendering. The manual also refers readers to the GPU Rendering page for supported GPUs; hardware compatibility is not detailed in these materials.

Step-by-step noise reduction

1. First, understand the effect of render samples

Cycles calculates an image by sending rays from the camera into the scene and tracing their paths until they reach a light source. Render (Max) Samples sets the number of paths traced per pixel in the final render. Increasing the value generally produces a cleaner image, but also increases render time. Increasing the sample count should therefore not be treated as a one-size-fits-all solution to apply indefinitely in every scene.

Viewport (Max) Samples applies to the 3D Viewport in Rendered view mode. Setting this value to zero means sampling continues indefinitely. Time Limit also stops rendering when the specified time is exceeded, even if the sample target has not been reached; a value of zero disables the time limit. This limit does not include the time taken by pre-render operations.

2. Try Adaptive Sampling

When Noise Threshold is enabled, Adaptive Sampling can stop sampling early for pixels that have reached a sufficiently low noise level. This allows areas that need more samples to keep rendering while avoiding unnecessary work in parts of the image that already look clean enough. The typical Noise Threshold range in the Blender manual is 0.1 to 0.001. A lower threshold targets higher quality but increases render time. If the value is zero, Cycles automatically estimates a value based on the total sample count.

Min Samples sets the minimum number of samples a pixel receives before Adaptive Sampling is applied. When the value is zero, Cycles automatically chooses this number based on the Noise Threshold. When evaluating these settings, check not only the overall image but also detailed surfaces and areas where noise is more noticeable.

3. Choose a denoising method and input data

Denoising reduces noise without calculating more samples. Denoising can be selected separately for the viewport and final render in the Cycles settings. The denoiser also affects the result: Automatic uses GPU-accelerated denoising if available and prefers OpenImageDenoise over OptiX. According to the manual, OpenImageDenoise generally delivers the highest quality. OptiX is available on some older NVIDIA GPUs when configured in Cycles Render Devices preferences.

The Passes setting, which determines which render passes the denoiser uses, is important. Blender recommends using at least Albedo; the None option can blur details, especially at low sample counts. Albedo + Normal uses the albedo and normal passes in addition to color data.

4. Set up the Denoise node in the Compositor

The Denoise node can be used to clean up noisy images from Cycles and other ray-tracing renders. For better results with Cycles, first enable Denoising Data in the View Layer properties, then render. This generates passes such as Noisy Image, Denoising Albedo and Denoising Normal.

In the Compositor, connect the Noisy Image output to the node’s Image input, and connect the Denoising Albedo and Denoising Normal outputs to the corresponding inputs. This additional data helps preserve edges, textures and fine details. The Denoise node can also work without the additional passes, but the result may look softer or lose detail.

5. Balance quality and processing time for your scene

The Prefilter options for OpenImageDenoise offer different trade-offs. None prioritizes detail and speed but assumes the input passes are noise-free. Fast is quicker but can produce a blurrier result. Accurate prefilters the passes to reduce noise and generally produces a more detailed result than Fast, at the cost of additional processing time.

Among the Quality options, High delivers the highest quality at the cost of longer processing time. Balanced strikes a balance between speed and quality. Fast sacrifices quality for a quick result. Comparing different results from the same scene is a more reliable way to evaluate these options than applying one setting to every project.

Common mistakes

• Relying on denoising alone with a low sample count can soften fine textures or edges. Using Albedo and Normal passes helps preserve this information.

• Don’t assume that lowering the Noise Threshold will make rendering faster. According to the manual, a lower threshold targets higher quality and can increase render time.

• When None is selected for Prefilter, keep in mind that noisy inputs may remain noisy after denoising.

• Don’t assume GPU denoising comes with no memory cost: processing may be faster on the GPU, but it requires additional GPU memory.

• Don’t look for path guiding in GPU rendering; this feature is available only when rendering on the CPU.

Effects on architectural visualization workflows

Interior visualization teams and students can use these settings, particularly when balancing render time against a clean image. Adaptive Sampling takes into account the number of samples different regions need, while denoising offers a way to reduce noise with fewer samples. However, details such as material textures, fine edges and scene lighting should still be checked in the result.

When deciding on a workflow, consider GPU memory, the denoising method and whether the required passes are available. OpenImageDenoise and OptiX have different requirements; OptiX requires an NVIDIA GPU and configuration in Cycles Render Devices. In shared workflows or across different hardware, don’t standardize on a single setting without comparing results. The manuals also note that render samples can be split into subsets across different machines and combined afterward; for this method, denoising must be disabled, and each subset must be configured to match the total sample count.

Next steps

First, evaluate the sample count and Noise Threshold under the same camera and lighting conditions, then compare denoising options. Inspect the final image not only for overall brightness but also for textures, edges and fine details. If you use the node in the Compositor, make sure the Denoising Albedo and Denoising Normal passes are connected to the correct inputs. If GPU memory is a constraint in large scenes, also check the effect of disabling GPU denoising.

Sources and license

This guide was translated and adapted from the “Sampling” and “Denoise Node” pages in the Blender Manual. Both sources are published under the CC BY-SA 4.0 license.