WebXR support landscape: what works in 2026

Portrait of the authorAuthor Placeholder1 min read

WebXR is a moving target. What worked in 2024 doesn't map to 2026. This is a snapshot of what we ship today across the GCC device mix.

Tier 1 — full WebXR

  • Chrome 130+ on Android 13+ — full SLAM, anchors, hit-testing.
  • Edge 130+ on Android — same Chromium-based path.
  • Samsung Internet 24+ — full WebXR with hardware-accelerated tracking.

Tier 2 — partial WebXR

  • Safari 17+ on iOS — WebXR Device API ships, AR Quick Look fallback for unsupported scenes.
  • Firefox 130+ on Android — works but anchors are flaky on giga-project plots.

Tier 3 — camera-only fallback

Older Android (12 and below) and Safari on older iOS get a camera-only fallback — full-frame video with the AR scene composited in 2D. Tracking quality drops, but the marketing experience is preserved.

Practical guidance

"Build for tier 1, degrade gracefully to tier 3, never assume tier 2."

Detection happens at scene load — XRSession.isSessionSupported('immersive-ar') tells you which tier you're on. The scene loader switches assets accordingly: high-LOD for tier 1, medium-LOD for tier 2, billboard fallback for tier 3.

Commission a spatial intelligence assessment