Skip to main content

3DGS Quality Compare — Side-by-Side Viewer

Compare two Gaussian Splatting files with synchronized cameras. See exactly how compression or editing affects visual quality.

Last updated Mar 2026

Drop 2 files here to compare side by side

e.g. original PLY + compressed SPZ of the same scene

What You Should Know

How the Comparison Works

Drop two 3DGS files (e.g., the original PLY and a compressed SPZ version of the same scene). Both are rendered simultaneously in side-by-side viewports with synchronized cameras — when you orbit, zoom, or pan one viewer, the other follows in real time. This lets you visually inspect quality differences at any angle without switching between tabs or tools.

What to Compare

Common comparison scenarios: (1) Original PLY vs SPZ/SOG compressed — check if compression introduced visible artifacts. (2) Different training iterations — compare an early checkpoint vs final result. (3) Before/after editing — see the effect of floater removal or region cropping. (4) Format comparison — same scene in SPLAT vs SPZ to evaluate SH preservation. The tool shows file size difference automatically so you can weigh quality against compression ratio.

Supported Formats

Both files can be any combination of PLY, SPLAT, SPZ, KSplat, and SOG formats. They do not need to be the same format — comparing a PLY original against its SPZ compressed version is the most common use case. Each file is rendered independently by Spark.js with full spherical harmonics support.

Frequently Asked Questions
Technically no — you can load any two 3DGS files. But the synchronized camera only makes sense for comparing different versions of the same scene (e.g., original vs compressed). Comparing unrelated scenes will show synchronized camera movement but the content will differ.
Not yet. Currently the tool provides visual side-by-side comparison and file size difference. Pixel-level quality metrics (SSIM, PSNR) require rendering both scenes at the exact same resolution and comparing pixel values, which is planned for a future update.
Each file can be up to 500 MB. Since both files are loaded simultaneously, the total memory usage is roughly double — so keep each file under 250 MB for the smoothest experience on devices with limited RAM.
No. Both files are rendered locally in your browser using WebGL. Nothing is sent to any server.

Related Tools

Step-by-Step Guides