English

View Your Splats Offline

Gaussian splats fail when the network does. See how to publish a splat Story, cache it in the browser, install it as a PWA, and run the whole experience offline.

· João Rodrigues· 5 min read
  • Gaussian splats
  • offline
  • PWA
  • WebXR
  • Cyango
View Your Splats Offline

You spent hours on capture. Focus stacks, COLMAP, training, cleanup. The splat looks incredible on your laptop with fiber Wi-Fi.

Then you walk into a museum basement, a heritage site with one bar of signal, or a client meeting where the venue blocks guest Wi-Fi. You open the link. The loader spins. The splat never arrives. All that work collapses into an apology about connectivity.

Gaussian splats are heavy. That is part of why they look good. It is also why "just send a link" is not always enough.

Why offline matters for splat creators

Most splat conversations stop at capture quality. Fair. But distribution is where projects live or die.

A conservation team wants visitors to explore a scanned artifact in a gallery with spotty coverage. A real estate agent previews a splatted interior in a basement showroom. A field researcher demos macro captures at a conference where everyone hogs bandwidth. A tourism board hands tablets to guides who cannot rely on mountain LTE.

In each case, the splat is not a lab demo. It is a presentation tool. And presentations do not get second chances because the network failed.

Standalone splat viewers are getting better at web delivery. Fewer of them treat the full experience as something you can install, cache, and reopen without a connection. That gap matters when your splat is wrapped in story, labels, scene flow, and brand context, not floating alone in a minimal orbit viewer.

What "offline" actually means here

Offline does not mean emailing a 400 MB .ply and hoping someone has desktop software.

In Cyango, you publish your splat inside a Story: scenes, camera paths, hotspots, UI, audio, other media if you need them. Viewers open a normal browser link on phone, tablet, desktop, or headset. No app store required.

The first time they load it online, the experience caches locally. After that, they can install it as a Progressive Web App on supported devices and reopen it without a connection. The splat, scene data, and bundled assets stay available from local storage.

That is a different workflow from "download this file." It behaves more like installing a lightweight app from a link, except you built it visually in the editor instead of shipping a native build.

Where this beats a naked splat viewer

A splat file alone is an asset. Most real deployments need structure around it.

You might want a guided opening camera move before free exploration. Labels on fragile details. A second scene with context photos. A call to action at the end. Password protection for a client preview. A QR code on a placard that opens the same experience on any phone.

Cyango keeps that structure intact offline. You are not stripping interactivity to make caching work. You are caching the whole published Story, including converted splat assets (.PLY, .SPLAT, .SPZ, .KSPLAT processed for web delivery), alongside models, panoramas, video, and UI.

For teams already using splats in marketing captures, immersive exhibitions, or tourism previews, offline install closes the last mile between "beautiful capture" and "works on site."

Practical setup (viewer side)

The flow is intentionally boring, which is good.

  1. Publish your Story from xr/studio.
  2. Share the link, embed, or QR code as usual.
  3. Ask viewers to open it once while online and let assets finish loading.
  4. On supported phones and desktops, use the browser's install or "Add to Home Screen" option.
  5. Reopen from the home screen icon. The experience runs from cache.

For venue rollouts, load each device once on reliable Wi-Fi before the event. After that, guides can demo without asking anyone to hotspot.

Practical setup (creator side)

A few habits keep offline installs smooth.

Test on the target device. A splat that streams fine on your editing machine may feel different on an older tablet. Publish a test link early.

Keep scenes focused. Offline cache is generous, but discipline still helps. Split huge projects into separate Stories if you are handing them to low-storage devices.

Combine formats wisely. Splats shine for captured realism; meshes still win for precise product edges or heavy interaction. Mix both when the experience deserves it.

Use password protection for client previews. Offline does not mean public. Lock sensitive captures while still letting approved viewers install locally.

When offline is the wrong goal

Be honest about limits.

Offline Stories cache what was loaded. If you update the published project, installed copies may need a refresh to pick up changes. Live analytics, livestream scenes, and anything that depends on real-time server data will not behave the same without a connection.

If your only need is a quick share of a raw capture for a colleague on fast Wi-Fi, a lightweight viewer might be faster than building a full Story. If your need is a branded, interactive splat experience that must work in the field, offline install is the point.

The distribution layer splats still need

Gaussian Splatting moved fast on capture. Distribution is catching up.

The creators doing the most interesting work are not just producing better splats. They are packaging them: context, navigation, multilingual support, shareable links, and delivery that survives bad networks.

That is the layer between "cool scan" and "useful on site."

If you already have splats and want to test offline delivery with your own captures, create a free Cyango account, build a short Story in xr/studio, publish, install it on a phone, then turn on airplane mode and walk back in.

If the splat still orbits smoothly with no signal, you are done apologizing for the Wi-Fi.