WebXR is the browser standard for virtual and augmented reality. It lets people open VR or AR experiences from a link or QR code without installing an app.

Does WebXR work on iPhone?

Not for AR in Safari on iPhone. iPhone users need fallbacks such as Apple's AR Quick Look through Google's model-viewer, an App Clip, or a native app built with ARKit or Unity.

Does WebXR work on Meta Quest?

Yes. The Meta Quest Browser supports immersive VR and passthrough mixed reality through WebXR.

What framework should I use for WebXR?

three.js for custom experiences, A-Frame for fast prototypes, Babylon.js or PlayCanvas for richer apps, Needle Engine for Unity content, and model-viewer for product viewers that also work on iPhone.

Should I build WebAR or an AR app?

Choose WebAR for reach, campaigns and fast launches; choose a native or Unity AR app when accuracy, features or iPhone AR support matter most.

WebXR in 2026: VR and AR in the Browser, Explained

The short answer

WebXR is the browser standard for VR and AR: people open an experience from a link or QR code with no app to install. In 2026 it works well on Meta Quest's browser for VR and passthrough, on Chrome for Android for AR on ARCore phones, and for VR in Safari on Apple Vision Pro. Safari on iPhone still does not support WebXR AR, so iPhone users need fallbacks such as AR Quick Look or a native app. Choose WebXR for reach and speed to launch; choose native apps when accuracy or iPhone AR matters most.

Where WebXR works

Device and browser	VR	AR
Meta Quest Browser	Yes	Passthrough mixed reality
Chrome on Android (ARCore devices)	Limited use	Yes, immersive AR
Safari on Apple Vision Pro	Yes, by default since visionOS 2	Not supported
Safari on iPhone and iPad	No	Not supported; use AR Quick Look or an app
Desktop browsers with PC VR	Varies by browser and headset	No

Our article on ARKit vs ARCore vs WebXR explains why the iPhone gap decides many AR projects, and how our AR furniture demo works on iPhone shows a real example.

Frameworks

Framework	What it is	Good for
three.js	The most widely used JavaScript 3D library, with WebXR support	Custom experiences, maximum control
A-Frame	HTML-like framework built on three.js	Fast prototypes, simple scenes
Babylon.js	Full-featured 3D engine from Microsoft	Richer apps and games
PlayCanvas	Web game engine with a visual editor	Teams wanting an editor and collaboration
Needle Engine	Brings Unity scenes to the web	Teams with Unity content
model-viewer	Google's web component for 3D models with AR fallbacks	Product viewers that work on iPhone via AR Quick Look

The iPhone fallback

For product visualisation, a practical pattern is model-viewer: Android users get WebXR or Scene Viewer, and iPhone users get Apple's AR Quick Look with a USDZ version of the model. It is not full WebXR, since interactions are limited, but it covers "see it in your room" for most shoppers. For richer iPhone AR, an App Clip or a full app built with ARKit or Unity AR Foundation is needed.

8th Wall and migrations

8th Wall, a commercial WebAR platform that worked around some browser gaps, ends hosted projects on 28 February 2027. Teams with live campaigns or printed QR codes should plan a migration; our 8th Wall migration guide covers the options.

Good uses for WebXR

Campaigns and packaging: scan a QR code, see the experience in seconds.
Product viewers: furniture, appliances and products in the customer's room.
Events and exhibitions: no install queues.
VR demos and training previews: share a link to a Quest headset.
Prototypes: test an idea before investing in a native app.

Performance tips for WebXR

Compress models: glTF with mesh compression and compressed textures can cut download size dramatically.
Load progressively: show something useful in a second or two, then stream the rest.
Keep draw calls low: merge static objects and share materials, especially for mobile AR.
Target the device: standalone headsets and phones need lighter scenes than desktop browsers.
Test on real hardware: desktop emulators hide most performance problems.

A typical WebAR campaign, step by step

Define the moment: what the customer should see in five seconds after scanning.
Prepare 3D assets at real-world scale and compress them for the web.
Build the experience with a WebXR framework, plus model-viewer or AR Quick Look for iPhone.
Generate QR codes and short links, and track scans and sessions with analytics.
Test on a range of Android phones and iPhones before printing anything.
Plan hosting for the length of the campaign and beyond, so printed codes keep working.

Limits to plan around

Performance is lower than native apps; keep models light and scenes simple.
Fewer platform features, such as advanced tracking and some sensors.
iPhone AR is missing, as above.
Download size matters: every second of loading loses visitors.

Measuring results

Because WebXR runs in a browser, normal web analytics work: track scans, page loads, how many visitors start the AR or VR session, how long they stay, and what they do next, such as visiting a product page. These numbers make WebXR campaigns easy to compare with other marketing.

Web or app?

Choose WebXR when	Choose a native or Unity app when
Reach and zero install matter most	Accuracy and features matter most
The audience is mostly Android or Quest	Many users are on iPhone and need AR
It is a campaign or short experience	It is a product people return to
You need to launch fast	You need offline use or deep device features

Costs

A focused WebAR or WebXR experience fits our VR and AR packages, starting at $999 for a single-scene experience or WebAR demo and $2,999 for a complete app. Our AR app cost guide breaks down budgets further.

Working with us

We build WebXR experiences, product viewers and native AR apps, and help teams choose between them. Try our live browser AR demos or see AR development.

Sources: W3C Immersive Web: WebXR Device API · MDN: WebXR Device API · Google: ARCore and WebXR · Road to VR: visionOS 2 enables WebXR · Google: model-viewer · three.js. Checked October 20, 2026.

WebXR in 2026: VR and AR in the browser