Path-Traced Gaussian Splatting in Octane 2026: A Production Workflow on iRender

Most Gaussian splat viewers treat each splat as a rasterized billboard. Octane 2026 takes a different approach by rendering Gaussian splats as native primitives through full path tracing. They can contribute to lighting, appear in reflections and refractions, and cast or receive shadows.

“In Octane, Gaussian splats become part of the ray-traced scene rather than just a camera-facing image.”

This article looks at what makes Octane’s implementation different and what to prepare before rendering a scene with Gaussian splats. The goal is a practical Octane Gaussian Splatting path traced workflow that fits real production work.

In most splat viewers, the captured appearance is displayed through rasterization. Octane 2026.1 introduced a different model, treating Gaussian splats as native renderable primitives with full path-traced GPU rendering. This allows them to respond to scene lighting and participate in effects such as reflections, refractions, and shadows.

That difference becomes especially useful when combining a scan with regular CG geometry. In Octane, splats can be relit and interact with global illumination, ray-traced shadows, reflections, and refractions. They can also cast and receive shadows, while clipping materials let standard scene objects cut into or intersect the splat data. This makes the asset much easier to integrate into a cinematic shot instead of treating it as a separate background element. For an Octane Gaussian Splatting path traced workflow, that interaction with the rest of the scene is one of the most important advantages.

Octane can load Gaussian Splatting data from .PLY and .SPZ files. These are widely used formats that can be generated from image captures with tools such as NeRF Studio and Polycam, giving artists a straightforward way to bring captured environments or objects into an Octane scene.

Once the splat is imported, I pay close attention to its Spherical Harmonics settings. Octane supports SH up to degree 3, and lowering the displayed SH level can reduce the amount of view-dependent detail while making the data lighter to process. Keeping degree 3 preserves more of the captured appearance, which is useful when reflections and lighting need to remain convincing as the camera moves. Octane 2026.4 also added fixes for .PLY files containing degree-4 SH data, although degree 4 remains outside the supported SH range. The same release reduced GPU memory usage for Gaussian splats and fixed a CUDA error affecting scenes with more than 30 million splat primitives.

Octane’s Gaussian splats already support relighting, shadows, clipping materials, trace sets, depth of field, and other path-traced effects. However, some production limitations have changed across the 2026 releases, so version matters when planning a shot.

• • • • Octane 2026.1: The initial implementation had several limitations. Gaussian splats were always rendered on top of volumes, they could not receive shadows from regular scene geometry, and render layers were not fully supported. Network rendering was also not supported for Gaussian splats at that stage, which was especially important for anyone planning to send a project to a render farm.
      • Octane 2026.2: This release fixed several splat-specific problems, including light leaking through splats, wireframe-pass hangs, incorrect splat-info AOVs with depth of field, and cases where splats could become invisible. It also introduced a compatibility mode for scenes created with 2026.1.
      • Octane 2026.4: Splat support moved forward with SPZ v4, lower GPU memory usage, and a fix for a CUDA error affecting scenes with more than 30 million splat primitives. The release also extended Neural Radiance Cache to macOS and added NRC support for network rendering.

Gaussian splats can become surprisingly demanding once the dataset grows. The number of splat primitives has a direct impact on how much GPU memory the scene needs, and path tracing adds more work because the splats participate in lighting, reflections, refractions, and shadows. Small or moderate datasets can be manageable, but scenes containing tens of millions of splats can quickly become a serious VRAM problem. For production work, I would treat GPU memory as a first-class requirement rather than choosing the GPU only by render speed. An RTX 5090 or RTX 4090 gives you a strong starting point for large Octane scenes, especially when the project also contains conventional geometry, textures, and other GPU-heavy assets. Octane 2026.4 reduced GPU memory usage for splats and fixed a CUDA issue affecting scenes above 30 million primitives, but large datasets can still push the hardware hard.

More GPUs do not automatically mean that all their VRAM becomes one large shared pool for every scene.

For an Octane Gaussian Splatting path traced workflow, I would prioritize a GPU with enough VRAM on a single device. A card with 32GB of VRAM can be more useful for a memory-heavy splat scene than simply adding another card and assuming the available memory will combine in the way you need. The actual behavior also depends on how Octane distributes the workload, so test the target scene on the intended hardware before committing to a long render.

• • • • Prepare the splat data: Check the .PLY or .SPZ file before opening the final scene, and make sure the data loads correctly.
      • Check the NVIDIA driver: Octane 2026.1 raised the minimum driver to R555, while GeForce RTX 50-series GPUs require R572. This requirement remains listed in 2026.4, so verify the driver before starting, especially on an RTX 5090.
      • Build a small test scene: Confirm that the splat displays correctly, interacts with lights, and behaves as expected with your CG geometry.
      • Render one test frame: Check VRAM usage, shadows, reflections, AOVs, and camera effects before launching the full sequence. For an Octane Gaussian Splatting path traced workflow, this small test can save a lot of time later.

VRAM and driver compatibility are two of the main reasons a rented GPU workstation can make sense for large splat scenes. More VRAM gives you more room for dense datasets, while having control over the workstation lets you configure the driver and software environment required by your GPU. This matters particularly with RTX 50-series cards, which have their own minimum driver requirement in Octane 2026.

iRender provides GPU workstations with options including RTX 5090 and RTX 4090, along with remote desktop access and administrator-level control of the machine environment. That setup lets you configure the workstation, install the software you need, and work with the scene much like you would on a local machine.

This workflow is closely tied to two practical requirements: VRAM and driver control. Gaussian splat scenes can become very heavy as the splat count increases, so an RTX 5090 with 32GB of GDDR7 gives more memory headroom than a 24GB card. More GPUs do not simply combine their VRAM into one larger pool. Driver control matters too. Octane 2026 requires R572 or newer for RTX 50-series GPUs, and iRender lets you install the required Octane version and driver, then save the configured environment as an image for later sessions.

There is also an important version difference to keep in mind. Gaussian Splatting first arrived officially in Octane 2026.1 with several early limitations, including no network rendering support for Gaussian Splats. Later releases improved the system, and Octane 2026.4 added network rendering support for splat workflows. If you are still working with an older version, a high-VRAM machine with the correct environment becomes especially useful. When renting a machine, remember that your Octane license is separate from the hardware rental. You provide and activate your own license, while rental time starts when the machine boots, not when rendering begins.

Right now, iRender is launching the 100% bonus for new user’s first deposit, check it out.

Check out some of iRender Octane tests on RTX 4090:

Q: How does Octane render Gaussian splats differently from a viewer?

Most Gaussian splat viewers rasterize the data as camera-facing billboards. Octane 2026 treats splats as native primitives and path traces them within the scene. As a result, they can interact with lighting, appear in reflections and refractions, cast and receive shadows, and respond to scene relighting, making them much easier to integrate with conventional CG geometry.

Q: What file formats does Octane accept for Gaussian splats?

Octane supports Gaussian splat data in .PLY and .SPZ formats, which can be generated from image captures using various splat-generation tools. Octane 2026.4 added SPZ v4 support. It supports Spherical Harmonics up to degree 3, so files containing higher-order SH data should be checked before production use.

Q: How much VRAM do Gaussian splat scenes need in Octane?

VRAM requirements depend heavily on the number of splats and the rest of the scene. Octane 2026.4 reduced GPU memory usage for splats and fixed a CUDA issue affecting scenes with more than 30 million splats. Test your actual scene before rendering, and remember that VRAM does not simply add together across multiple GPUs.

Register an account on iRender to claim your 100% bonus for the first deposit and render without limitations.

iRender – Maximum Speed – Absolute Freedom.