Blender Cycles Volumes and OpenVDB (2026): Null Scattering in Blender 5, VDB Sequences and Memory
Blender 5.0 made an unbiased null scattering algorithm the default for Cycles volumes, so smoke and fire can look and time differently than in 4.x; the old ray marching is still available as Render › Volume › Biased. For VDB files, keep sequences inside the project, check grid names, and use the volume object’s Precision and Clipping to control memory.
- Blender 5: null scattering by default; Biased restores step size and max steps.
- VDB files: Volume object › OpenVDB File with Sequence; grid names must match the shader.
- Memory: Precision Half or Variable and Clipping reduce memory.
- Motion blur: set the Velocity Grid on the volume object.
Volumes are where Cycles scenes most often change between versions and machines. Blender 5.0 replaced the default volume algorithm, VDB sequences depend on file paths, and a single dense grid can fill a GPU on its own.
This guide covers what changed in Blender 5, how to load and render OpenVDB files, the settings that control volume memory, and the problems that most often break volume renders on another machine. For Houdini volumes rendered elsewhere, see missing VDBs on a Blender render farm.
Checked against the Blender 5.0 Cycles release notes and the Blender Manual (Volume Properties, Light Paths), November 2026.
1. What changed for volumes in Blender 5.0
The Blender 5.0 release notes state that a new volume rendering algorithm based on null scattering was added as the default (Blender 5.0: Cycles). Performance and noise can differ from before and depend on the scene. If a volume renders slower and looks different, the notes explain, it is usually because the old step rate was too large and the result was biased. Simple scenes and heavily tuned volume shaders may be faster with biased rendering, while unbiased removes manual tuning and handles mixed dense and thin volumes better.
The previous ray marching algorithm is still there: enable Render › Volume › Biased, which also restores the step size and max steps options. Pick one per project and keep it for every shot, so frames rendered on different machines match.
2. Loading OpenVDB files
Volume objects read OpenVDB files from other software such as Houdini or from Blender’s own fluid cache; you can add one from the Add menu or drag a .vdb into Blender (Blender 2.83 release notes: Volume Object). In Volume Properties, Sequence loads one VDB per frame; the files need a numerical suffix, like an image sequence, and Frames, Start, Offset and Mode control how the sequence maps to scene frames (Blender Manual: Volume Properties).
By default the Principled Volume shader reads grids named density, color and temperature; if your file uses other names, choose them in the shader nodes. A volume that renders empty on another machine is usually a path or grid-name problem rather than a GPU one.
Two links have to hold for a VDB to render: each file in the sequence must map to the right scene frame, and each grid in the file must reach a shader input or the velocity setting. When either link breaks on another machine, the volume renders empty or static.
3. Volume memory: precision and clipping
The volume object has Cycles-only render settings that control memory. Clipping sets the value under which voxels are treated as empty space. Precision chooses Full (32-bit), Half (16-bit) or Variable, which uses less precision in less noticeable areas; the Manual notes that lower values reduce memory at the cost of detail. Every GPU holds the whole volume, so these come before buying a bigger card. Our guide to Cycles GPU memory covers the rest of the scene.
4. Motion blur and light bounces
For motion blur, set Velocity Grid on the volume object: either one grid with 3D vectors or a prefix for three scalar grids ending in x, y and z, plus Velocity Unit (per frame or per second) and Velocity Scale. Volume light bounces are set under Render › Light Paths (Blender Manual: Light Paths); more bounces brighten thick clouds and smoke but cost render time.
Cycles uses the velocity stored in each voxel to smear the volume over the shutter time, so the blur follows the simulation rather than the object’s transform.
Common volume problems and a first fix
Symptoms artists report after moving to Blender 5 or to another machine.
| Symptom | Likely cause | First check |
|---|---|---|
| Smoke looks different or renders slower after upgrading to 5.0 | New default null scattering algorithm | Compare with Render › Volume › Biased on one frame; keep whichever look and time you need |
| Volume missing on the render machine | .vdb path absolute or files not uploaded | Keep .vdb files in the project, use relative paths, check the Sequence settings |
| Volume renders black or empty | Principled Volume reads grids named density, color, temperature; your file uses other names | Check the grid names in Volume Properties and set them in the shader |
| No motion blur on the volume | No velocity grid assigned | Set Velocity Grid, Velocity Unit and Velocity Scale on the volume object |
| GPU memory fills up | Large grids at full precision | Set Precision to Half or Variable and raise Clipping slightly |
A volume checklist before a long render
- Algorithm: unbiased (default) or Biased chosen once and kept for the whole project
- Files: .vdb sequence inside the project, relative path, Sequence frames and offset correct
- Grids: density, color, temperature or your grid names set in the shader
- Memory: Precision and Clipping set; peak memory checked on the heaviest frame
- Motion blur: Velocity Grid, Unit and Scale set if the shot has motion blur
- Test: one heavy frame rendered on the target machine before the sequence
For paths and caches in general, see our 10-point Blender Cycles pre-flight checklist.
Both farm models can render VDB volumes if the files arrive with the scene. On an IaaS server you can open the scene, confirm the sequence loads, compare biased and unbiased on the heaviest frame and watch memory before committing to the full sequence.
Rendering volumes on an iRender server
- Upload the project folder with its .vdb sequences 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 frame, check the volume, grids and memory.
- Render the sequence and shut down; multi-GPU servers are billed per minute.
Frequently asked questions
1. Why does my smoke look different in Blender 5?
Blender 5.0 made an unbiased null scattering algorithm the default. The release notes say that if a volume looks different and renders slower, the old step rate was usually too large and biased.
2. Can I get the old volume rendering back?
Yes. Enable Render › Volume › Biased, which restores ray marching with the step size and max steps options.
3. How do I render a VDB sequence in Blender?
Add a volume object, choose the first .vdb file and enable Sequence. Files need a numerical suffix, like an image sequence.
4. Why is my VDB volume empty when rendered?
Usually the file path is wrong on that machine or the grid names do not match the shader, which reads density, color and temperature by default.
5. How do I reduce volume memory in Cycles?
Set the volume object’s Precision to Half or Variable and raise Clipping so near-empty voxels count as empty space.
6. How do I get motion blur on a volume?
Set the Velocity Grid on the volume object, with Velocity Unit and Velocity Scale.
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.




