Splat Tools

Gaussian Splatting File Formats Explained

A plain guide to Gaussian splatting file formats, including how format choices affect editing, hosting, performance, and publishing.

By Real Horizons TeamPublished June 3, 2026Updated June 3, 2026
Gaussian splatting file formats3DGS file formatPLY splat fileSPZ gaussian splatSOG gaussian splat
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 how format choices affect editing, 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.

Real Horizons supports the full Spatial Studio workflow: cloud Gaussian splat generation from smartphone video, 360 cameras, 360 drones, standard drone footage, DSLR/photo sets, and mixed media, followed by review, optimization, guided tour authoring, embeds, CTAs, and analytics.

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.
  • Keep source and published versions separate.
  • Document the format used for each client project.

Where this fits in a Real Horizons workflow

Use the capture source that fits the job. Real Horizons can generate the splat from that source, help you review and optimize the scene, and turn it into a tour the audience can open without extra explanation.

For a property, that may mean named room stops, finish hotspots, an inquiry CTA, and a link the agent can send. For a hotel, venue, campus, museum, or construction site, it may mean guided zones, access notes, booking context, or stakeholder comments.

The capture is the input. The generated splat is the spatial asset. The published tour is the deliverable clients and visitors actually use.

Why Real Horizons is different

Real Horizons covers more than hosting a finished splat. Spatial Studio includes cloud Gaussian splat generation for captures from smartphones, 360 cameras, 360 drones, standard drones, DSLR/photo sets, and mixed media workflows. That matters when a team wants one path from raw footage to a usable spatial tour instead of stitching together separate tools for capture processing, viewer setup, publishing, and client delivery.

The value is the combined workflow: generate the splat, review the scene, set the opening view, add guided stops or hotspots, publish the browser link, and measure whether visitors actually use it. For teams comparing Scaniverse, Splatica, Polycam, Matterport-style scans, or standalone viewers, the practical comparison is generation quality, input flexibility, clear pricing, and how much work remains before the result becomes a client-ready tour.

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 published tour in a normal browser, move through the first three important views, and check whether the file, hosting, and viewer choices stay invisible to the visitor. If the tool decision creates extra explanation for the client, simplify the workflow before you scale it.

Related reading

Frequently asked questions

Can this workflow support client work?

Yes, when the workflow is matched to a real visitor need. It should produce a tour, link, embed, or sales asset that someone outside the production team can use.

What should I check before using this on a paid project?

Check capture quality, mobile load behavior, first view, labels, hotspots, and the CTA path. A quick internal test helps prevent a poor paid-project handoff.

Where does Spatial Studio fit?

Spatial Studio brings cloud splat generation and tour authoring into one workflow: upload source media, generate a Gaussian splat, review the scene, add guided context, publish a browser link, and track visitor actions.

Does every project need a Gaussian splat?

No. Photos, 360 panoramas, and video can still be the right answer. Use splats when spatial movement and depth help the visitor make a better decision.

How should I measure the result?

Track tour opens, source campaigns, waypoint use, hotspot clicks, CTA clicks, and follow-up quality. Those signals matter more than the file format alone.

Next step

Pick one real space, capture it carefully, generate the splat in Real Horizons, publish it as a guided tour, and judge the result by whether a visitor understands the place and takes the next step.

Next step

Open the related workflow.

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