Photos show what a product looks like. A 3D AR product viewer lets shoppers rotate it, inspect details and place it in their own room before buying. For furniture, home goods, fashion accessories and equipment, that can answer questions that otherwise lead to hesitation or returns. Building one well is less about flashy effects and more about a solid asset pipeline, broad device support and fast loading.
What the experience usually includes
- An interactive 3D viewer on the product page where users can rotate, zoom and sometimes switch materials or colors.
- A View in your space button that opens augmented reality on supported phones and tablets.
- A QR code on desktop or in print that sends people straight to the AR view on their phone.
- Variants and configurations, such as fabrics or finishes, reflected in the model.
- Analytics on views, interactions and AR launches.
Formats: GLB for the web and Android, USDZ for iOS
Two file formats cover most needs. GLB, the binary form of the glTF standard, is the common choice for web viewers and for Android’s Scene Viewer. USDZ is the format Apple’s AR Quick Look uses on iPhone and iPad. Supporting native AR on both platforms therefore usually means producing and maintaining both files for each product and variant. Native AR viewers are attractive because they use the operating system’s own AR capabilities, so shoppers do not have to install an app.
The asset pipeline is where projects succeed or stall
Most of the effort in a 3D commerce project goes into the models, not the viewer code. Plan the pipeline carefully:
- Source the models. They may come from CAD files used in manufacturing, from 3D artists working from photos, or from photogrammetry scanning. CAD files are precise but usually too heavy and need conversion.
- Optimize geometry. Reduce polygon counts to what is visible on a phone screen. Detail can often be carried by textures instead of geometry.
- Prepare realistic materials. Use physically based rendering materials so wood, fabric and metal react to light convincingly. Keep texture sizes sensible.
- Compress. Techniques such as Draco mesh compression and compressed textures shrink files significantly for web delivery.
- Export both formats and check them side by side for scale, orientation and material differences.
- Validate real-world scale. A sofa that appears at the wrong size in AR destroys trust instantly.
- Store and version the assets with clear naming tied to product and variant IDs.
Choosing technology for your 3D AR product viewer
| Option | What it is | Good fit when |
|---|---|---|
| model-viewer | An open-source web component from Google for displaying 3D models with AR support | You want a reliable viewer with AR launch and minimal custom code |
| three.js | A widely used JavaScript 3D library with full control over scenes and rendering | You need custom interactions, configurators or special effects |
| Platform plug-ins | 3D features offered by e-commerce platforms or third-party services | You want something quick and your catalog fits their constraints |
| Custom platform | Your own system managing models, variants, QR codes and analytics | 3D and AR are central to your offer or you serve many brands |
If you are unsure whether a plug-in or a custom build makes sense, our guide to custom software vs off-the-shelf lays out the trade-offs.
Performance and fallbacks
Accessibility matters as well. Provide descriptive text for the model, make controls usable with a keyboard and avoid motion that starts automatically and cannot be stopped. A 3D viewer should enhance the product page, never replace the essential information on it.
3D files can be large, and product pages must stay fast. Show a static poster image first and load the model only when the user interacts or the viewer scrolls into view. Keep an eye on file sizes per model, and test on mid-range phones, not just the latest devices. Always provide a graceful fallback: if AR is not supported, the button should explain why or simply not appear, and the regular photo gallery should remain available.
Bridging print, showroom and online with QR codes
QR codes connect physical touchpoints to digital experiences. A catalogue, trade-show stand or showroom tag can link straight to a product’s AR view. Generate codes per product, point them at a URL you control so you can update destinations later, and track scans so you know which channels drive engagement.
A real-world example
Our Sanctus project is a multi-tenant SaaS platform for furniture brands. Each brand manages its own catalogue with a 3D viewer, native AR through GLB and USDZ files, QR catalogues, team roles and analytics, all from one system. It shows how 3D and AR become far more valuable when they are part of a manageable platform rather than one-off embeds.
Measuring whether it works
Decide what success means before launch so you can judge the investment fairly. Useful signals include:
- Share of product page visitors who interact with the 3D viewer.
- AR launches per product and per device type.
- QR scans by channel or printed piece.
- Conversion and return behavior for products with and without 3D, compared over the same period.
Bring your products to life with SiteWright Technologies
SiteWright Technologies builds 3D viewers, native AR experiences and the platforms that manage them, from asset pipelines to analytics. If you want shoppers to see your products in their own space, explore our full-stack development services or get in touch.


