Guide · Embed

Embed a Gaussian Splat on a Website

Embed a ready public Gaussian splat with one responsive iframe. Copy the current splats.ai snippet, test it, and share the work safely.

Place an interactive Gaussian splat in a portfolio, project page, or client site with an iframe. The splats.ai detail page provides a public work route and a copyable embed snippet; you supply the page that will contain it.

This guide covers the current public-work path: select a ready work, replace the sample ID in the snippet, paste the iframe into your page, and test it in the place where visitors will see it.

Choose a public work

Start with the Explore gallery and open a work that is publicly available and ready. The embed route is intended for a work that viewers can access; do not use a private record or an unlisted link as the example for a public tutorial.

Choose any work that Explore currently shows as public and ready. Open its detail page and use the ID in that route. This guide uses <work-id> as a generic placeholder so readers can follow the steps with the work they choose; it does not require a featured or official sample. A curated example can be added later as an optional editorial enhancement after a public work has been selected and checked.

The work page is the source of truth for its title, creator, category, cover, and available details. A page author should not infer a file type, capture device, location, model size, or performance result that the work does not show.

Copy the iframe snippet

The current public detail page shows an Embed block with a Copy action. The snippet observed on 2026-09-18 UTC uses the /embed/<id> route, a 100% width, a 480px height, fullscreen and XR permissions, and a border reset with a 12px radius.

Replace <work-id> with the ID of the public work you opened in Explore before copying this template:

<iframe src="https://splats.ai/embed/<work-id>" width="100%" height="480" allow="fullscreen; xr-spatial-tracking" style="border:0;border-radius:12px"></iframe>

This is a template, not a live example URL. Replace <work-id> with the ID from the public work you chose in Explore. Do not publish a page whose iframe still contains the placeholder.

The exact snippet, route, dimensions, and permissions are volatile product details. Recheck them on the publication date against a current public detail page. If the live product changes the snippet, use the live version and update the dated sentence above.

Add the iframe to your page

Paste the completed snippet into the HTML or embed field for the page where the work should appear. The default template fills the available width and reserves 480px of height. A parent container can control the available width; if your CMS applies its own height or strips iframe markup, use the CMS's HTML/embed component and verify the rendered result.

Keep the source URL on the splats.ai origin unless you have deliberately chosen a different, verified route. The path should remain /embed/<id>, with the selected public work ID in place of <id>.

Use an honest caption or surrounding text when visitors need context. The iframe itself does not establish who made the work, whether the source was authorized, or whether the work will remain public. Link the surrounding page to the approved detail URL when attribution or project context matters.

Test the embed before sharing it

Run this short check on the actual page that will contain the iframe:

  1. Load the page in a clean browser tab.
  2. Confirm that the intended work appears, rather than a placeholder or a different ID.
  3. Drag to orbit and scroll to zoom inside the viewer.
  4. Try the page at the target desktop and mobile widths.
  5. Check that fullscreen behaves as expected in the target browser.
  6. Open the detail URL separately and confirm that the work is still public and ready.
  7. Check the page's attribution and surrounding copy before publishing it.

The interaction controls and device behavior checked on 2026-09-18 UTC were drag-to-orbit and scroll-to-zoom. Recheck those controls, loading behavior, fullscreen behavior, and target-browser support before publication. Do not promise a fixed load time, universal device support, a particular frame rate, or a reconstruction result.

Troubleshoot a blank or unavailable embed

The viewer is blank or never becomes ready. Confirm that the ID is correct and that the selected work is ready and public. Try the detail URL in a separate tab to distinguish a work-status problem from a host-page problem.

The wrong work appears. Compare the ID in the iframe src with the approved detail route. Keep the title and attribution around the iframe aligned with that same work.

The iframe is missing from the page.Some site builders sanitize iframe markup or require a dedicated HTML/embed block. Check the rendered page source and the builder's documented embed field.

The viewer is too tall or too short. Start with the 480px template, then adjust the height for the page layout and test it again at the target widths. Do not call a layout choice a product guarantee.

Fullscreen or XR behavior differs.Check the browser's permission handling and the current allow attribute from the live snippet. Do not add permissions that the product has not documented or that your host does not need.

If you need to create a work first

If you own a supported splat file or video but do not yet have a ready public work, use the Upload page after signing in with Google. Wait for processing or delivery to finish, review the detail page, and choose the intended visibility before you copy an iframe.

The currently documented input path, checked on 2026-09-18 UTC, accepts SOG for direct delivery, PLY/SPLAT/SPZ/KSPLAT for optimization to SOG, and supported MP4/MOV/WebM video for reconstruction into a viewable splat. Recheck those formats, processing behavior, Google sign-in requirement, duration limits, and file-size limits immediately before publication. This guide does not state a duration or size limit because those values are volatile and belong to the live upload surface.

New uploads remain unlisted until the author makes them public from the dashboard, subject to current product behavior. Do not treat an unlisted URL as confidential access, and do not publish an embed guide that implies private hosting or a security boundary.

When you are evaluating hosting options

If you are deciding whether a browser gallery and hosting workflow fits a project, read the current splat.host and splats.ai comparison. That page is a dated product comparison; this guide is only the implementation path for a ready public work. Neither page should be read as a promise of a feature, price, private embed, API entitlement, catalog size, or future release.

What this embed does not promise

An iframe can make a ready public work viewable inside another page. It does not promise:

  • that every source, scene, browser, mobile device, or host page will work;
  • a specific reconstruction time, visual quality, file size, latency, or frame rate;
  • private or confidential sharing, instant deletion from every cache or backup, or access control beyond the current public-work behavior;
  • paid-plan enrollment, private hosting, analytics, white-labeling, an API, storage quotas, or an SLA; or
  • that the work, route, embed snippet, or public catalog will remain available forever.

Use the live detail route, current embed block, upload page, and approved product policies as the source of truth.