On this page
- Specification status
- Browser support (as-of 2026-05)
- Session modes and ecommerce relevance
- Ecommerce use cases
- Conversion and returns impact
- Technical implementation
- 3D file formats
- model-viewer
- 8th Wall
- Asset performance targets
- Developer tooling (as-of 2026)
- WebXR vs native AR
- Market sizing
- Key terms
- Frontier links (no page yet)
WebXR
WebXR
The WebXR Device API is a W3C browser standard that gives web pages access to augmented reality (AR) and virtual reality (VR) hardware — enabling retailers to deliver immersive product experiences (room-placement, virtual try-on, 3D viewers) without requiring any app download.
Specification status
The WebXR Device API reached W3C Candidate Recommendation Draft status as of mid-2026 — the final formal checkpoint before a specification is considered finished, requiring at least two independent, interoperable browser engine implementations. (source: web-platform-tests/interop issue #1021; vr.org June 2026)
The spec is modular: the core Device API is accompanied by ten satellite specifications — Anchors Module, Augmented Reality Module Level 1, Depth Sensing Module, DOM Overlays Module, Gamepads Module Level 1, Hand Input Module Level 1, Hit Test Module, Layers API Level 1, Lighting Estimation API Level 1 — all published by the W3C Immersive Web Working Group. (source: MDN Web Docs, last updated 2026-06-02)
A formal proposal was filed to make WebXR a focus area in Interop 2026 (web-platform-tests/interop issue #1021), but WebXR was not selected for the 2026 cycle — confirmed by the official Interop 2026 announcement on web.dev (2026-02-12), which lists 20 focus areas with no mention of WebXR. MDN still flags the API as "experimental" and "limited availability". (source: web.dev/blog/interop-2026; MDN 2026-06-02)
Chrome 144 (stable 2026-01-13) shipped the XRVisibilityMaskChange event, which provides a vertex-and-index mesh of the visible viewport to limit how much of the viewport is drawn, improving rendering performance. XRView objects now carry unique identifiers to pair with associated masks. (source: developer.chrome.com/release-notes/144, as-of 2026-01-13)
Browser support (as-of 2026-05)
| Browser | Support | Notes |
|---|---|---|
| Chrome 79+ | ✅ Full | Desktop + Android |
| Edge 79+ | ✅ Full | Desktop + Android |
| Opera 66+ | ✅ Full | |
| Samsung Internet 12+ | ✅ Full | Optimised for Samsung Galaxy XR |
| Meta Quest Browser | ✅ Full | Passthrough AR, hand tracking, anchors, plane detection |
| Safari on visionOS 2.0 | ⚠️ Partial | immersive-vr only; AR module NOT enabled |
| Firefox | ❌ None | Implementation paused after discontinuing Firefox Reality |
| iOS Safari | ❌ None | Apple has no public timeline |
| macOS Safari | ❌ None | Apple has no public timeline |
(source: testmuai.com, published 2026-04-28, last updated 2026-05-05; vr.org June 2026)
Safari WebXR support scope: vr.org (June 2026) states Safari on visionOS 2 "closed the last major cross-browser gap" and implies general cross-browser coverage. TestMuAI (May 2026) and MDN (June 2026) clarify that only immersive-vr is enabled on visionOS and that iOS Safari, macOS Safari remain unsupported with no committed timeline. The vr.org framing overstates coverage — the AR module is not enabled on visionOS and iPhone users cannot access WebXR natively.
The no-iOS-Safari gap means approximately 27% of global mobile web traffic (iOS share) cannot run native WebXR AR; iPhone users reach WebXR AR only via third-party browser apps (e.g. WebXR Viewer) or WebAR platforms such as 8th Wall that run their own SLAM engine independent of the browser WebXR API. (source: testmuai.com 2026-04-28)
Module support is fragmented across devices — hand input, hit testing, depth sensing, anchors, and lighting estimation are not universally available even on supported browsers. Feature detection is mandatory before using any module. (source: testmuai.com 2026-04-28)
Accessibility gap: canvas-rendered WebXR scenes are opaque to assistive technology; there is no standardised screen-reader access for WebXR content as of mid-2026. (source: testmuai.com 2026-04-28)
Session modes and ecommerce relevance
WebXR exposes three session modes:
inline— 3D viewer embedded in a standard browser canvas, no headset required; the most immediately relevant mode for ecommerce product pagesimmersive-ar— camera passthrough AR on mobile; powers room-placement and virtual try-on when device + browser support itimmersive-vr— full VR; requires headset hardware
The inline mode enables interactive 3D product viewers on any browser tab without requiring AR-capable hardware, making it the baseline ecommerce entry point. (source: testmuai.com 2026-04-28)
Ecommerce use cases
Product categories with the highest AR benefit: furniture and interiors (true-to-scale room placement), cosmetics (shade try-on on face), eyewear and jewellery (front-camera fitting), footwear (on-foot model), and technical accessories (overlay on own device). Fashion/apparel body-mapping try-on data is thin in current sources — most coverage skews to the above categories. (source: xictron.com 2026-03-05)
The mechanics: a customer opens a product page, taps "View in AR," points the smartphone camera at a surface, and a 3D model appears at true scale. The customer can rotate and reposition using finger gestures — no app download required. (source: xictron.com 2026-03-05)
Retailers cited: IKEA (furniture room placement), Shopify merchants (try-before-you-buy via browser), Ben & Frank Optics (glasses try-on). (sources: vr.org 2026-04-13; testmuai.com 2026-04-28)
Google has supported 3D/AR product listings in Search results via structured data ([[3DModel Schema]]) since 2020; shops with 3D product data have a higher probability of appearing in rich results, and the engagement signals (dwell time, lower bounce rate) may act as positive SEO ranking signals. (source: xictron.com 2026-03-05)
Conversion and returns impact
Conversion lift figures conflict across sources: xictron.com (2026-03-05) and multiple aggregators cite "up to 94% higher conversion rate" (attributed to Shopify data), "shoppers ~3× more likely to add to cart," "~50% higher purchase conversion," and "view ~7× more products." TestMuAI (2026-04-28) cites "94% higher conversion rates" and "25–48% lower returns." These statistics measure different KPIs and cohorts and should not be stacked multiplicatively. All are vendor-sourced or cite vendor-sourced studies; no neutral academic study corroborates these specific magnitudes. See also Virtual Try-On for similar conflicting conversion data.
(as-of 2025–2026 based on available vendor studies)
Technical implementation
3D file formats
The dominant 3D file formats for ecommerce WebAR: glTF/GLB (open Khronos web standard, supported by all browsers, Google, and Shopware — described as "the JPEG of 3D") and USDZ (Apple's format for AR Quick Look on iOS/macOS). A single source model typically generates both. (source: xictron.com 2026-03-05)
model-viewer
Google's <model-viewer> web component is described as the most pragmatic ecommerce AR integration — embeds via a few lines of HTML, loads glTF/GLB models, provides an automatic AR fallback (Scene Viewer/ARCore on Android, AR Quick Look on iOS), and activates only on user interaction, preserving Core Web Vitals. (source: xictron.com 2026-03-05) See model-viewer.
8th Wall
8th Wall (Niantic commercial platform) runs its own SLAM computer vision engine independent of WebXR, covering older devices without ARCore/ARKit support — recommended for more demanding AR use cases such as interactive room planners or gamified shopping, and is the primary path for iPhone users who cannot run native WebXR AR. (source: xictron.com 2026-03-05)
Asset performance targets
Optimised 3D asset targets for ecommerce: raw models (50–200 MB from CAD/photogrammetry) compressed to 2–10 MB glTF with Draco compression; recommended production target is under 5 MB per model to preserve PageSpeed scores. (source: xictron.com 2026-03-05)
Progressive enhancement pattern: AR-capable devices get full AR; devices without AR support get an interactive 3D viewer; older devices get high-quality 2D images — with assets loaded on-demand to avoid affecting page performance. (source: xictron.com 2026-03-05)
Developer tooling (as-of 2026)
Three.js remains the de facto standard for browser-based 3D; its built-in WebXRManager makes VR and AR development straightforward. A-Frame (declarative HTML, built on Three.js) and Babylon.js are the other major mature options with full WebXR support. (source: vr.org 2026-04-13)
WebGPU — the browser successor to WebGL — is now widely supported and brings near-native rendering performance to the browser, alongside improved hand tracking, eye tracking, and spatial audio APIs. Thanks to WebGPU and faster processors, the visual quality gap between WebXR and native AR has substantially closed since 2023. (source: vr.org 2026-04-13; madxr.io 2026-02-01)
Meta's Immersive Web Emulator runs as a Chrome extension and lets developers simulate a headset, controllers, and hand poses on desktop without physical hardware — enabling iteration on Three.js scenes without headset access. (source: vr.org June 2026)
Shopware natively supports 3D product visualization — glTF models can be uploaded as product media and displayed on the product page. (as-of 2026-03-05, source: xictron.com)
WebXR vs native AR
| Dimension | WebXR (browser) | Native AR (ARKit/ARCore) |
|---|---|---|
| Installation | None — opens in browser tab | App download required |
| iOS reach | Not available natively (no iOS Safari) | Full via ARKit |
| Tracking quality | Slightly lower; can drift over time | Higher; LiDAR depth on supported devices |
| Occlusion | Virtual objects float in front — no depth pass | Correct occlusion with LiDAR |
| Rendering | Near-native with WebGPU; gap closed vs 2023 | Native GPU |
| Asset compatibility | glTF/GLB; reusable for headsets | ARKit uses USDZ/RealityKit |
| Dev complexity | Web stack (JS, Three.js, model-viewer) | Swift/Kotlin + ARKit/ARCore |
(source: xictron.com 2026-03-05; madxr.io 2026-02-01; codebrewery.com — undated)
The occlusion limitation and tracking-drift claims are from codebrewery.com (undated, likely pre-2026). WebGPU rendering advances may have partially addressed these; no 2026 primary source confirms or denies current occlusion status.
Requiring an app download reduces engagement by 50–70% compared to browser-based experiences, according to research cited by MadXR (2026-02-01; no primary study linked). WebXR coverage as of April 2026 reaches over 5 billion people with web browsers in some form. (source: vr.org 2026-04-13 — no primary study linked for either figure)
For complex, graphically demanding experiences (AAA VR games, highly detailed simulations), native development retains a performance ceiling advantage; WebXR is described as compelling for the "enormous middle ground" of training modules, product configurators, marketing experiences, and interactive demos. (source: madxr.io 2026-02-01)
Market sizing
Market size figures conflict: MarketsandMarkets (cited via xictron.com 2026-03-05) valued the global AR shopping market at USD 3.4B in 2023, projecting USD 11.6B by 2028 (28% CAGR). Mordor Intelligence (2025-06, gated report, cited via search summary) valued XR in virtual retail at USD 5.01B in 2025 projecting USD 10.62B by 2031 (12.67% CAGR). BrandXR (2025 Research Report) describes AR adoption as "mainstream" with 60% of U.S. consumers interacting with AR (as-of 2025). These use different market definitions, base years, and methodologies — they are not directly comparable.
MarketsandMarkets figures use a 2023 base year (cited via xictron.com 2026-03-05). BrandXR figure is from 2025 report.
Key terms
| Term | Meaning |
|---|---|
| WebXR Device API | W3C browser API for AR and VR hardware access |
| inline session | 3D viewer in standard browser canvas; no headset required |
| immersive-ar session | Camera passthrough AR; requires compatible device + browser |
| immersive-vr session | Full VR immersion; requires headset |
| glTF/GLB | Khronos Group open 3D format; the standard for web-based 3D |
| USDZ | Apple's Universal Scene Description format; required for AR Quick Look |
| SLAM | Simultaneous Localisation and Mapping — the tracking engine behind AR anchoring |
| Draco compression | Google compression library for 3D mesh data; reduces glTF file size |
| WebGPU | Browser successor to WebGL; near-native GPU rendering in browser |
| model-viewer | Google web component for embedding 3D/AR on product pages |
| 8th Wall | Niantic commercial WebAR platform with own SLAM engine |
Frontier links (no page yet)
WebGPU · model-viewer · glTF · USDZ · 8th Wall · Three.js · AR Quick Look · 3DModel Schema · Android XR