Get Splat Count

Get Splat Count is the smallest node in this family, and it knows it. You feed it a SPLAT, and it gives you back the same SPLAT unchanged plus an INT with the total number of gaussians in it, summed across the batch. It even prints the count right on the node face, so you can see "134,217 splats" at a glance without hunting through logs.

That's genuinely useful information in the current ecosystem. TripoSplat, the main image-to-splat model that shipped alongside ComfyUI's native splat support in mid-2026, generates a variable number of gaussians - up to 262,144 depending on your settings. So "how many splats is this?" is not a question with a fixed answer. Knowing the number tells you a few things at once:

• Whether your decode is as dense as you wanted, or whether you should push for a higher gaussian count.
• How much a downstream Merge Splats or Extract Mesh step is going to cost. Splat-to-mesh time scales badly with density, and the count is the early warning.
• Whether a merge actually did anything. Merging two 50k splats should read ~100k; if it doesn't, your inputs were emptier than you thought.

How to use it

There's exactly one input and the only real decision is where to drop it, because its pass-through design means you can insert it into an existing chain without changing anything downstream. Two placements that earn their keep:

• Right after the decode - know what you generated before you do anything expensive.
• After Merge Splats - confirm the merge grew the splat the way you expected.

Wire the count output into a primitive or string node if you want it in a filename, or just read it off the node.

It ships with ComfyUI core - part of the gaussian splat node family that landed together in late May 2026. Nothing to install, no model files, no configuration.

Common issues

Honestly, this node doesn't have many failure modes - it's a pass-through with a counter. The one thing to keep in mind: the count is summed across the batch, so if your splat is a batch of several items, the number is the total, not per-item. That's usually what you want, but don't be confused when a batched splat reports a bigger number than a single decode's limit.

A splat with zero gaussians reports zero, which is worth knowing because it means upstream generation silently failed before you wasted time on a render or mesh of nothing.