Placement in the Ecosystem: glTF from the Khronos Group is a lightweight asset format for realtime engines, viewers, and DCC export, commonly used between tools rather than inside them, and now it wants splats too. Visit their site here.
A careful step into splat territory
The Khronos Group has published a release candidate for a new glTF extension that adds support for Gaussian splatting. The proposal, named KHR_gaussian_splatting, defines how 3D Gaussian splats can be represented inside glTF 2.0 assets using a common, vendor-neutral schema.
Gaussian splatting is a scene representation technique where geometry is described as large numbers of oriented 3D Gaussians rather than polygon meshes. Each splat typically carries position, scale, rotation, colour and opacity. Rendering relies on blending these splats in screen space to approximate surfaces and volumetric detail. The approach is increasingly used in photogrammetry-derived captures and radiance field research, particularly where dense detail and rapid rendering are required.
Until now, Gaussian splats have circulated in a growing number of ad hoc file formats. Khronos is explicitly positioning this extension to prevent early fragmentation by defining a baseline encoding before incompatible variants become entrenched.
What the extension actually defines
KHR_gaussian_splatting introduces a standardised way to store splat data in glTF without redefining the rendering algorithm. The extension specifies how splats are described as primitives and which attributes are required or optional. These include spatial transforms and per-splat appearance data, mapped onto existing glTF data structures where possible.
The proposal does not mandate a specific splatting technique or optimisation strategy. Khronos describes the design as algorithm-agnostic, with the goal of supporting multiple implementations rather than locking vendors into a single approach. This restraint is notable given how quickly splat rendering methods are evolving.
Viewers that do not support the extension are expected to fall back gracefully, typically treating the data as a point cloud. This preserves basic visibility rather than failing outright, which aligns with glTF’s long-standing emphasis on predictable degradation.
Why Khronos is getting involved now
Gaussian splatting has moved from research into production-adjacent tools at a speed that has made standardisation awkward but necessary. Khronos frames this release candidate as a response to real usage rather than speculative future demand. The organisation is inviting feedback from developers and vendors before final ratification, signalling that the format is still open to adjustment.
The work builds on earlier collaboration between Khronos and geospatial and platform vendors exploring splat-based representations for large-scale scenes. While those efforts are not detailed in the extension itself, the context suggests a desire to make splats a first-class citizen alongside meshes, animations and textures in glTF.
glTF is often described by Khronos as a transmission format rather than a working format. Adding splats does not change that positioning, but it does acknowledge that realtime pipelines are absorbing data types that were previously confined to research or proprietary viewers.
Interoperability over novelty
There are no promises of faster rendering, smaller files, or better fidelity. Instead, the emphasis is on interoperability and predictability. This is a conservative but welcome stance for a standard that already underpins web viewers, game engines and real-time visualisation tools.
Compression is not part of the core proposal. Khronos notes that companion extensions may be introduced to improve storage efficiency, but they are not part of the current release candidate. No compression scheme is ratified as part of KHR_gaussian_splatting yet.
This separation is sensible. It allows the base representation to stabilise before additional complexity is layered on top, and avoids repeating past mistakes where format and codec decisions were entangled too early.
A positive but cautious signal
As proposed, KHR_gaussian_splatting does not attempt to redefine how Gaussian splats are generated or rendered. It simply gives them a place to live in a widely adopted container format. That restraint is arguably its strongest feature.
For production teams experimenting with splat-based capture or visualisation, a common interchange format reduces risk. For tool developers, it provides a reference target rather than another reverse-engineered file. For Khronos, it reinforces glTF’s role as a neutral meeting point rather than a battleground of features. As always, new formats and extensions should be tested thoroughly before being relied on in production environments.
// Khronos Group press release on glTF Gaussian Splatting
// https://www.khronos.org/news/press/gltf-gaussian-splatting-press-release
