Blender Cycles Denoising for Animation (2026): OpenImageDenoise vs OptiX, Passes and Flicker-Free Sequences
Cycles offers two AI denoisers, OpenImageDenoise and OptiX. Feeding them the Albedo and Normal passes keeps detail, and the Manual recommends at least Albedo. Most flicker in denoised animations comes from too few samples, so the denoiser guesses differently on each frame; fix the noise first, then denoise.
- Denoiser: OpenImageDenoise typically gives the highest quality; OptiX runs on NVIDIA GPUs.
- Passes: Albedo + Normal; color alone can blur detail at low sample counts.
- OIDN options: Prefilter Accurate keeps more detail; Quality High is best at extra time.
- Animation: enable Use Animated Seed and check several frames in playback, not one still.
A denoiser can turn a grainy Cycles frame into a clean one in seconds, but on an animation the same setting can leave blotches that crawl from frame to frame. The difference is rarely the denoiser itself; it is how much noise the denoiser had to remove.
This guide covers the two denoisers in Cycles, the passes and options that control them, why denoised sequences flicker, and how to keep the option to denoise again later. For grain and fireflies in general, see pixelated and grainy renders in Blender.
Checked against the Blender Manual (Sampling, GPU Rendering, Denoise node), November 2026.
1. OpenImageDenoise or OptiX?
The Manual lists three choices under Render › Sampling › Denoise: Automatic, which uses GPU-accelerated denoising if supported and prefers OpenImageDenoise over OptiX; OpenImageDenoise, Intel’s AI denoiser, which typically provides the highest quality; and OptiX, NVIDIA’s AI denoiser, which is only available on NVIDIA GPUs configured in the Cycles Render Devices preferences (Blender Manual: Sampling). The GPU Rendering page adds that GPU acceleration for OpenImageDenoise is available on compute capability 7.0 and higher, which includes all NVIDIA RTX cards (Blender Manual: GPU Rendering).
OpenImageDenoise vs OptiX in Cycles
What the Blender Manual says about each denoiser and its options.
| OpenImageDenoise | OptiX | |
|---|---|---|
| Made by | Intel | NVIDIA |
| Manual says | Typically provides the highest quality | Supports GPU acceleration on some older NVIDIA GPUs where OpenImageDenoise does not |
| Runs on | CPU, or GPU where supported (NVIDIA compute capability 7.0+, all RTX cards) | NVIDIA GPUs configured in Cycles Render Devices |
| Extra options | Prefilter (None, Fast, Accurate) and Quality (High, Balanced, Fast) | Passes only |
| Automatic setting | Preferred when both are available | Used if OpenImageDenoise cannot run on the GPU |
2. Passes, prefilter and quality
Passes control which inputs the denoiser uses: None (color only), Albedo (color and albedo) or Albedo + Normal. The Manual says the more passes the denoiser has, the better the result, and recommends at least Albedo because None can blur out details, especially at lower sample counts.
With OpenImageDenoise, Prefilter decides how the guide passes are cleaned first: None keeps the most detail and is fastest but assumes noise-free passes; Fast is quicker but blurrier; Accurate prefilters the passes and usually gives more detailed results than Fast, with more processing time. Quality High gives the best result at the cost of time, with Balanced and Fast as quicker options.
3. Why denoised animations flicker
The denoiser works from the passes of the frame it is cleaning. When a frame has little noise, there is little to guess and consecutive frames come out the same. When the input is very noisy, the denoiser fills in more, and its guesses differ slightly from one frame to the next. The result can look clean as a still and still boil or flicker in playback.
Fixes, in order:
- Lower the noise first. Lower the Noise Threshold or raise Max Samples; the Manual gives typical Noise Threshold values from 0.1 to 0.001, lower meaning better quality and longer renders.
- Use Albedo + Normal with Prefilter Accurate and Quality High for final frames.
- Enable Use Animated Seed under Sampling › Advanced. The Manual recommends it for animations because a varying noise pattern is less noticeable.
- Be careful with Scrambling Distance. The Manual describes it as reducing randomness between pixels to improve GPU performance, at the cost of potential artifacts; keep it on Automatic or off for final animations if you see patterns.
- Judge in motion. Render three or four consecutive frames and play them back before the full sequence.
4. Denoise during the render or afterwards
Denoising in the render settings is simplest: the saved frames are already clean. If you want to keep the option to change the denoiser later, enable the Denoising Data render pass; the Manual notes that you can then denoise in the compositing step with the Denoise node instead (Blender Manual: Sampling, Denoise node). Save the noisy beauty and the passes to a multilayer EXR, and you can try both denoisers on the same frames without rendering again. Our guide to compositing an animation in Blender covers the EXR workflow.
Route A gives final files straight away; route B costs disk space for the extra passes but lets you compare OpenImageDenoise and OptiX, or change Quality and Prefilter, on frames that are already rendered.
A denoising checklist for Cycles animations
- Noise: Noise Threshold and Max Samples set so the raw frame is not very grainy
- Denoiser: OpenImageDenoise or OptiX tested on the same frames
- Passes: Albedo + Normal
- OIDN: Prefilter Accurate, Quality High for final frames
- Seed: Use Animated Seed on for animations
- Playback: three or four consecutive frames checked in motion
- Safety net: Denoising Data and noisy beauty saved to multilayer EXR if you may re-denoise
For the settings to check before any farm render, see our 10-point Blender Cycles pre-flight checklist.
On a submission (SaaS) farm, the denoise settings saved in your .blend are applied to every frame, which suits approved looks. On an IaaS server you can render a few frames, compare OpenImageDenoise and OptiX in playback and change samples before committing to the whole sequence.
Testing denoising on an iRender server
- Upload the project folder to iRender Drive before you start the server; uploading is free and does not use rental time.
- Start a server with RTX 5090 (32 GB) or RTX 4090 (24 GB) GPUs and connect by remote desktop.
- Render four consecutive frames with each denoiser and play them back.
- Render the sequence with the settings that stay stable in motion, then shut down; multi-GPU servers are billed per minute.
Frequently asked questions
1. Which denoiser is better in Blender Cycles, OpenImageDenoise or OptiX?
The Blender Manual says OpenImageDenoise typically provides the highest quality, while OptiX runs on NVIDIA GPUs and supports GPU acceleration on some older cards. Test both on a few frames of your own shot.
2. Why does my denoised Blender animation flicker?
Usually the input is too noisy, so the denoiser guesses differently on each frame. Lower the Noise Threshold or raise samples, use Albedo + Normal passes, and enable Use Animated Seed.
3. Which passes should I use for denoising?
Albedo + Normal. The Manual recommends at least Albedo, because color alone can blur details, especially at low sample counts.
4. Does OpenImageDenoise run on the GPU?
Yes, on supported GPUs. The Manual lists GPU acceleration for OpenImageDenoise on NVIDIA compute capability 7.0 and higher, which includes all RTX cards.
5. Can I denoise after rendering?
Yes. Enable the Denoising Data pass, save to multilayer EXR, and use the Denoise node in the compositor.
6. What does Use Animated Seed do?
It changes the noise pattern on each frame. The Manual recommends it for animations because a varying noise pattern is less noticeable.
Render your Blender projects on iRender
iRender is an IaaS GPU render farm: you rent a bare-metal server with 1, 2, 4 or 8 NVIDIA RTX 4090 (24 GB) or RTX 5090 (32 GB) GPUs, an AMD Ryzen™ Threadripper™ PRO CPU, 256 GB ECC RAM and a 2 TB NVMe SSD, connect by remote desktop and work on it like your own workstation, with full administrator access. You install Blender once; your server image is saved between sessions, so Blender and your add-ons stay installed.
Multi-GPU servers are billed per minute (1-GPU servers have a one-hour minimum), and sessions of 3 hours or more get 10% off. Our 4-GPU and 8-GPU servers are liquid-cooled; in our own measurements the GPUs hold 60–70°C under sustained render load. Elite support is available 7 days a week by hotline, live chat, Skype, WhatsApp and email.
This quick start shows how to start a server and render Blender on it:
Two Blender runs we recorded on our servers: 120 frames at 1080p on 4x RTX 5090 at 72 seconds per frame, and the same 4K scene on 4x RTX 5090 and 4x RTX 4090 at 87 and 108 seconds per frame per GPU:
New users get a 100% bonus on the first top-up (minimum $50). See plans on the Blender render farm page or download the iRender GPU app.




