Does Splat Count Matter? Why More Gaussians ≠ Better Quality
Guide · 2026-06-11 · 7 min read · by SplatMart Team
It's the first spec everyone looks at, but a 60M-splat scene isn't automatically better than a 5M one. Here's what splat count actually controls, where quality really comes from, and how to pick the right count for web, VR, and offline work.
Splat count, the number of 3D gaussians in a scene, is the first spec everyone looks at, and the most misunderstood. The short answer: more gaussians does not mean better quality. Count is a capacity and performance budget; quality comes from the capture and training behind it. Here's how to actually read this number.
What splat count actually controls
Each gaussian is a tiny coloured blob; millions of them together form the scene. More gaussians give the training process more capacity for fine detail, but capacity only converts into detail if the source images support it. One drone-mapping team's 70-million-splat city scene needed around 8,000 input photos at 5K resolution to fill that capacity. The same 70M budget trained from 300 phone photos would just be a heavier, blurrier file.
Where quality really comes from
- Input images: count, resolution, sharpness and coverage. This is the single biggest factor, practitioners routinely capture hundreds of photos for a single object.
- Training: iterations and settings matter; under-trained scenes look soft no matter the count.
- Cleanup: removing floaters and cropping bounds. A cleaned 3M-splat scene reads as higher quality than a raw 10M one.
In the r/GaussianSplatting community, where drone mappers regularly push past 50M splats, the consensus is blunt: "more splats does not always equal better quality," and for most scenes tens of millions is simply overkill.
Splat count is a performance budget
Every gaussian costs file size, loading time, and GPU work at render time. That's why the right question isn't "how many splats can I get?" but "how many can my target platform afford?"
- Web and mobile embeds: aim under ~2M splats in a compressed format (.sog/.spz). A typical product splat compresses from ~16MB to ~4MB with SOG, and load time is what users actually feel.
- Quest 3 / standalone VR: roughly 1–3M splats compressed runs comfortably in WebXR viewers.
- Desktop apps and offline renders: 20M+ is fine; streamed level-of-detail systems handle the truly huge scenes.
How to judge a splat before you buy it
- Use the interactive preview, zoom into edges and fine detail; your eyes beat any spec.
- Check capture details: input photo count, camera, capture tool. Strong inputs are the real quality signal.
- Look for 'cleaned' or 'floaters removed' in the description.
- Match the splat count and compressed file size to your platform budget, not to a bigger-is-better instinct.
Every SplatMart listing shows splat count, file size per format and capture tool for exactly this reason, so you can budget instead of guess.
Frequently asked questions
Is a higher splat count better quality?
Not by itself. Splat count is capacity, it only becomes detail if the input photos and training support it. A clean, well-captured 3M-splat scene beats a noisy 20M one. Treat count as a performance budget for your target platform.
How many splats do I need for VR on Quest 3?
Roughly 1–3 million splats in a compressed format (.spz/.sog) runs well in standalone WebXR viewers. PC-tethered VR can push much higher.
How many splats for a web page embed?
Stay under about 2M splats and use SOG or SPZ compression to keep the file in the low megabytes, visitors feel load time more than they see extra detail.
Why is my splat file so large?
Raw .ply files store every gaussian uncompressed, so size scales directly with count, often hundreds of MB. Convert to .sog or .spz for a 10–20x reduction with minimal visible loss.
Does splat count affect frame rate?
Yes, directly, rendering cost scales with the number of visible gaussians. If a scene stutters, use a lower-count version or a viewer with level-of-detail streaming.