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 August 2, 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.

Compare the exact files, not the acronyms

TestWhat to recordWhy
Visual parityThin edges, transparency, color, background, and artifacts after conversion.A smaller file is not useful if the scene visibly degrades.
Byte sizeRaw file and network transfer size.Extension alone does not tell you the delivered weight.
Tool supportGenerator, editor, viewer, host, and export path.One unsupported stage can force another conversion.
Load and memoryTime to first useful frame and stability on a normal phone.Web delivery fails when the target device cannot hold the scene.
Round tripWhether editing and re-export preserve needed properties.Some workflows are good for delivery but poor for interchange.

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 format mistakes

  • Assuming every .ply is a Gaussian splat rather than a mesh or point cloud.
  • Comparing extensions without recording the encoder, settings, and source scene.
  • Converting repeatedly and attributing accumulated loss to the final format.
  • Testing on a workstation while ignoring mobile memory and transfer time.
  • Deleting the original interchange file after creating a compact delivery copy.

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.

Load the same camera view from each file and capture a screenshot after the scene settles. Compare edges and distant detail at equal viewport size. Then repeat on mobile. A format that looks identical in a desktop editor may reveal slower startup or memory pressure in the delivery environment.

Keep a small test corpus rather than relying on one cafe. Include an interior with thin furniture, an outdoor scene with foliage, and a larger site. Store the source, conversion command or product version, settings, output size, and screenshots together.

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.

For a city or land tour, file format is only one performance lever. The surrounding map, images, and viewer code also affect loading. Measure the published page rather than crediting or blaming the splat container for the whole experience.

Spatial Studio can keep a delivery copy attached to the guided tour while the team retains the source export for future editing. The visitor should never need to know whether the asset is PLY, SOG, or SPZ.

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.