Blender Cycles Caustics and Subsurface Scattering (2026): Shadow Caustics, Random Walk and Render Time
For glass and water, Cycles has shadow caustics (MNEE, added in Blender 3.2): enable Shadow Caustics on the light, Cast Shadow Caustics on the refractive object and Receive Shadow Caustics on the surface, and Cycles renders sharp refractive caustics inside shadows only. For skin, wax and marble, Blender 5.0 made Random Walk subsurface scattering multi-bounce, which reduces dark artifacts at some render-time cost.
- Caustics: light + caster + receiver must all be enabled.
- Limits: refractive only, smooth normals on the caster.
- SSS: 5.0 Random Walk is multi-bounce.
- Cost: test the heaviest close-up on the target GPUs.
Caustics and subsurface scattering are two of the slowest effects to converge in a path tracer, and both are common in product, food and character work. Cycles offers targeted tools for each.
This guide covers shadow caustics and their limits, the Light Paths caustics settings, what changed for Random Walk SSS in Blender 5.0, and how to budget render time for shots that use them.
Checked against the Blender 3.2 and 5.0 Cycles release notes, the Cycles MNEE commit and the Blender Manual (Object Settings, Light Paths, Subsurface Scattering), November 2026.
1. Shadow caustics with MNEE
Blender 3.2 added shadow caustics based on manifold next event estimation (MNEE) (Blender 3.2: Cycles). The developer commit explains the idea: enable caustics selectively on a few objects where they have a big visual impact, without slowing the rest of the scene. The Shadow Caustics option must be enabled on the light, the receiver and the caster, and on those light paths Filter Glossy is ignored in favour of sharp caustics (Cycles MNEE commit).
2. Limits worth knowing
MNEE only produces caustics in the shadows of refractive objects, not reflective ones. The Manual lists further limits: caustic rays can pass through only a limited number of caster surfaces, caster objects need smooth normals, the Ambient Occlusion node does not give a valid result on casters or receivers, and volumes are not considered (Blender Manual: Object Settings). If a shot needs reflective caustics or caustics outside shadows, enable the general caustics options in Light Paths and expect more samples.
Only the first case is what shadow caustics are built for. The other three need either a change to the model, such as smooth shading on the caster, or the general caustics settings described next. The table sums up the settings and their cost.
Caustics and SSS settings and their cost
Where each setting lives and what it changes.
| Setting | Where | Effect |
|---|---|---|
| Shadow Caustics | Light, and Object › Shading › Caustics | Approximate refractive caustics in shadows via MNEE; only where enabled |
| Filter Glossy | Render › Light Paths › Caustics | Blurs glossy bounces to reduce noise; ignored on MNEE paths |
| Reflective / Refractive Caustics | Render › Light Paths › Caustics | Turn general caustic paths on or off for the whole scene |
| Random Walk SSS | Principled BSDF or Subsurface Scattering node | Multi-bounce in Blender 5.0: fewer dark artifacts, some extra render time |
| SSS Radius and Scale | Material | Larger scattering distances generally take longer to converge |
3. Light Paths: general caustics
Render › Light Paths › Caustics has Filter Glossy, which blurs glossy reflections after blurry bounces to reduce noise, and toggles for Reflective and Refractive caustics (Blender Manual: Light Paths). Turning caustics off removes much of the noise in glass-heavy scenes; turn them on only for the shots where viewers will notice them.
Both paths start on a diffuse surface and reach the light only through a sharp glass or mirror bounce, which random sampling rarely finds. That is why caustics are noisy, and why switching off the type a shot does not need removes much of the noise.
For the same problem in Redshift for Cinema 4D, including sparkles on the glass itself, see Redshift caustics: how to stop flickering in animations.
4. Random Walk SSS in Blender 5.0
The Blender 5.0 release notes describe a more accurate random walk subsurface scattering with multiple bounces, reducing darkening artifacts at the cost of some render time (Blender 5.0: Cycles). Existing scenes using Random Walk pick this up when opened in 5.0, so re-check render time on character close-ups after upgrading, and keep every frame of a shot on the same Blender version. SSS parameters are described on the Subsurface Scattering manual page.
Both effects add samples rather than memory, so they scale well across GPUs; split frames as in multi-GPU rendering in Cycles and denoise consistently, see denoising Cycles animation.
Light that enters skin or wax leaves at a different point, which gives the soft, glowing look; tracing that walk is also where the extra render time goes.
A caustics and SSS checklist
- Caustics: Shadow Caustics on the light, caster and receiver only where needed
- Caster: smooth normals; no AO node on casters or receivers
- Light Paths: general caustics off unless the shot needs them
- SSS: close-up re-checked after moving to Blender 5.0
- Version: same Blender version for every frame of the shot
- Test: heaviest close-up rendered on the target GPUs
For paths, caches and other scene checks, see our 10-point Blender Cycles pre-flight checklist.
Both farm models render caustics and SSS. On an IaaS server you can try caustics on and off and compare SSS close-ups on the GPUs that will render the sequence, then pick the settings before the full run.
Rendering caustics and SSS 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 the heaviest close-up, compare caustics and SSS settings.
- Render the sequence one Blender per GPU, then shut down; multi-GPU servers are billed per minute.
Frequently asked questions
1. How do I render caustics in Blender Cycles?
For refractive caustics in shadows, enable Shadow Caustics on the light, Cast Shadow Caustics on the glass and Receive Shadow Caustics on the surface. For other caustics, enable Reflective or Refractive caustics in Light Paths.
2. Why are my shadow caustics not showing?
All three settings (light, caster, receiver) must be enabled, the caster must be refractive with smooth normals, and the caustic must fall in a shadow.
3. Does MNEE work with reflective objects?
No. Cycles shadow caustics handle caustics in shadows of refractive objects only.
4. What changed for subsurface scattering in Blender 5.0?
Random Walk SSS became multi-bounce, which reduces darkening artifacts at the cost of some render time.
5. Do caustics and SSS use more GPU memory?
Mainly they need more samples and time; memory is driven more by geometry and textures.
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.




