A Blender Cycles fireflies fix starts with the cause: caustics, close lights, bright shader colors, bounces or small bright spots in the environment. Here is a safe order to follow.
Key points
Fireflies in Cycles are single pixels that render far brighter than their neighbours. They appear when a light path is hard to find but carries a lot of energy, so the best Blender Cycles fireflies fix is to remove the cause first and clamp only as a last step.
FOCUS: BLENDER CYCLES FIREFLIES FIX
- Fireflies come from rare, high-energy light paths, not from too few samples alone.
- The Blender manual names caustics, near-zero light distances, shader colors close to 1.0, many bounces and small bright spots in environment maps as typical sources.
- Work in this order: crop test, caustics, Filter Glossy, bounces, shader colors, environment map, then clamp indirect light.
- Clamping and Filter Glossy trade accuracy for less noise, so check a crop before you commit a full animation.
- In an animation the dots land on different pixels every frame, which reads as flicker.
You raise the samples, switch on the denoiser, and a handful of white dots are still there. A reliable Blender Cycles fireflies fix starts with knowing what those dots are. They are not ordinary grain. Each one is a sample that carried far more light than the samples around it, and the pixel that caught it now reads as a hot spot.
What fireflies are in Cycles
The Blender manual describes fireflies as the result of a light path that has a low chance of being found but contributes a lot of light. One pixel happens to find that path and comes out very bright. The pixel next to it does not, and stays normal. That uneven luck is why fireflies look like scattered dots rather than a smooth wash of noise.
A pixel is an average of its samples, so a single very bright sample drags the average up and it takes many ordinary samples to dilute it. Doubling the sample count therefore makes fireflies rarer, but it rarely removes them. The general case of a render that stays noisy at high sample counts is covered in render still noisy with high samples. This guide stays with the isolated bright dots.
Six common causes of fireflies in Cycles
The manual page on reducing noise lists the usual sources. Table 1 pairs each one with what it looks like on screen and the first fix to try, together with what that fix costs you.
| Cause | What you see | First fix | What it costs |
|---|---|---|---|
| Caustics | Speckles under glass, water or shiny surfaces | Turn off Reflective and Refractive caustics | Removes some legitimate light |
| Light very close to a surface | Hot spots on nearby walls and props, mostly in indirect light | Move the light or use the Light Falloff node Smooth factor | Lowers the intensity of nearby light |
| Shader colors close to 1.0 | Fireflies in bright, white interiors | Keep color components around 0.8 or below and raise the light strength instead | Small change in material look |
| Many light bounces | More noise in complex interiors | Lower the total or per-type bounces, or use the limited global illumination preset | Glass needs bounces and can lose realism |
| Small bright spots in an environment map | Sparkles in scenes lit by an HDRI | Enable World Multiple Importance and check the map | Takes samples from brighter lights |
| Sharp glossy reflections after blurry bounces | Bright pinpoint reflections | Raise Filter Glossy, starting near 1.0 | Softens highlights |

A fix order that does not wreck the look
Each fix below changes the image, so the order matters. Start with the changes that remove light you do not need, and leave the ones that dim everything for the end. Treat this as the order that preserves the most accuracy, not as the only valid one.
- Render a crop. Use the render region in the viewport and keep one frame where the fireflies are obvious. Every test below is a few seconds instead of a few minutes.
- Turn off caustics. In Render Properties, open Light Paths and uncheck Reflective and Refractive under Caustics. Skip this step if the scene depends on caustics, for example a glass of water as the hero object.
- Set Filter Glossy. The manual suggests 1.0 as a starting point. Check highlights afterwards, because the blur can soften them noticeably.
- Trim the bounces. Lower the total or the per-type limits and look at glass and interiors again, because fewer bounces reduce realism there.
- Lower the shader colors. Keep color components around 0.8 or below and make the lights brighter to compensate.
- Check the environment map. If an HDRI has small bright spots, World Multiple Importance sends rays toward them. It can take samples from brighter lights, so expect some trial and error.
- Clamp last. Set Clamp Indirect Light first, because indirect bounces cause more fireflies, and compare against 0, which disables clamping.

How clamping works and what it costs
Clamping caps the intensity a single sample can add to a pixel. It is effective and it is blunt, which is why the manual presents it as a trade of accuracy for less noise. A clamp set too low can remove highlights you may want for camera effects such as bloom or glare. The manual shows a comparison between no clamp and a value of 4, and that value is an example from the comparison, not a target for your scene.
| Setting | What it limits | Best used for | Side effect |
|---|---|---|---|
| Clamp Indirect Light | Rays that have bounced several times | First choice for fireflies | Dims bounced lighting |
| Clamp Direct Light | Rays that have not bounced yet | Blown direct highlights | Dims bright lights and reflections |
| Filter Glossy | Blurs glossy reflections after blurry bounces | Pinpoint reflections | Softens highlights, can lose detail |
| Caustics off | Removes caustic light paths | Glass, water and shiny floors | Loses some legitimate light |
Why more samples and the denoiser do not fully fix fireflies
A denoiser works from neighbouring pixels. A very bright isolated pixel can be kept as detail or spread into its surroundings, depending on the denoiser and the frame, so denoising a firefly-heavy image is a gamble. In practice you clean the source first, then denoise, and you compare a crop before and after. If the denoiser then removes fine detail, denoiser losing detail in animation explains how to tune it without smearing the frame.
Adding samples has the same limit. It lowers the chance that any given pixel catches a rare path, but a pixel that does catch one still carries the full spike. Clearing the cause costs less than rendering at four times the samples, and it keeps working when the frame count goes up.
Fireflies in an animation
In a still image a few fireflies can be painted out. In an animation they cannot, because each frame samples the rare paths differently and the dots land on different pixels. At playback speed that reads as sparkle or flicker. Table 3 turns the documented causes into quick symptom checks, and it is a starting point for diagnosis, not a measured rule.
| Symptom | Likely cause | First check |
|---|---|---|
| Dots jump to new pixels every frame | Rare high-energy paths sampled differently per frame | Apply the source fixes, then clamp indirect light |
| Same hot spot in the same place across frames | Light or geometry placement | Move the light, check falloff and the Smooth factor |
| Fireflies only on glass or water | Caustics | Turn off Reflective and Refractive caustics |
| Fireflies only in sky-lit scenes | Small bright spots in the environment map | Enable World Multiple Importance and test another map |
If the sequence still flickers after the dots are gone, the cause may be elsewhere. The render noise and flicker pillar guide covers the wider set of noise, flicker and quality problems in animation renders.
Mistakes that hide fireflies badly
- Clamping to a very low value to rescue a whole sequence, which removes highlights and flattens the lighting.
- Turning off caustics in a shot where glass or water is the subject.
- Cutting bounces until glass looks dull, because glass needs more bounces to look right.
- Adding samples instead of finding the cause, which raises render time without fixing the spike.
- Judging a fix on the full frame, where a small change is easy to miss.
When render cost enters the decision
Fireflies cost money on a render farm because the usual workaround, more samples, multiplies the cost per frame. Fix them on one test frame locally and then submit the sequence. If a scene still needs heavy sampling after these fixes, compare services on cost per frame, for example through the top 5 render farms for Blender in 2026. A Blender Cycles fireflies fix belongs before that comparison, not after it.
FAQ: blender cycles fireflies fix
What are fireflies in Blender Cycles?
Fireflies are isolated pixels that render much brighter than the pixels around them. The Blender manual explains them as the result of light paths that are unlikely to be found but carry a lot of light. A pixel that catches such a path gets a very high value, while its neighbours never find it. They show up as white or colored dots that more samples reduce slowly.
Why do fireflies stay after I increase the samples?
Each pixel is an average of its samples, and one very bright sample can outweigh many ordinary ones. Extra samples dilute it, but slowly, so the dots become rarer rather than gone. When doubling the samples barely helps, the cause is usually in the scene or the light path settings, such as caustics, a light placed very close to a surface, or a small bright spot in an environment map.
Should I use clamping to remove fireflies?
Clamping works, but treat it as the last step. The manual says it reduces noise at the cost of accuracy and can dim bright lights and reflections you want to keep. Start with Clamp Indirect Light, because indirect bounces tend to produce more fireflies, and leave direct clamping alone unless you need it. Setting a value to 0 disables clamping, which is a quick way to compare before and after.
Does the denoiser remove fireflies?
Not reliably. A denoiser works from neighbouring pixels, so a very bright isolated pixel can be kept as detail or spread into its surroundings, depending on the denoiser and the frame. The safer order is to remove the cause or clamp first, then denoise. Always compare a crop with and without denoising, because the result differs between scenes and denoiser types.
How do I find which object or light causes the fireflies?
Render a small region of one frame where the fireflies are obvious, then change one thing at a time. Hide a light, disable caustics, lower the bounces, or swap the environment map, and render the same region again. The setting that removes the dots points to the cause. Keeping the region small makes each test fast, and changing only one variable avoids false conclusions.
Why do fireflies flicker in an animation?
Fireflies depend on which rare light paths each frame happens to sample. Different frames catch them in different pixels, so the dots appear to jump around, which reads as flicker. Fixing the source is better than raising samples, because a brighter dot in a new place every frame is still visible at playback speed. The flicker pillar page covers the wider set of causes.
Will a render farm fix my fireflies?
No. A render farm runs your scene with your settings, usually faster, so fireflies appear in the same way. Because the common workaround of adding samples raises the cost per frame, it is cheaper to fix the cause on one test frame before submitting the sequence. If the scene still needs heavy sampling afterwards, then compare farms on cost per frame.
Sources
- Blender Manual: Reducing Noise (Cycles): fireflies, caustics, Filter Glossy, light falloff, bounces, World Multiple Importance and Clamp Fireflies.
- Blender Manual: Light Paths (Cycles): Max Bounces, Clamping, Filter Glossy and Caustics settings.

COMMENTS