SwiftXR Logo

Blog

November 13, 2026
·4 min read

Add a 3D Model to Wix CMS Dynamic Pages


Otuokon Nsikak
Otuokon Nsikak
Add a 3D Model to Wix CMS Dynamic Pages

To add a different 3D model to each Wix CMS dynamic item page, publish each model as a SwiftXR project and store its approved HTTPS viewer URL on the matching CMS item. In Wix Velo, wait for the item dataset to load, read that item's URL, then set the HTML component's source. Keep the viewer collapsed when there is no approved URL, and leave the product photos and specifications visible on every page.

A lighting brand might have dozens of catalogue pages on one Wix template. If the template carries a fixed viewer URL, the first lamp can look right in testing while the same lamp appears on unrelated pages. The approval rule is simple: approve the item and its viewer URL together. A model loading successfully proves very little about whether it belongs on that page.

Choose the Wix route that matches your catalogue

This approach is for a custom catalogue built with Wix CMS dynamic item pages. The same page template takes its product name and images from a different CMS record at each item's URL. If your catalogue is already built on Wix Stores, start with the SwiftXR integration for Wix and evaluate its product mapping before adding a separate Velo integration.

Store the viewer URL with the product record

Use the SwiftXR 3D Viewer to set up each approved product model. Publish the project, then use the sharing options in the SwiftXR HTML guide to get the embed. Store the HTTPS URL from the iframe source in a dedicated URL field on the Wix CMS item. Store the URL alone, without the iframe markup. Open it directly and confirm the model before saving it against the product code.

Agree who owns each side of the mapping. The 3D owner approves the model and publishes the experience. The catalogue editor pairs the viewer URL with the CMS record and checks it against that item's photos. Leave the field empty for an item awaiting approval, even if a similar product already has a viewer.

Read the item after the Wix dataset is ready

Add an HTML component to the dynamic item template and set it to start collapsed. In the page's Velo onReady handler, register a handler for the item dataset's onReady event. Inside that handler, call getCurrentItem and read the field using its CMS field ID. The dataset may still be loading when the page handler runs; using the dataset's handler avoids reading the item too soon.

Check that the field holds a valid HTTPS URL on a host your team has approved. If it does, assign it to the HTML component's src property and expand the component. If the item or URL is missing or fails the check, keep the viewer collapsed. Never populate the template with an unrelated demo as a fallback. If your page changes items without reloading, Wix documents an onCurrentIndexChanged handler; apply the same check there before showing the next model.

Test three catalogue records before rollout

Use two products with visibly different shapes and a third with no 3D asset. Open each published item directly on desktop and on a phone. Check that the first two show the matching models, that the third shows no empty viewer panel, and that photos, dimensions and the enquiry action remain usable on all three. If the template lets visitors move between items, repeat the checks in both directions.

If a URL opens directly but the model is clipped or unavailable in Wix, inspect the published iframe and mobile layout before changing the model. If the wrong model also appears at the direct URL, hand it back to the 3D owner. If the direct URL is right but the Wix page selects a different one, check the CMS record and dataset mapping first.

For a first pilot, use one product family. Set up a SwiftXR 3D product viewer for two clearly different products, then run the three-record test before extending the template.

SwiftXR Logo

SwiftXR ©2026 / ALL RIGHTS RESERVED

PrivacyTerms