WebAR settings & the launcher

AR “just works” on published projects — these settings control how it’s offered.

WebAR settings

Per project, with a live settings preview:

• Keep WebAR launcher experiences available — the launcher stays on for published projects, giving phones a straight-into-AR path.
• Share AR launcher links without removing the main viewer flow — launcher links coexist with the normal viewer; offering AR-first entry doesn’t cost you the interactive 3D page.
• Disable launcher button — hide launcher entry on surfaces where AR-first isn’t wanted.

The launcher itself — what it is, launcher URLs and iframes — is covered in Links, QR & the launcher.

Plan entitlement

AR Support is a plan feature: launcher links and launcher embeds require it, while direct viewer sharing keeps working on every plan. The panel states this exactly where it applies (see Plans & billing).

Pre-launch checklist

• Scale: the model was exported in meters at true size — AR renders it 1:1 in the room (Preparing models).
• Configured products: multi-part selections merge server-side per selection and are cached — first entry per new combination warms the cache, repeats are instant.
• Your own AR button: call enterAR() from a real click handler (Localization & AR).
• Desktop: offer the QR handoff (getQr()), don’t hide AR entirely.
• Something still off? Troubleshooting lists the device-specific causes.