Splat Tools

SOG vs PLY vs SPZ for Gaussian Splats

Compare SOG, PLY, and SPZ Gaussian splat formats by viewer support, compatibility, editing, compression, hosting, and browser tour use.

By Real Horizons TeamPublished June 3, 2026Updated July 16, 2026
SOG vs PLY vs SPZ Gaussian splatsGaussian splat file formatsPLY gaussian splatopen PLY fileSOG file viewerSPZ splat formatSPZ file viewercompressed gaussian splat
A Gaussian splatting software workflow with cameras, captured scenes, editing stages, and published tour outputs
Splat Tools

Compare SOG, PLY, and SPZ Gaussian splat formats by viewer support, compatibility, editing, compression, hosting, and browser tour use.

File format choices affect generation output, loading, compatibility, editing, and publishing, so judge them by the full delivery workflow.

Short answer

Format discussions are useful only when they connect back to web delivery and viewer support.

File format choices affect generation output, loading, compatibility, editing, and publishing, so judge them by the full delivery workflow. For a client project, pick a format your generation tool, editor, hosting layer, and browser tour can handle reliably.

Use the Spatial Studio Splat Viewer to open supported splat files in the browser before you decide which format belongs in the publishing workflow.

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

  • Record which format your generation tool exports.
  • Check which viewer or editor can open it.
  • Compare file size after compression.
  • Test the same scene in a browser viewer.
  • Test mobile load behavior.
  • Keep a fallback plan for client delivery.

Opening each format

FormatOpen it whenWatch for
PLY fileYou need a common export or interchange format.Some PLY files are meshes, not Gaussian splats.
SOG fileYou need a compact format for browser delivery.Test loading and image quality on mobile.
SPZ fileYou need another compact splat format for web workflows.Confirm your viewer and publishing stack open it.

The Spatial Studio Splat Viewer can open supported PLY, SOG, and SPZ files for a quick browser check before publishing.

How to compare SOG, PLY, and SPZ

Do not compare formats only by file extension. Compare the exact output from your toolchain: visual quality, load time, editor support, hosting requirements, and whether the browser viewer handles it without extra conversion.

PLY is common and useful for interchange. SOG and SPZ are often used for compact web delivery. The practical choice is the format that opens reliably, keeps the scene readable, and fits the publishing surface.

Where Spatial Studio fits

Spatial Studio can open supported splat files for review and publish finished scenes as guided tours. Use the viewer to check the raw file. Use tour publishing when the result needs a browser link, waypoints, labels, 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 creators, web 3D teams, and tour 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 city-scale map tour gives large sites the context that a room-by-room viewer cannot provide alone.

A city-scale map tour gives large sites the context that a room-by-room viewer cannot provide alone.

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 the same scene in the Spatial Studio Splat Viewer, then compare it against the published tour path on desktop and mobile.

Next step

Open the related workflow.

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