What WebXR is
MDN describes WebXR as a group of standards used together to render 3D scenes to hardware for virtual worlds (VR) or to add graphics to the real world (AR) [1]. The WebXR Device API gives access to head tracking, motion controllers, hand tracking and display output of such devices [4].
The W3C specification defines three session modes [2]:
| Mode | Meaning |
|---|---|
inline | 3D inside the page, no headset |
immersive-vr | a fully virtual environment on a VR headset |
immersive-ar | content over the real environment, defined in the AR module [3] |
Both documents have the W3C status Candidate Recommendation Draft, so they are not yet finished standards [2][3].
How it differs from Quick Look and Scene Viewer
AR Quick Look and Scene Viewer are operating-system viewers that open a finished file. With WebXR your own application keeps running in the browser, so in principle options could be changed inside AR. The trade-off: support varies more between browsers and devices than with the system viewers.
In practice
Many websites combine the routes. The model-viewer component by default tries WebXR, Scene Viewer and Quick Look in turn [5]. Before a project, check current browser support and test on the devices your buyers use.
For configurators
WebXR is worth it when buyers should adjust the product in its surroundings, such as furniture in a room. For a simple "how big is it in my space?" the system viewers are usually enough. See our 3D product viewer page for AR on product pages.