1 big thing

SuperSplat rewrote itself on WebGPU and deleted the fallback

The SuperSplat 3.3.0 editor with a Gaussian splat capture of a street cafe loaded — furled yellow umbrellas over metal tables, parked cars and a tree-lined street behind. The scene manager and transform panels sit at the left, the tool strip along the bottom, and the status bar reads two million splats

Screenshot: SuperSplat 3.3.0 editor · Tools

PlayCanvas shipped SuperSplat 3.0 a week ago and has pushed six more releases since. It is a ground-up rewrite of both the renderer and the editor's data model on WebGPU, and the headline is not a feature but a subtraction: the editor no longer keeps the scene in JavaScript, and it no longer runs on WebGL2 at all.

Why it matters: SuperSplat is where a great many captures get cleaned up before they go anywhere, and its binding constraint has always been browser memory. A large PLY had to be parsed into JavaScript, held there as float arrays, and sorted on the CPU by a worker every time the camera moved. Scenes that were merely big became scenes that crashed the tab.

In 3.0 the splat data lives in chunked GPU storage, with only a small per-gaussian instance list — selection, locks, transform and colour indices — describing the editable state. Projection, frustum culling, compaction, depth sorting and draw submission all run on the GPU every frame, through a compute projector, a GPU radix sort and indirect draws. The CPU sort worker is gone.

Exports were the other memory cliff, and they are now streamed chunk by chunk through splat-transform, so saving a PLY, SOG, SPZ or project file no longer materialises the whole scene before writing it.

Two rows of photoacoustic reconstructions of a branching vascular phantom, shown for SlingBAG, for PAGS, and as the ground-truth digital phantom. The SlingBAG panels carry a mottled noise floor around the vessels; the PAGS panels are cleaner, with the vessel network closer to the crisp white tracery of the phantom

Splatting, but the light is sound and the camera is a transducer

Sep 1, 2026

A schematic of a scene divided into a wireframe grid of cells against black. One cell is outlined in yellow and holds a sharp green cylinder; a blurred blue slab sits behind it and a red slab in front, standing in for the frozen regions flattened into single background and foreground images

Their trick makes VRAM independent of scene size. The test scenes were too small to show it.

Aug 31, 2026

Six holographic reconstructions of laboratory equipment photographed against black through a HoloLens: a Bunsen burner and a rack of capped test tubes above, and below them a shredded, torn reconstruction of a mortar and pestle beside two further mortar-and-pestle models whose pestles are visibly deformed

PSNR said Gaussian splatting won. Seventeen people said it didn't.

Aug 29, 2026

A fairground drop-tower ride rendered twice: on the left from a degraded reconstruction, where the tower and foliage dissolve into white streaks and smears, and on the right after refinement, sharp and photographic against a clear sky

Give it scattered keypoints and it matches a full splat reconstruction

Aug 29, 2026

Amara Osei

Aug 28, 2026Tools

To put splats on the globe, he replaced the renderer

Key art for the plugin: a Gaussian-splat capture of a derelict stone barn with a corrugated roof, sitting on a white tile and surrounded by scattered blue and purple splat points, with the wireframe box of its tile bounds drawn around it

Two standards have been circling each other for most of a year. Khronos defined how a Gaussian splat lives inside a glTF file; the OGC's 3D Tiles defines how you stream a planet's worth of glTF to a browser. A plugin published this morning puts them together, and the interesting part is what its maintainer had to throw away to do it.

Why it matters: 3D Tiles is how large geospatial scenes actually get delivered — a spatial hierarchy of tiles, fetched on demand, disposed when they leave view. It is the format behind most serious terrain and city streaming on the web, and `3d-tiles-renderer`, maintained under NASA-AMMOS, is its three.js implementation.

Go deeper (3 min. read) ⟶

Theo Lindqvist

Aug 28, 2026Tools

Babylon.js gave splats a hard ceiling

The base of a Gaussian-splat capture of a pasta box shown twice. Above, the shadow beside it breaks into a hard blocky wedge, circled in red by the developer. Below, after the fix, the same shadow falls away as a smooth gradient

Babylon.js shipped 9.23.0 on Wednesday with four Gaussian splat changes, two of which are substantial. The first admits something the field has been quiet about: distance-based level of detail does not actually bound how much you draw. The second fixes a shadow bug with an unusually clean diagnosis — the randomness was in the wrong place.

Why it matters: Streamed splat scenes can render an unbounded number of primitives. On a workstation that is a feature. On a laptop it is dropped frames, and on a phone it is a coin toss, because the only lever available was to reduce detail with distance — which lowers the count without capping it.

Go deeper (4 min. read) ⟶

Wen Jiang

Aug 28, 2026Research

738 MB to 3.2 MB, without touching the training loop

The same view of a white bicycle leaning against a black bench on grass, rendered twice side by side — once from the uncompressed reconstruction and once from the compressed one — with no visible difference between them

The best 3D Gaussian splat compression systems have generally been the ones that reach into training and change how the scene is built, which makes them effective and almost impossible to take apart. A group at Fraunhofer HHI and Humboldt-Universität zu Berlin has published the opposite proposition: leave training alone entirely, take a finished vanilla 3DGS scene, and compress it afterwards in two independent stages.

Why it matters: Splat files are enormous, and the field's answer has been to fold size reduction into reconstruction — learned entropy models, anchor structures, quantisation-aware training. Those systems work, but they combine several strategies at once, which makes it hard to see where the gains actually come from and harder still to reuse a component in someone else's pipeline.

Go deeper (3 min. read) ⟶

Priya Raghunathan

Aug 28, 2026Research

A driving world model that only predicts the parts that move

Three pairs of suburban street scenes from a car's forward camera, each pair showing the ground-truth future frame beside 4DGS-WAM's prediction of it at a different horizon

World action models — the systems that predict what a scene will look like a few frames after an agent acts — almost all work in 2D video, which means redrawing every pixel of every frame, including the buildings that have not moved since the drive began. Yueen Ma and colleagues at the Chinese University of Hong Kong, Fudan, and the Shanghai Academy of AI for Science argue that this is a strange way to spend a prediction budget, and propose keeping the background.

Why it matters: A video world model treats the future as an image-generation problem. It has no explicit notion that the parked car on the left is an object, that the object has a pose, or that the terrace behind it was fully observed ninety frames ago and has not changed since. Every frame is regenerated from scratch, and the model spends most of its capacity reproducing content it already had.

Go deeper (4 min. read) ⟶

Wen Jiang

Aug 27, 2026Research

The water got murkier and the scores went up

A figure summarising the study: five systems and four water regimes across the top, a row of murky underwater renderings of a submerged structure, and beneath them two Gaussian point clouds of a sunken car — one coherent and car-shaped labelled 3DGS, one scattered and diffuse labelled SeaSplat, each captioned with its PSNR and chamfer error

Two underwater Gaussian splatting papers appeared on Monday, each declaring state of the art on an evaluation set it had assembled itself, neither citing the other. Olaya Álvarez-Tuñón and Stella Graßhof have now done the thing that was missing: taken five underwater splatting systems with public code, run them under a single protocol with shared poses, initialisation, compute budget and evaluator, and pushed them across four water regimes. The conclusion is that the architecture matters less than the setup, and that the numbers the field reports do not show it.

Why it matters: Underwater splatting has a benchmark culture problem that is easy to state and hard to see: the standard photometric metrics reward a model for fitting the water rather than the scene behind it. Haze is smooth, low-frequency and highly predictable, so a system that commits opacity to the veil scores well on held-out views while placing its geometry in the wrong place.

Go deeper (5 min. read) ⟶

Tessa Marchetti

Aug 26, 2026Industry

Arrival.Space gave away the browser version of what it sells

The Tanks and Temples Truck scene — a pale blue vintage flatbed pickup parked on a pavement — rendered sharply inside the Splat.js browser interface, with a readout showing 579,748 splats and a Train button in the toolbar

Arrival.Space sells hosted reconstruction: you upload video, their servers turn it into a splat, you get it back. A week ago the company published Splat.js under an MIT licence — a library that does the whole job in a browser tab, on the viewer's own GPU, without the photographs ever leaving the device. As of this afternoon it scores better on the standard benchmark than the 2024 papers it was presumably meant to be a toy beside.

Why it matters: The division of labour in splatting has been stable for two years: capture on a phone, solve and train on a server or a workstation with CUDA, view in a browser. The browser was the last mile, and everything upstream of it was somebody's compute bill.

Go deeper (4 min. read) ⟶

View all stories ⟶