A Practical Guide to WebXR
The web standard for delivering virtual and augmented reality experiences in the browser, without installing an app.
Imogen Clarke
The key figures
- Standard
- the W3C WebXR Device API
- Modes
- immersive VR and immersive AR sessions
- Libraries
- Three.js and other frameworks support WebXR
- Security
- requires a secure context over HTTPS
Why this is worth getting right
WebXR lets people try AR and VR from a link, but device and browser support vary and performance budgets are tight.
Do this, not that
Do
- Check support on the target devices and browsers
- Keep models light for mobile performance
- Offer a non-XR fallback view
- Test with the headsets and phones your audience uses
- Design comfortable motion for VR
Don’t
- WebXR as the only way to view content
- Heavy scenes that drop frames
- Motion that causes discomfort
- Assuming support on all phones
When to bring in help
Our advice Bring in help when planning browser-based AR or VR experiences.
Where this comes from
- W3C — WebXR Device API
- MDN Web Docs — WebXR Device API
- Three.js — WebXR documentation
The figures and practices above come from the sources listed.
Working on something like this?
We take on 3D Design & Development work for teams who want it done once, properly. Tell us what you are building and we will tell you honestly whether we are the right studio for it. Start a project.
Where to go next
Spotted something wrong? Report an error on this page. We correct on the page and say what changed.
