Splat Tools

Gaussian Splatting File Formats Explained

A plain guide to Gaussian splatting file formats, including PLY, SOG, SPZ, SPLAT, KSPLAT, viewer support, hosting, performance, and publishing.

By Real Horizons TeamPublished June 3, 2026Updated July 16, 2026
Gaussian splatting file formats3DGS file formatPLY splat fileopen PLY fileSPZ gaussian splatSOG gaussian splatSOG file viewerSPZ file viewer
A Gaussian splatting software workflow with cameras, captured scenes, editing stages, and published tour outputs
Splat Tools

A plain guide to Gaussian splatting file formats, including PLY, SOG, SPZ, SPLAT, KSPLAT, viewer support, hosting, performance, and publishing.

The right format is the one your generation, editing, hosting, and viewer stack can support without weakening the final tour.

Short answer

Format choice matters most when it affects load time, compatibility, and update workflow.

The right format is the one your generation, editing, hosting, and viewer stack can support without weakening the final tour. Pick the format that preserves enough visual quality, loads on the target devices, and still works with the publishing workflow.

To quickly check a .ply, .compressed.ply, .splat, .ksplat, .sog, or .spz, open it in the Spatial Studio Splat Viewer. Use a hosted lod-meta.json URL when you need to inspect a streaming LOD scene.

How to judge the workflow

AreaWhat to checkWhy it matters
Input and formatCheck what the tool opens, exports, and preserves.Compatibility affects the whole stack.
EditingClean, crop, inspect, and optimize before sharing.A messy scene weakens trust.
DeliveryShare as a browser tour with context and tracking.The client usually needs more than a raw viewer.

Practical checklist

  • Name the source tool and exported format.
  • Check editor support before committing.
  • Test compression on important scene areas.
  • Open the exported file in a browser viewer before sending it.
  • Keep source and published versions separate.
  • Document the format used for each client project.

How to open common splat files

File typeHow to open itWhat to check
.ply fileDrop it into the Splat Viewer.Confirm it is a Gaussian splat PLY, not only a mesh PLY.
.compressed.plyOpen it like a PLY file and compare against source.Look for compression damage in important details.
.sog fileDrop it into the viewer or paste a hosted URL.Check browser load time and mobile performance.
.spz fileDrop it into the viewer or paste a hosted URL.Check visual quality after compact delivery.
.splat or .ksplatOpen the local file or hosted file URL.Check camera controls, orientation, and whether cleanup is due.
lod-meta.jsonPaste a hosted metadata URL.Confirm chunk files are reachable from the metadata path.

How formats affect the workflow

Formats matter at four points: generation output, editing support, browser viewing, and final publishing. A file can look good in one tool and still fail later if the next viewer cannot open it, if the hosted paths break, or if the compressed version damages the areas people care about.

Keep the original export, the edited file, and the published version separate. That makes it easier to test a lighter web format without losing the source scene.

Where Spatial Studio fits

Spatial Studio can generate splats from flexible capture sources, open supported splat files in the browser, and publish finished scenes as guided tours. Use the viewer for a quick format check. Use the tour workflow when the scene needs waypoints, hotspots, embeds, CTAs, and analytics.

Common mistakes

  • Judging the result only inside a raw viewer.
  • Forgetting the first view, so visitors open into a confusing angle.
  • Adding too many labels instead of a clear route.
  • Sending a heavy scene without testing a normal phone.
  • Treating the same capture method as right for every project.

What the finished tour should prove

A published cafe tour gives visitors a clear first view before they move through the space.

A published cafe tour gives visitors a clear first view before they move through the space.

A viewer, editor, optimizer, or file-format choice should be judged by the tour it helps produce. The first published angle should load cleanly, show the subject clearly, and make the next action obvious. For technical operators, media teams, and web publishers, this is more useful than a feature checklist that never reaches a real visitor.

Use the public tour view as a quality gate. Check whether movement feels controlled, whether labels and stops are readable, and whether the scene still works after compression or hosting changes. If the tour only looks good in an editor but feels weak in the browser, the workflow is not ready for a client handoff.

A heritage tour needs guided views so visitors can understand the building, courtyard, and points of interest.

A heritage tour needs guided views so visitors can understand the building, courtyard, and points of interest.

The publishing step keeps tool choices tied to the visitor experience. File size, format, cleanup, and hosting decisions all affect what visitors see after they click the link. Keep the workflow simple enough to repeat: source capture, generated splat, cleaned scene, reviewed first view, published link, mobile check, and one clear next step.

Keep the handoff organized around the actual workflow: source file, cleaned scene, optimized model, published tour, and review link. For a broader look at the stack, compare Gaussian Splatting Software with Splat Virtual Tour Software.

Use a simple acceptance test before choosing the stack. Open the raw file in the Splat Viewer, then open the published tour in a normal browser. Move through the first three important views and check whether the format, hosting, and viewer choices stay invisible to the visitor.

Next step

Open one exported splat in the Spatial Studio Splat Viewer. If the format loads cleanly, test the published tour path next.

Next step

Open the related workflow.

Review live examples or move straight into the matching Spatial Studio flow.