3DGS File Inspector — Analyze Any Gaussian Splatting File

No. The inspector runs entirely in your browser using JavaScript. Your file never leaves your device. Only the first 8 KB of the file header is read into memory for analysis — the full file is not loaded.

The inspector distinguishes 3DGS PLY files from standard mesh PLY files by checking for Gaussian-specific properties: spherical harmonics coefficients (f_dc_*, f_rest_*), rotation quaternions (rot_*), scales (scale_*), and opacity. If these properties are missing, the file is a triangulated mesh PLY, not a Gaussian Splatting file.

SPZ files are gzip-compressed, so the actual Gaussian count is stored inside the compressed data stream. Reading it would require decompressing the entire file. Instead, the inspector divides the file size by the typical compressed bytes per Gaussian (~24 for SPZ, ~28 for KSplat) to give a close estimate. For PLY and SPLAT files, the count is exact.

Compression potential shows how much smaller your file could become if converted to SPZ format. For example, a PLY file with SH degree 3 at ~236 bytes per Gaussian can be compressed to ~24 bytes per Gaussian in SPZ — roughly a 90% reduction. Files already in SPZ format show no compression potential since they are already compressed.

Yes. Because the inspector only reads the first 8 KB of the file header, it works with files of any size. The file is not loaded into memory — only a small slice is read for header analysis. This makes the inspector fast even for multi-gigabyte PLY files.

The GPU memory estimate assumes a standard WebGL/Vulkan rendering pipeline: 12 bytes for position (3 × float32), 4 bytes for RGBA color, 24 bytes for 3D covariance matrix (6 × float32), plus 4 bytes per SH coefficient. The actual memory usage depends on the viewer implementation and may be higher if additional buffers or textures are used.