WebVR Implementation Status
WebXR Device API
- Using the WebXR device API requires a compatible device running Android O or later.
- The WebXR device API is available on other browsers with a polyfill.
- Documentation is available from the Immersive Web Early Adopters Guide.
Today the API is available in:
|AR hit test support||Chrome Canary for the immediate future.||Enable the #webxr and #webxr-hit-test flags under chrome://flags|
|VR use cases||Chrome 66 and later||Enable the chrome://flags/#webxr flag. (The URL must be entered manually.)|
|VR use cases||Chrome 67 origin trial||Enable the chrome://flags/#webxr flag and sign up for the origin trial (explainer, sign-up form).|
Learn more about the immersive web at the Immersive Web Community Group.
Today the WebVR 1.1 API is available in:
- Firefox Nightly.
- Samsung Internet for Android and for Gear VR.
- A Chrome Origin Trial that ran from version 56 beta to June of 2017.
It's supported on:
- Daydream View since M56
- Google Cardboard since M57
It's also available through the WebXR Polyfill.
Find more information on browser implementation status on chromestatus.com.
Here are things to remember when building WebVR experiences today.
- You must serve your WebVR content over HTTPS. If you don’t your users will get warnings from the browser. See Enabling HTTPS on Your Servers for more guidance.
- The WebXR Polyfill may not always be a 1:1 match with native implementations of the spec. If you plan to use the Polyfill, be sure to check on both VR-capable and non-VR devices.
- For some types of sessions, users must click a button before AR or VR are available to your code. See the Immersive Web Early Adopters Guide for more information.