June 14, 2025 Lynn Nguyen

How to Fix Grainy Renders in Blender (Cycles and EEVEE)

Executive SummaryGrainy Blender renders at a glance
Blender 4.x and 5.x

Grain in Cycles is Monte Carlo noise: each pixel is an average of random light paths, and the average settles slowly. You remove it with the sampling settings, a denoiser, and by making the light easier to find.

  • Overall grain: lower Noise Threshold (default 0.01) and raise Max Samples if the threshold is not reached
  • Leftover noise: turn on Denoise with Albedo and Normal passes; OpenImageDenoise works on any hardware, OptiX on NVIDIA RTX
  • White specks: clamp Indirect Light, raise Filter Glossy, add a Portal to window openings
  • EEVEE: grainy soft shadows and effects usually mean too few Render samples

You press F12 and the image is covered in grain, or a few bright specks sit on walls and glass. It looks like a bad GPU, but grain is how a path tracer works: Cycles traces random light paths for every pixel and averages them, and the average is noisy until enough paths have been traced. The fix is to give each pixel enough samples, clean the rest with a denoiser, and stop the few paths that carry huge values.

This guide goes through the settings in the order to change them, explains fireflies and grainy shadows, and ends with a checklist.

Checked against the Blender Manual (Cycles and EEVEE, 4.4–5.0), November 2026.

1. Why Cycles renders look grainy

Each Cycles sample follows one random path of light from the camera into the scene. A pixel’s value is the average of its samples, so with few samples the random paths do not agree yet and neighbouring pixels land at different values. That spread is the grain.

The spread shrinks only with the square root of the sample count, a property of every Monte Carlo estimate. Four times the samples halve the noise, which is why going from 1,024 to 4,096 samples costs a lot of time for a visible but modest gain. Scenes where light is hard to find, such as interiors lit through a window, light bouncing off glossy surfaces, or small bright lights, need many more samples for the same result.

iRender
Why more samples clean a Cycles render so slowly
Schematic
Same pixel area, more samples: noise falls as 1 / √samples16 samplesnoise ×164 samplesnoise ×0.5256 samplesnoise ×0.251024 samplesnoise ×0.1254096 samplesnoise ×0.063166425610244096relative noisesamples per pixel (log scale)4× the samples = half the noiseand roughly 4× the render timeEach step to the right costs four times the samples but only halves the grain, which is why denoising and fixing the light matterMonte Carlo error falls with 1/√N (PBRT, Monte Carlo Integration); patches are generated noise at those levels, not Blender renders
Relative noise (1/√samples)Sample counts shown above
Noise patches generated from the formula

How to read the figure. The five squares are the same patch of a flat grey surface rendered with more and more samples. Each step to the right uses four times as many samples and the grain halves, as the curve below shows: it drops fast at first and then flattens. When a render is still grainy at a few thousand samples, adding more is the slowest fix; denoising and making light easier to reach (sections 2 and 3) help far more.

2. Fix grain in Cycles, step by step

Change one setting at a time and render the same frame, so you can see which change helped. The badges in the figure match the steps.

  1. Noise Threshold (Render Properties › Sampling › Render): this is adaptive sampling. Cycles keeps sampling a pixel until its noise is below the threshold, then stops. The default is 0.01; lower it, for example to 0.005, for a cleaner image. Lower values take longer.
  2. Max Samples: the cap per pixel. If dark or difficult areas stay grainy, they are hitting this cap before the threshold; raise it. Min Samples and Time Limit can stay at 0.
  3. Denoise (Sampling › Denoise): turn it on for final renders. Choose OpenImageDenoise (any hardware) or OptiX (NVIDIA RTX), keep Passes at Albedo and Normal, and set Prefilter to Accurate for the best detail.
  4. Clamp Indirect Light (Light Paths › Clamping): if white specks remain, lower it step by step. It caps the brightness of each bounced sample.
  5. Filter Glossy (Light Paths › Caustics): raising it blurs sharp glossy reflections a little and removes many noisy caustic paths.
  6. Portal (an Area light with Portal enabled): for interiors lit by the sky through windows, place a Portal light in each opening, facing in. Cycles then sends more samples through the window.
iRender
The Cycles settings that control grain, in the order to change them
Schematic
Render Properties › Sampling (Cycles)RenderNoise Threshold0.01 → lower1Max Samples40962Min Samples0Time Limit0Denoiseon for final renders3DenoiserOpenImageDenoisePassesAlbedo and NormalPrefilterAccurateOptiX denoiser is an option on NVIDIA RTX GPUsRender Properties › Light PathsClampingDirect Light0 (off)Indirect Light10 → lower4CausticsFilter Glossy1.00 → raise5Reflective / RefractiveArea light › Light propertiesShapeRectanglePortal6place the light in the window opening, facing inOrder: 1 and 2 for overall grain → 3 to clean what is left → 4 and 5 only if white specks (fireflies) remain → 6 for interiors lit through windowsChange one setting at a time and render the same frame, so you can see which change helpedOrange outline = the value to change; badge = step number in the textLayout reconstructed from the Blender Manual (Cycles Sampling, Light Paths, Light Settings); defaults shown are Blender 4.x and 5.x
Value to changeOption turned on
Simplified mockup; not every control is shown

How to read the figure. The left panel holds the three settings that decide overall grain: badge 1 Noise Threshold, badge 2 Max Samples and badge 3 Denoise with its options. The right column holds the fixes for specks and difficult light: badge 4 clamps bright bounced samples, badge 5 filters glossy caustics, badge 6 turns an Area light into a Portal. Work through them in badge order; if the image is clean after badge 3, leave the rest at their defaults, because clamping and filtering also change the look slightly.

3. Fireflies: the bright specks that samples do not fix

Fireflies are single pixels much brighter than their neighbours. They come from rare light paths that carry a very large value, for example light that bounces off a glossy floor, through a small gap and onto a wall. Such a path is found only once in a while, so when it is found it dominates the pixel average. More samples make fireflies rarer but slow to disappear, and a denoiser can smear them into blotches.

iRender
How clamping removes a firefly
Schematic
One pixel, 32 samples: a single bright indirect sample makes a firefly010203040Clamp Indirect Light = 10one sample = 38Pixel value = mean of the sampleswithout the bright sample: 0.91with it, no clamp: 2.07 (firefly)with it, clamped at 10: 1.19sample number (1–32) → sample valueClamping caps each sample, so one lucky light path can no longer turn a pixel white; too low a clamp also darkens real highlightsValues computed in this figure; clamp behaviour from the Blender Manual (Cycles Light Paths, Clamping)
Normal sampleOutlier sampleClamp value
Example values, not a Blender measurement

How to read the figure. Each bar is one sample of the same pixel. Thirty-one samples sit around 1, and one indirect sample came back at 38. Because the pixel is the mean of all samples, that single bar more than doubles the pixel value, which shows as a white speck. The dashed green line is a clamp of 10 on indirect light: the tall bar is cut to the green box, and the pixel drops back close to its neighbours. The cost is a small loss of energy in genuinely bright bounces, so lower the clamp only as far as the specks need.

Besides clamping and Filter Glossy:

  • Make small bright sources bigger. A larger, less intense light or emissive surface is found more often by random paths and produces less noise than a tiny, very bright one.
  • Use Portals for windows so sky light is sampled through the openings.
  • Turn off caustics you do not need with the Reflective and Refractive Caustics options in Light Paths.
  • Path Guiding (Sampling › Path Guiding) learns where light comes from during the render and reduces noise in difficult indirect lighting. It runs on the CPU only, so it applies when the Device is CPU.

4. Grainy shadows, and grain in EEVEE

Cycles: soft shadows from large lights are themselves sampled, so they are often the grainiest part of the image. The fixes are the same: a lower Noise Threshold, more Max Samples, and denoising. Shadows from a very small, very bright light are sharp and clean; it is the large soft ones that need samples.

EEVEE: EEVEE builds soft shadows, depth of field and ray-traced effects by accumulating several samples per pixel. If shadows or reflections look grainy in the final render, raise the Render sample count in Render Properties › Sampling; the Viewport value only affects the viewport. EEVEE does not have Cycles’ adaptive Noise Threshold, so the sample count is the main control.

5. When denoising makes things worse

A denoiser can only work with what the samples give it. With very few samples it guesses, and you see blotches, smeared textures or flat surfaces that should have detail. Keep the Albedo and Normal passes on so it can tell texture from noise, give it a reasonable number of samples first, and use Prefilter Accurate. In animation, frames denoised one by one can shimmer; our guide to denoising Cycles animations covers that case.

Grainy render checklist

Tick each item before you render the full sequence.

ChecklistGrainy render checklist
0 / 7 done
Tip: tick each item as you set up the job; the ticks reset when the page reloads.

SaaS or IaaS render farm for a grainy scene?

Sampling, clamping, denoiser and portal settings are saved in the .blend, so a grainy frame at home is equally grainy on every farm; a farm only renders it faster. What differs is how you tune it. Finding the right Noise Threshold and clamp for a heavy scene usually takes a few test renders of the same frame.

CompareNeutral guide

Tuning noise on a render farm

How the two farm models fit a scene that still needs noise tuning.

Your situationSaaS render farmIaaS render farm (iRender)
Settings already tuned at home; you only need the framesA good fit: upload and the farm renders the range across its nodesWorks as well: open the file and render the range
The scene is too slow at home to test sample settingsEach test is a submitted job; you see the result when it comes backRender test frames on the server and change settings in Blender between them
You rely on add-ons or a specific Blender buildCheck that the farm supports themInstall your own version and add-ons once; they stay in your server image
Rule of thumb: if the frame is already clean at home, a SaaS farm is the shorter path; if you still need to tune samples and clamps on a heavy scene, renting the whole machine lets you test as you would at home.

A noise-test workflow on an iRender server

iRender
How iRender works: your computer controls your own multi-GPU server
IaaS render farm
Your PC or MacNo powerful GPU neededRemote desktopLive screen1:1 like your PCYOUR OWN GPU SERVERbare-metal · not sharedGPUGPUGPUGPUGPUGPUGPUGPU1, 2, 4 or 8 × RTX 5090 (32 GB) or RTX 4090 (24 GB)Threadripper PRO · 256 GB ECC RAM · 2 TB NVMe SSDFull admin access · your setup is saved between sessions1Register, top upFirst $50+ top-up doubled2Upload your projectiRender Drive, free3Start and connectRemote desktop, any OS4Render, shut downBilling stops, per minute✓ Your workstation, just more GPUs: no queue to wait, no farm plugin, no job submission, no settings changed
Your mouse and keyboardServer screen streamed back
Schematic, not to scale

How to read the figure. The top row is the setup: your own PC or Mac connects by remote desktop to a whole bare-metal server with 1, 2, 4 or 8 GPUs, so you open the .blend in Blender there exactly as at home. The numbered row is the order of a session: register and top up, upload to iRender Drive before the server runs, start and connect, then render test frames and the job, and shut down so billing stops.

  1. Upload first. Put the project in iRender Drive before you start a server; transfer and storage are free and no rental time runs while you upload.
  2. Start a server. Cycles uses every GPU, so a 2x, 4x or 8x RTX 4090 (24 GB) or RTX 5090 (32 GB) server shortens each test frame. Multi-GPU servers bill per minute; 1-GPU servers have a one-hour minimum.
  3. Install Blender. Blender is not pre-installed: download your version from blender.org (the portable .zip runs without installing). It stays in your server image.
  4. Tune on one frame. Render the hardest frame, change one setting, render again, and compare at 100% zoom.
  5. Render the range, download the frames and shut the server down so billing stops.

Frequently asked questions

1. Why does my Blender render look grainy?

Cycles averages random light paths for each pixel, and with too few samples the average is still noisy. Lower the Noise Threshold, raise Max Samples, and turn on Denoise for the final render.

2. What does Noise Threshold do in Blender?

It turns on adaptive sampling: Cycles stops sampling a pixel once its noise falls below the threshold. The default is 0.01; a lower value gives a cleaner image and a longer render.

3. Why are my shadows grainy in Blender?

Soft shadows from large lights are sampled, so they need more samples than the rest of the image. In Cycles lower the Noise Threshold and denoise; in EEVEE raise the Render sample count.

4. How do I get rid of fireflies in Blender?

Lower Clamp Indirect Light in Light Paths, raise Filter Glossy, turn off caustics you do not need, add Portal lights to window openings, and make tiny bright lights larger and less intense.

5. Which denoiser should I use in Blender?

OpenImageDenoise works on any hardware and gives clean final frames. OptiX runs on NVIDIA RTX GPUs. Keep the Albedo and Normal passes on either way.

6. Does EEVEE render grainy?

EEVEE has no Cycles-style path tracing noise, but soft shadows, depth of field and ray-traced effects are built from several samples. If they look grainy, raise the Render samples in Render Properties.

7. Will a render farm fix a grainy render?

No. The sampling and denoising settings are in the .blend, so the frame looks the same on any farm. A farm with more GPUs only makes it faster to render more samples and test settings.

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.

Accelerate your production pipeline with high-performance IaaS render farm services and dedicated bare-metal workstations powered by up to 8x NVIDIA GeForce RTX 5090 (32GB GDDR7), high-frequency AMD Ryzen™ Threadripper™ PRO processors, 256GB ECC RAM, and dedicated 2TB NVMe SSD storage tailored for your pipeline:
, , , , , , , , , , , , , , , , , , , , ,

Lynn Nguyen

Lynn Nguyen has written more than 80 articles for the iRender blog in English and Korean, covering Blender, Maya and Unreal Engine workflows for artists rendering on iRender servers.
Contact

iRENDER GPU

Render Farm Pricing
Quick Start
Multi-GPU Benchmarks
iRender GPU App
Blog
Documentation
The Render Farm
The Company
Terms & Conditions

INTEGRATIONS

Autodesk Maya
Blender
Cinema 4D
Houdini
Karma XPU
Lumion
KeyShot
Unreal Engine
Twinmotion
Redshift
Octane
And many more…

iRENDER TEAM

Elite support 7 days a week
SATURDAY – SUNDAY: 6:00 AM – 11:59 PM
(UTC+7)
Hotline: (+84) 912-785-500
Skype: iRender Support
Email: [email protected]
Address 1: 68 Circular Road #02-01, 049422, Singapore.
Address 2: No.22 Thanh Cong Street, Hanoi, Vietnam.

Contact
이 페이지는 한국어로도 제공됩니다. 한국어로 보기 →