WebGPU 3DGS Renderer

Gaussian Splats on the Web

A WebGPU Gaussian splat renderer I built and released publicly, plus the authoring editor and streaming viewer I built around it. Together they take real-world captures from raw files to a fast, photoreal experience in any browser.

At a Glance

  • Role: sole author of Radiance, built in my own time and released publicly. Built the editor and viewer at Rotor Studios, writing over 95% of the code.
  • Stack: WebGPU, WGSL compute shaders, WebGL fallback, Three.js, glTF/GLB
  • Formats: PLY, SOG, SPZ, .splat, GLB/glTF
  • Scale: millions of splats on desktop. Content typically targets around one million, with lighter versions for lower-end devices.

About The Project

Gaussian splatting turns photos or drone footage into a photoreal 3D capture of a real place. Engineers already use it for site surveys: fly a drone over a site, and soon after you have a navigable 3D record of it. The capture on this page is an aerial survey of a coastal site, shared by a coastal engineer whose team uses splats to survey sites for port and breakwater projects across the Pacific.

There are plenty of splat renderers for the web, and nearly all of them compromise somewhere. Either quality drifts from the reference, or sorting runs on the CPU, which caps how many splats a scene can hold and how fast it can update. Radiance is built to avoid that trade-off. It sorts on the GPU in WebGPU compute shaders and matches ground-truth renders almost pixel for pixel. The editor and viewer around it take content from raw capture to a fast, streamed experience in the browser.

Key Features

Reference-Accurate Rendering

Spherical harmonics from degree 0 to 3, matched almost pixel for pixel to ground-truth reference renders.

GPU Sorting at Scale

A per-frame compute-shader sort with frustum culling. Millions of splats render in real time on desktop.

Depth-Correct Mixed Scenes

Multiple splats interleave in one scene. Meshes depth-test against individual splats, and everything composites with Three.js.

Built for Delivery

Splat LODs are generated in about 30 seconds instead of hours of retraining, quality scales at runtime, and streaming starts from the manifest so the first pixel arrives fast.

Process & Technical Insights

Process & Technical Insights

With Gaussian splats, overdraw sets the performance limit more than splat count does. Most content therefore targets around a million splats, and lower-end devices get lighter versions automatically. On top of that, the viewer scales screen resolution, anti-aliasing and level of detail at runtime to hold frame rate. Browsers without WebGPU fall back to a Three.js WebGL renderer. Quality holds up there, but sorting moves to the CPU, so the splat budget is lower.

The editor came from need. Once Radiance was rendering well, managing assets became the bottleneck. I built the viewer as a separate library with a clean API, and made the editor its first client. That keeps a single code path, means anything authored in the editor behaves the same once embedded, and makes the viewer easy for other developers to drop into a page.

Publishing optimises for load time. Binary GLB files are split into glTF, so the viewer can read the manifest first, see every dependency and prioritise what the user sees first. The user gets something on screen quickly while the rest of the scene loads in the background.