Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
Splat Viewer: photoreal Gaussian-splat avatars in the browser
The Splat Viewer renders Gaussian-splat and radiance-field scenes right in your browser, the photoreal output of capture engines like GaussianAvatars and HumanGaussian. Load a .ply (plain or compressed), .spz, .splat, .ksplat, or .sog by URL, drop a file in, or try a built-in sample, and orbit a photoreal avatar or scene with no plugin, no upload to a server, and no account. All decoding happens client-side.
Page: /splat
Why it exists
Mesh avatars (GLB) are lightweight, riggable, and universal, and that is what most of three.ws generates. But the photoreal frontier of avatar capture is radiance fields: Gaussian splatting reconstructs a person or a scene as millions of tiny anisotropic blobs that render with real skin, hair, and lighting no polygon budget can match. Those captures ship as .ply, .spz, .splat, .ksplat, or .sog files, and most tools to view them are desktop apps. The compressed containers matter: the same scene that is a 1 GB PLY is roughly 100 MB as SPZ and roughly 42 MB as SOG, which is the difference between a scene you can share as a link and one you cannot. The Splat Viewer is the browser front door: a place to open any splat scene, evaluate a capture engine's output, and share a photoreal avatar with a link. It complements /avatar-engines, which surveys the capture methods; the viewer is where their output actually renders.
How it works
The viewer (src/splat-viewer.js) is entirely client-side. Rendering lives in src/splat-stage.js, a shared module on top of Spark (@sparkjsdev/spark, MIT, by World Labs), lazy-loaded on first render so the page shell paints instantly. The Forge Studio Lab's splat tools render through the same module, so both surfaces read the same formats and behave the same way.
Spark renders splats as ordinary objects inside a normal three.js scene rather than inside a viewer of its own, which is what makes the rest of this page's behaviour possible:
- The format is read from the bytes, not the filename. A URL that ends in a query string, a redirect, or no extension at all still decodes. Only two containers fall back to the name:
.splatis a raw 32-byte-per-splat array with no header to sniff, and a bundled.sogis a zip. - The camera frames the scene it actually loaded, from the splat centres in world space. Splat scenes are authored at wildly different scales, and a fixed camera distance is right for exactly one of them.
- The live state waits for the first sorted frame. Spark sorts splats on a worker and paints once that lands, so the stage holds a "Sorting splats" state rather than going live over an empty canvas on a slow GPU.
- The canvas is opaque. Spark accumulates colour with premultiplied alpha and leaves destination alpha at zero, so a transparent canvas would composite a fully rendered scene away to nothing.
Every state is designed: idle, fetching, decoding, sorting, error, and a live HUD showing the scene label and its real splat count.
There are three ways to load a scene:
- By URL. Paste a link and the viewer fetches the bytes and decodes them. To survive cross-origin blocks, it rewrites the human-facing URLs of common asset hosts to their CORS-enabled raw form: GitHub
raw/bloblinks becomeraw.githubusercontent.com, Hugging Face/blob/becomes/resolve/, and Dropbox links are forced to a direct download. When a host still blocks the browser fetch, the error state tells you to download the file and upload it instead. Because the bytes are already in memory once a remote scene renders, the download control offers them back, so a scene you reached by URL is as saveable as one you uploaded. - By file. Pick a file or drag and drop a
.ply/.spz/.splat/.ksplat/.sogonto the stage. The file is read locally and never leaves your machine; a download button is offered for the loaded buffer. - Samples. Two procedurally generated scenes ship in the page: a radiance shell (6,000 splats) and a synthetic head-and-shoulders bust (14,000 splats) that evokes what a real GaussianAvatars capture looks like in the viewer. These are synthetic, generated in-browser, and downloadable.
A deep link, ?src=<url>&name=<label>, loads a scene straight from the URL on page load, so a photoreal avatar is shareable with a single link. A recenter control resets the camera on the live viewer, so it snaps back without dropping and rebuilding the WebGL context. Teardown is explicit: the renderer's graphics context is released by hand on every scene swap and when the page is hidden, because the splat library's own dispose stops short of that. If the browser drops the context anyway, after a GPU reset or under memory pressure, the stage reports it and offers a reload rather than freezing on the last frame.
Walkthrough
- Open /splat.
- Try a sample first: click the radiance shell or the head bust to see the viewer in action.
- Load your own scene: paste a
.ply/.spz/.splat/.ksplat/.sogURL and click Render, or drop a file onto the stage, or pick one from disk. - Orbit, zoom, and pan with the built-in controls. The HUD shows the scene label and splat count.
- Recenter if the camera drifts. Download the loaded buffer, whether the scene came from a file, a sample, or a URL.
- Share a scene by appending
?src=<url>to the page URL.
Examples
The viewer is driven by the URL, so sharing and embedding is just a link.
# Open a scene directly by deep link.
https://three.ws/splat?src=https://huggingface.co/<user>/<repo>/resolve/main/avatar.ply&name=My%20Avatar
# A GitHub-hosted splat: the viewer rewrites blob/raw links to the CORS raw host automatically.
https://three.ws/splat?src=https://github.com/<user>/<repo>/blob/main/scene.splat
Supported inputs at a glance:
.ply: Gaussian-splat point cloud in PLY format, plain or in PlayCanvas's compressed variant..spz: Niantic's compressed container, about a tenth the size of the equivalent PLY. The broadest delivery format in the ecosystem..sog: PlayCanvas Spatially Ordered Gaussians, roughly 15 to 20 times smaller than the PLY. What SuperSplat exports..splat: the antimatter15 layout (32 bytes per splat)..ksplat: the compressed KSplat format for faster loads.
Large scenes, hotspots and video
- Level of detail: once a scene clears 50,000 splats the viewer builds a Spark 2.3 LoD tree from the decoded buffer in Spark's worker pool, so distant regions render coarser. No network or paging is involved (Spark's
pagedmode streams chunked remote sources and has no path for an in-memory buffer). - Hotspots: save up to 25 named camera views from the current orbit position, jump to any of them, and see them as markers on the stage.
- Camera timeline: play the saved views in order as a smooth camera path.
- Video export: record the playing path in the browser with
MediaRecorderand download it. Nothing is uploaded.
States and limits
- Idle: prompts you to load a splat, drop a file, or try a sample.
- Fetching / decoding: shows the host and the buffer size in MB; large radiance fields take a moment to decode.
- Error: an invalid file reports "that file isn't a valid splat"; a blocked fetch explains the CORS limit and suggests downloading then uploading; the retry loads a sample so the stage is never dead.
- CORS: only hosts that send permissive cross-origin headers load by URL; the viewer auto-rewrites GitHub, Hugging Face, and Dropbox links, but other hosts may require a local upload.
- Client-side only: files you upload are decoded in the browser and never sent to a server. Generation is a separate step:
POST /api/forge-splat(TripoSplat) turns one image into a splat and returns aviewer_urlthat opens here via?src=. - Rendering runs on WebGL; very large scenes are bounded by your device's GPU and memory.
Related
- /avatar-engines surveys the photoreal capture engines (GaussianAvatars, HumanGaussian and peers) whose output this viewer renders.
- Avatar creation and avatar pipeline cover the mesh (GLB) avatar path.
- Scene Capture reconstructs point clouds from video, a related radiance-adjacent capture flow.
- Pages: /create, /scene.