· Mimic XR

WebXR Browser Compatibility in 2026: A Production Checklist

Check WebXR browser support across Android and visionOS. Learn how to test AR and VR modes, diagnose session failures and plan useful fallbacks before launch.

Concept illustration: a phone, laptop and generic XR visor arranged around a browser-based spatial architecture demo, coherent cross-device testing scene with no readable interface labels.

Which browsers support WebXR? Documented routes include Chrome on supported Android devices, Chrome on Android XR, and Safari on visionOS for immersive VR. Support still depends on the device, session mode and requested features. A normal 3D viewer is not proof of immersive support. This documentation-based guide was checked on 30 October 2026; it is not a claim that Mimic XR has tested every browser and device.

Cover image: editorial concept illustration. It does not depict a tested device comparison or a Mimic XR client project.

In this guide

Which browsers support WebXR?

A conventional browser-based 3D viewer can offer rotation, zoom and product options without entering an immersive session. WebXR adds an interface for supported immersive devices and modes. Treat these as separate capabilities in the brief.

MDN’s WebXR reference marks the API as having limited availability and requiring a secure context. Use its current compatibility information as a starting point, then test the combinations your audience actually uses. A browser-family name alone is not a release acceptance criterion.

Chrome on Android phones: Google documents WebXR AR on ARCore-supported devices with Google Play Services for AR installed and enabled. Check the actual phone against Google's WebXR requirements. Installing Chrome alone does not establish AR compatibility.

Chrome on Android XR: Android's developer guide lists WebXR support and features including AR, hit testing, hand input and anchors. Treat this as a separate target from Chrome on an Android phone. Test the precise headset or wired-glasses configuration and the features your application requests.

Safari on Apple Vision Pro: WebKit documents immersive-vr support beginning with Safari 18 on visionOS 2. WebKit's release notes establish that platform-specific support; they do not establish the same support on iPhone, iPad or Mac. Check AR and optional features separately rather than treating all Safari devices as equivalent.

These are documented examples, not an exhaustive certification list. For other desktop, mobile and headset browsers, check current compatibility documentation and run the same capability tests. Record the operating system and device alongside the browser name; classify an untested combination as unverified.

Test modes and features separately

Record whether the experience needs immersive VR, immersive AR, hand input, hit testing or other capabilities. A device may support one mode without providing every optional feature. Your application should check capabilities and handle an unsuccessful session request gracefully.

A useful test record names the hardware, operating-system version, browser version, required features and observed result. Include the date. Repeat the important journeys after browser, platform or application updates instead of treating a one-time compatibility result as permanent.

A practical support check has two stages. First check for navigator.xr, then call isSessionSupported('immersive-ar') or isSessionSupported('immersive-vr') for the mode you need. Handle both false and a rejected promise. MDN's isSessionSupported reference explains that this is a mode check; it does not certify your assets, interactions or complete feature set.

Start the immersive session from a user action such as an Enter AR button. Declare essential capabilities in requiredFeatures and enhancements in optionalFeatures, then handle a rejected requestSession call. A supported mode can still fail when required features or permissions are unavailable. Follow the requestSession guidance and retain the non-immersive journey until a session actually starts.

Provide a useful fallback

If immersive mode is unavailable, retain the product information, a conventional 3D viewer or an accessible image-and-text explanation. Explain the alternative clearly and keep the next action available. Do not leave visitors at a disabled button with no explanation.

Apple’s Quick Look workflow is a separate route for supported AR model viewing. A platform viewer and a WebXR session are not interchangeable, so scope and test the chosen route explicitly. Keep asset preparation and interaction expectations consistent with that route.

Include permissions and interrupted sessions

Serve production over HTTPS and request only the capabilities the experience needs. Test the visitor declining permission, switching tabs, rotating the phone, losing connectivity and ending the immersive session. The page should recover without losing the essential product information.

Measure asset transfer and interaction performance on the slowest supported device and connection. Test touch, keyboard and non-immersive navigation separately. A fast desktop demo cannot establish mobile usability.

If WebXR works on a standalone test page but fails inside an embedded experience, inspect the embedding page and its Permissions Policy. An xr-spatial-tracking restriction can reject the support check with SecurityError. Test the production iframe and origin configuration, not just a local demo. Do not label every session failure as an unsupported browser.

Test the actual entry route: a QR code, email link or social-app link may open a different browser context from the one used in development. If that context cannot run the experience, explain how to open the page in a tested browser and keep a usable 3D, image or text alternative available.

Define a release matrix

Build a short matrix with supported combinations, supported-with-fallback combinations and combinations you do not support. Give each a named acceptance journey. For a product viewer, that might be opening the item, changing a finish, inspecting a detail and requesting a quote.

For each release test, record: device model, OS and browser versions, test date, entry route, session mode, required features, permission result, session-start result and fallback result. Then complete one business journey—inspect the product, select an option and request information—and verify that the same next action remains available after leaving XR. Mark each combination as passed, fallback-only, failed or untested.

To scope a compatibility review, send the target audience's device mix, required AR or VR interactions, existing assets, launch date and intended embed or campaign links. The XR project brief template helps capture those requirements before agreeing device coverage, testing effort and fallbacks.

Use WebXR development to plan the implementation and 3D asset production to prepare the content. Contact Mimic XR with your priority devices and intended experience.

Frequently asked questions

Does WebXR work everywhere?

No. Support varies by browser, operating system, device, mode and feature.

Is a 3D viewer the same as WebXR?

No. A conventional 3D viewer may work without immersive device access.

Does production need HTTPS?

Yes. WebXR is available in secure contexts on supporting browsers.

Can one compatibility test cover all phones?

No. Test the actual device and browser combinations you intend to support.

Is Quick Look a WebXR session?

No. It is a separate platform viewing route with its own requirements.

What happens if permission is declined?

The page should explain the limitation and retain a useful non-immersive experience.

Should unsupported visitors be blocked?

Provide an alternative that preserves essential information and the next action.

When should compatibility be retested?

After relevant browser, device-platform or application updates, and before a major campaign.

Does Safari support WebXR?

Safari on visionOS supports immersive VR, documented by WebKit from Safari 18 on visionOS 2. Do not extrapolate that support to every Apple device or to immersive AR. Check the required mode and features on the exact device; Quick Look is a separate viewing route.

Why can WebXR fail even when the browser supports it?

A supported mode does not guarantee that session creation will succeed. Required features, permissions, embedding policy or the device configuration can prevent it. Check the error, test the production context and preserve the fallback experience.

Sources and further reading

W3C — WebXR Device API: the web standard for virtual- and augmented-reality device access.

MDN Web Docs — WebXR Device API: browser-facing implementation guidance and compatibility context.

Khronos Group — OpenXR: the open standard for cross-platform XR application access.

About this article

Mimic XR is an extended reality production studio based in Potsdam, Germany. This article provides general planning information; project decisions should be validated against current hardware, platform, privacy and operational requirements.

Creation note: AI tools assisted with drafting and structure. Mimic XR reviewed and is responsible for the published content. External technical sources are linked where relevant. Last reviewed: 29 October 2026.

Keep reading

Related articles.