Enabling and Fine‑Tuning the Cycles Denoiser in Blender

Desired outcome

Render a scene with Cycles while reducing image noise using the built‑in denoiser, keeping the ability to inspect the effect and revert if needed.

Prerequisites

• Blender 3.0 or newer (the denoiser UI is stable from this version).
• A scene set up to render with Cycles (CPU or GPU).
• If you plan to use the OptiX denoiser, an NVIDIA RTX GPU with driver version ≥ 470 and CUDA toolkit installed.

Focused procedure

1. Open the Render Properties panel

   In the Properties editor, click the camera icon to open Render Properties.

2. Select the render engine

   Set Render Engine to Cycles. Choose CPU, GPU, or CPU+GPU in the Device dropdown according to your hardware.

3. Enable denoising

   Scroll to the Denoising section. Check the box Denoise.

4. Choose a denoiser type

   From the Denoiser dropdown select:

   • OpenImageDenoise – works on CPU and any GPU (default).
   • OptiX – requires an NVIDIA RTX card; uses hardware‑accelerated ray tracing.
   • Nvidia OptiX – same as OptiX but exposed for explicit selection; offers the lowest overhead on supported GPUs.

   If you are unsure, start with OpenImageDenoise; it is safe on all hardware.

5. Set denoising passes

   Below the denoiser selector, adjust Denoising Passes. A value of 1 is suitable for quick previews; 2 gives a cleaner final image with modest extra time and memory. Higher values (>2) are rarely needed and increase memory noticeably.

6. Limit denoising to the final image (optional)

   If you need to keep raw data for compositing (e.g., depth or normal passes), uncheck Denoise for Passes and leave only Final enabled. This preserves the original passes while denoising the combined result.

7. Render a test frame

   Press F12 (or click Render → Render Image) to produce a single frame. Observe the denoised output in the Image Editor.

Expected checks

• Visual verification: Open the rendered image, then enable the Side‑by‑Side view in the Image Editor’s header and toggle Difference mode. The difference view should show mostly dark areas (low residual noise) while preserving edges and fine details.
• Memory usage: In the same Properties editor, go to the Performance tab. Note the Memory value before and after enabling the denoiser; expect an increase of roughly 2‑4 GB for a 1920×1080 render on CPU and slightly less on GPU, depending on scene complexity.
• Device utilization: Open the Statistics window (Window → Toggle System Console or Window → Statistics) and confirm that the reported Device matches your selection (CPU, GPU, or CPU+GPU) and that denoiser activity appears as an extra step in the render log.

Recovery options

• If the denoised image looks overly smooth or you notice loss of fine geometry/texture, reduce Denoising Passes to 1 or switch to a less aggressive denoiser (e.g., from OptiX to OpenImageDenoise).
• Should GPU memory exceed available VRAM and cause a crash, disable denoising, render on CPU only, or lower the render resolution.
• To revert all denoiser settings, simply uncheck Denoise in the Denoising section; the render will proceed without any denoising overhead.

Example configuration

# Render Settings (Properties → Render)
Engine: Cycles
Device: GPU (NVIDIA RTX 3060)

# Denoising
Denoise: ✓
Denoiser: OptiX
Denoising Passes: 2
Denoise Final Only: ✓   # keep raw passes for compositing

# Expected outcome
# - Noticeable noise reduction in the beauty pass
# - Depth and normal passes remain unchanged
# - Approx. +3 GB GPU memory vs. denoise‑off render

Limitations and practical verification
The denoiser works best on samples that already contain sufficient anti‑aliasing noise; extremely low sample counts may produce artifacts that the denoiser cannot fix. Always compare denoised output against a reference render with the same sample count but denoiser disabled, using the difference view as described above. If the difference shows structured patterns (e.g., banding), increase the sample count or reduce the denoising passes.