What Builds the Scene? Luminance Dominates Geometry Formation in 3D Gaussian Splatting
Rezvan Joshaghani, Steven Cutchin
cs.CV, cs.GR
2026-10-01
Luminance alone nearly matches RGB for 3DGS geometry (0.085 dB gap); chroma-only geometry trails by 3.9-5.5 dB, and deleted chroma can be re-fit on frozen geometry.
Standard 3D Gaussian Splatting trains geometry and appearance against a single RGB loss, so the residual cannot tell you whether luminance or chroma drove the representation to form. A simple intervention exposes the ambiguity: supervise only the Y channel for the first half of training, release Cb/Cr later, and final quality lands close to ordinary RGB training. That fits two opposite stories. Either luminance already built the geometry and chroma just fills in color, or the late full-color phase repairs geometry that luminance left incomplete.
Prior work on monochromatic reconstruction plus colorization, fixed-geometry appearance recovery, and YUV-domain SH compression each hints at a luminance/chroma division of labor. None of it measures what chromatic supervision actually contributes while standard RGB 3DGS learns its geometry. This paper supplies that measurement.
The core move is separating what supervises training from how appearance gets fitted:
The shared solver is validated first: delete chroma from a trained model (which costs 3.1-16.5 dB by itself, 8.2 dB on average) and re-fit it on frozen geometry, and recovery reaches 1.017, where 1 matches the trained model. The solver is not the bottleneck. Confounds are bounded by controls: a YCbCr parameterization trained under the stock RGB loss differs by only -0.018 dB, ruling out the color basis itself; pruning to matched Gaussian counts moves the gap by at most 0.006 dB; and a densification-free comparison has both arms keep the identical set of Gaussians.
| Comparison | Metric | Result |
| Y-only vs RGB geometry, same A | held-out PSNR gap | -0.085 ± 0.037 dB; 8/11 scenes within ±0.15 dB |
| KITCHEN / DR. JOHNSON / PLAYROOM | same | RGB ahead by 0.2-0.3 dB |
| CbCr-only vs Y-only geometry | same | 3.9-5.5 dB worse (three scenes) |
| Same Gaussians, densification off | same | chroma still 1.4-2.5 dB worse |
| Remove SH degrees 1-3, luminance | held-out PSNR | -1.441 dB (MSE +35%) |
| Remove SH degrees 1-3, chroma | held-out PSNR | -0.187 dB (MSE +3.6%) |
| Re-fit deleted chroma on frozen geometry | recovery ratio | 0.300 (scene tint) → 1.017 (coupled degree-3) |
| Adversarial chroma, mismatched across views | same A PSNR | -0.15 to -0.67 dB, all four seeds separated |
Part of the chroma-only deficit is algorithmic. Chroma produces smaller positional gradients, so under the stock densification threshold it finishes with only 7.0-15.3% as many Gaussians as luminance training. Lowering the threshold to match the growth regime recovers only 36-43% of the gap. Stretching chroma contrast to luminance scale recovers at most 9% of what remains, leaving 2.1-3.1 dB. Mismatched chroma does hurt geometry, with complete separation across seeds, so chroma is not geometrically inert, but the effect is an order of magnitude smaller than removing luminance. Specular scenes mark the boundary: on the chrome ball, deleting higher-order chroma costs 0.61 dB against 5.7 dB for luminance, and measured chromaticity does shift with viewpoint. The verdict is luminance-dominated, not luminance-exclusive.
For anyone building 3DGS systems, this turns a vague intuition into a quantified division of labor. The authors flag three untested design directions: densification and other geometry-oriented operations could use luminance-weighted signals; chromatic appearance could be fitted or replaced after spatial support is established, giving monochrome-capture-plus-colorization pipelines a measured basis; and chromatic SH degree and precision could be compressed far more aggressively than luminance, which explains HiGS's 6-bit luminance / 4-bit chroma packing from the training-dynamics side.
To be clear about scale: the geometry-side gap is 0.085 dB. This is a measurement paper that clarifies a division of labor, not a performance improvement.
The authors list nine; the load-bearing ones:
One more from the numbers: the formal equivalence test at ±0.15 dB narrowly fails, with the 90% interval extending 0.001 dB past the band, and the authors kept the original band. Strictly speaking, "nearly the same" is doing real work in the headline.