On November 11, 2025, XGRIDS moved its Lixel CyberColor (LCC) file format into the open, publishing a white paper and developer SDKs and positioning the container as a common backbone for Gaussian splat workflows across game engines and the web. The organization’s new GitHub repository, LCCWhitepaper, documents the format’s structure, spanning meta.lcc metadata, tiled Index.bin, packed Data.bin, optional Shcoef.bin for 3rd-order spherical harmonics, Environment.bin, and a chunk-aligned Collision.lci BVH, for progressive, LOD-aware streaming at city-scale.
The technical brief is explicit about why a purpose-built container matters: the format couples spatial chunking with native LOD so viewers can load what’s needed when it’s needed—reducing memory pressure while preserving visual fidelity. LCC’s rotation, scale, and SH blocks are tightly encoded for GPU-side decode, keeping CPU parsing minimal and enabling asynchronous fetch of splat tiles during navigation. That’s a practical blueprint for real-time visualization, editing, and collision-aware interaction on large scenes.
Crucially, XGRIDS is shipping code around it. The company has published SDKs for Unity, Unreal, and the web, with the Web SDK explicitly supporting Three.js and Cesium, ray-casting, SH toggling, and environment data streams.
The “why now” is interoperability. XGRIDS has been vocal about the container’s practical wins, smaller payloads than vanilla PLY and a design that travels cleanly between viewers. Its product pages claim up to ~90% smaller files when exported to .lcc, with is in line with SOTA benchmarks. Given the average XGRIDS capture is much larger scale, having an efficient representation is critical.
And the ecosystem has already begun to meet LCC in the middle. PlayCanvas’ splat-transform CLI added LCC read support the past week, while SuperSplat introduced import for .lcc packages earlier this fall, signals that open documentation can catalyze cross-tool flow rather than lock in. Additionally, we have recently seen support added in both Nucleus and Arrival Space for the file format.
Today’s open sourcing also arrives with a community facing message. In XGRIDS’ announcement on social channels, the company frames LCC as a contribution to the broader 3DGS stack, promising leaner files, LOD streaming, and cross-platform compatibility, rather than a walled garden tied to its scanners alone. If Gaussian splats are to become a substrate for spatial computing, a transparent, well-documented interchange layer is table stakes.
With the spec now public and SDKs live, we’ll be tracking uptake across engine plugins and web viewers, how quickly third party capture apps emit .lcc, and whether open LCC nudges more editors and converters to treat splat datasets the way glTF did meshes. For now, the canonical sources are live.
