How to Put Gaussian Splatting on a Product Page with SwiftXR

A product page does not need more media for the sake of it. It needs better proof.

Static images can show a product from selected angles. Video can show it in motion. But both still ask the buyer to accept the view the brand has chosen for them.

Gaussian Splatting changes that relationship. It can turn a real product capture into a photorealistic, interactive 3D experience that shoppers can explore from different angles in their browser. Materials feel less flattened. Surface details are easier to inspect. The product begins to carry more of its physical presence onto the screen.

But a Gaussian Splat sitting in a capture tool or on a hard drive is not yet a product experience. It only becomes useful when it is prepared for the web, published, placed correctly on the product page, and tested around the decision the buyer needs to make.

That is where SwiftXR comes in.

SwiftXR brings Gaussian Splatting into the same no-code environment used to create, publish, share, and embed interactive 3D experiences. Instead of building and maintaining a custom web renderer, a brand can move from a completed capture to a live experience on Shopify, Wix, WooCommerce, WordPress, or another website through a published SwiftXR project.

The short answer

To put Gaussian Splatting on a product page with SwiftXR:

Capture or create a clean Gaussian Splat of the product.

Remove unwanted background data and check the product's orientation.

Create a project in the SwiftXR Hub.

Add the Gaussian Splatting component in the SwiftXR editor.

Upload the supported splat asset and set its framing and presentation.

Publish the project.

Copy the embed code or connect the published project through SwiftXR's ecommerce plugin.

Place the viewer where it supports the buying decision, then test it across devices.

The embed may be the shortest step. The strategy around it is what determines whether the experience helps the page perform.

First, decide whether Gaussian Splatting is right for the product

Gaussian Splatting and traditional polygon-based 3D models solve different problems.

A conventional 3D mesh is built from defined geometry, materials, and textures. It is often the stronger choice when the experience depends on exact dimensions, clean configuration logic, colour or material switching, animation, or controlled real-scale placement.

A Gaussian Splat is reconstructed from images or video. Its advantage is captured appearance. It can preserve the visual character of a real object or space, including fine textures, complex surfaces, natural depth, and lighting information that may take longer to rebuild manually in a traditional 3D pipeline.

Use a Gaussian Splat when the buyer needs to appreciate:

• Material character and surface detail
• Craftsmanship and irregular forms
• The visual presence of a physical object
• A product within a captured environment or showroom
• A more photographic form of interactive 3D

Consider a mesh, or a hybrid experience, when the buyer needs:

• Exact geometric inspection
• Reliable real-world measurements
• Multiple configurable variants
• Parts, assembly, or animation
• A highly controlled AR placement workflow

This is not a contest between two formats. The strategic question is simpler: What does the buyer still need to understand before they feel confident enough to act?

Step 1: Capture the product with the final page in mind

The quality of the product-page experience begins before SwiftXR. It begins with the capture.

Keep the product completely still and use bright, even lighting. Move around it slowly and capture overlapping views from different heights and angles. Polycam's current capture guidance recommends roughly 60 to 80 percent overlap between images, while Scaniverse advises covering a subject from high and low, near and far, and from both direct and angled views.

For an individual product, aim to capture the complete object without collecting more of the room than the experience needs. Extra background data creates more cleanup work and can distract from the product after publishing.

Before processing, check for:

• Motion blur
• Missed angles or hidden surfaces
• Strong exposure changes
• Moving people or objects in the background
• Reflections that break apart between views
• Areas where the product blends into the background

Reflective, transparent, very thin, or repetitive surfaces deserve additional testing. Gaussian Splatting can represent complex appearance impressively, but the quality of the result still depends on capture coverage, lighting, and reconstruction.

Step 2: Clean and prepare the Gaussian Splat

A raw capture often includes floaters, unwanted floor or wall data, soft edges, or excess space around the subject. Clean these before the asset reaches the product page.

Your preparation checklist should include:

• Crop the capture tightly enough to keep attention on the product.
• Remove obvious reconstruction artefacts and floating points.
• Check the upright orientation of the object.
• Set a useful starting angle.
• Confirm that important details remain clear when viewed at product-page size.
• Balance visual fidelity against download weight and mobile performance.

Export the asset in a Gaussian Splat format supported by the current SwiftXR uploader. Because splat formats and web pipelines are evolving quickly, use the format listed in the live uploader rather than renaming or converting a file blindly.

Step 3: Create the experience in SwiftXR

Open the SwiftXR Hub and create a new project. Give the project a clear name that connects it to the correct product, variant, and revision. This becomes important when several published experiences must be mapped across a growing catalogue.

Inside the editor:

Open Components.

Add the Gaussian Splatting component to the canvas.

Open the component's properties.

Upload the supported Gaussian Splat asset.

Adjust its position, rotation, scale, framing, and starting view.

Set the surrounding background and presentation so they support, rather than compete with, the product.

SwiftXR projects can also support interactive elements such as hotspots. Use them selectively. A hotspot should answer a real product question, such as identifying a material, revealing a functional detail, or linking a feature to supporting information. If every surface becomes clickable, exploration becomes work.

The first frame matters. Before the shopper touches the viewer, the product should already appear at a persuasive angle and useful scale. Treat that opening view with the same care as the lead image in the product gallery.

Step 4: Publish the SwiftXR project

When the experience is ready, select Publish. If the project is already live, use Update to release the new version.

After publishing, open the dropdown beside the publish or update control, select Share, and copy the embed code. SwiftXR also provides a shareable link, which is useful for internal approval and device testing before the experience is placed on a live product page.

At this point, the Gaussian Splat has moved beyond capture. It is now a browser-based experience that can be distributed through the website.

Step 5: Add it to the product page

The exact placement route depends on the ecommerce platform.

Shopify

Install the SwiftXR Shopify app, connect the store, and map each product to its corresponding published SwiftXR project. SwiftXR's current plugin workflow is designed to render the linked experience on the relevant product page.

Wix

Install the SwiftXR Wix app and add the SwiftXR block to the required page in the Wix editor. Connect the published project, position the block within the product-page layout, and publish the site.

WordPress and WooCommerce

Use the SwiftXR plugin, shortcode, or Gutenberg block to place the published experience in the product page or product template.

Webflow, Squarespace, BigCommerce, or a custom website

Paste the SwiftXR embed snippet into the page's embed or custom HTML area. If the product template is managed dynamically, connect the correct published project ID through the site's existing content or catalogue workflow.

SwiftXR handles the interactive rendering. The page still owns the surrounding sales journey.

Where the viewer should sit on the page

Do not bury the Gaussian Splat at the bottom of a long product page and expect it to influence the decision.

Place it where the unresolved visual question appears. For a product whose finish, form, or craftsmanship is central to its value, that is usually within the main media gallery or directly beside the product information. For a large or complex item, the experience may work better after a short value proposition and before technical specifications.

Use shopper-facing language such as Explore in 3D, View Every Angle, or See the Product Up Close. Most customers do not need the term “Gaussian Splatting” to understand the benefit.

Keep the following outside the viewer and visible in the page itself:

• Product name and description
• Price and availability
• Dimensions and specifications
• Variant controls
• Delivery and return information
• Add-to-cart or enquiry action
• Accessible product images and alternative text

The viewer should strengthen the product page, not become the only place where essential information exists.

Protect page speed and mobile usability

Photorealistic 3D is persuasive only when the experience loads reliably.

Before launch:

• Test the page on a real phone, not only a desktop preview.
• Test on a slower mobile connection.
• Reserve a fixed space for the viewer to prevent layout movement.
• Use a clear poster or fallback image while the experience loads.
• Avoid loading the viewer before critical above-the-fold content unless it is the primary product visual.
• Consider lazy-loading the embed when it sits below the first viewport.
• Check that scrolling, zooming, and product interactions do not compete with one another.
• Compare page performance before and after implementation.

Google's web performance guidance notes that lazy-loading offscreen iframes can reduce bandwidth competition and improve Largest Contentful Paint. The right setup depends on where the SwiftXR experience sits and how important it is to the first view of the page.

Test the experience like a buyer

Run a product-page QA check before publishing to the full catalogue.

Area

What to verify

Product accuracy

The correct product, finish, orientation, and revision are shown.

First frame

The product is immediately recognisable and persuasively framed.

Interaction

Rotate, pan, zoom, hotspots, and links behave as intended.

Mobile

Touch controls are comfortable and the viewer fits the screen.

Browser coverage

The experience works across the browsers and devices important to the store.

Performance

The page remains stable and usable while the experience loads.

Fallback

A useful image and product information remain available if the viewer does not load.

Accessibility

The page provides descriptive text and does not hide essential information inside the interactive canvas.

Analytics

Viewer interaction and downstream actions can be compared with the normal product journey.

SEO

Product copy, crawlable information, canonical settings, and structured data remain intact.

Start with one representative product. Learn from real behaviour before scaling the workflow across the catalogue.

Measure the decision, not just the interaction

A high viewer interaction rate can be encouraging, but interaction alone is not the business outcome.

Track:

• Viewer load and interaction rate
• Time to first interaction
• Product-page engagement after interacting
• Add-to-cart or enquiry rate among viewers and non-viewers
• Mobile and desktop performance differences
• Exit rate after the viewer loads
• Customer questions about appearance, material, scale, or fit
• Return reasons connected to visual expectation

Use an A/B test or a controlled product rollout where possible. That separates novelty from genuine decision support and gives the team evidence for where Gaussian Splatting deserves a larger role.

Frequently asked questions

Do I need to code to put a Gaussian Splat on a product page?

Not for the standard SwiftXR workflow. You can create and publish the experience in SwiftXR, then use a platform plugin or copy the embed snippet into the website. A custom catalogue or heavily customised theme may still require implementation support.

Can I add Gaussian Splatting to Shopify?

Yes. SwiftXR provides a Shopify app that connects published SwiftXR projects to store products so the correct experience can appear on the relevant product page.

Does SwiftXR work with Wix and WooCommerce?

Yes. SwiftXR provides a Wix app, plus a WordPress and WooCommerce plugin with shortcode and Gutenberg options. A universal embed is available for other platforms.

Is a Gaussian Splat the same as a normal 3D model?

No. A conventional 3D model is usually built from polygon geometry, materials, and textures. A Gaussian Splat reconstructs appearance from multiple images or video using many positioned, coloured, semi-transparent Gaussian primitives. The two formats have different strengths.

Can a Gaussian Splat be used in AR?

SwiftXR supports 3D, AR, and VR experiences, but Gaussian Splats and polygon meshes do not behave identically. If real-scale AR placement is essential to the buying decision, validate the specific asset, device path, scale, and interaction before launch. A mesh or hybrid experience may be the better fit for some products.

Will a Gaussian Splat slow down the product page?

Any interactive 3D asset adds work for the browser. The impact depends on asset size, page placement, device, connection, and loading strategy. Clean the capture, test on real mobile devices, use a useful loading state, and consider lazy-loading when the viewer is below the fold.

What products benefit most from Gaussian Splatting?

Products where finish, texture, craftsmanship, irregular form, or visual presence strongly influences the purchase can benefit most. Furniture, décor, art, premium accessories, fashion pieces, equipment, and one-of-a-kind products are strong candidates, but every capture should be tested against the actual buyer task.

From captured product to commercial experience

Gaussian Splatting can preserve the visual richness that product photography often compresses. But the format is not the strategy.

The strategy is to identify what the customer cannot confidently understand from the existing page, then give them a better way to see it.

SwiftXR makes that leap practical. It takes a technically sophisticated capture and turns it into a publishable, interactive experience that can live where the buying decision already happens.

Do not just put your product online. Put it in their world.

Start a free SwiftXR project and publish your first Gaussian Splat experience.

Start Free Trial today.

No credit card. No developer. Live on your store in minutes.

Questions? Book a call or join the community on Discord.