When it comes to mobile webar, augmented reality used to mean downloading an app. For years, that single requirement — install our app first — was the wall that AR marketing kept hitting. Customers would not do it, and who could blame them: nobody downloads a 200MB app to look at one sofa.
Mobile WebAR removes the wall. It delivers augmented reality directly in the smartphone browser — the customer taps a link, scans a QR code, and the AR experience opens. No download, no account, no storage space sacrificed. In 2026, it is the default way businesses deploy AR, and this guide explains what it is, how it works, where it shines, and where it does not.
What mobile WebAR is
WebAR is augmented reality delivered through web technologies instead of a native app. Mobile WebAR simply means the flavour designed for smartphones — which is where almost all consumer AR happens.
The experience starts the way any web page does: a link in an email, a QR code on packaging, a button on a product page. Tapping it opens the phone browser, which requests camera access. The page then uses the camera feed, the phone's motion sensors and on-device processing to place virtual 3D content into the real world as seen through the screen.
Because it is the web, everything businesses like about the web applies: the experience is instantly updatable (change the 3D model on the server and every user sees the new version), shareable with a URL, measurable with standard analytics, and indexed and linked like any page. Because it is AR, the content sits in the customer's real environment — on their floor, on their face, on their street.
How it works on a phone
Three things have to happen for WebAR to work, and the phone does all of them.
First, tracking: the browser-based AR engine works out where the phone is and what it is looking at. On most retail experiences this means plane detection — finding floors, tables and walls to place objects on. More advanced experiences use SLAM-based world tracking to build a persistent map of the space. Either way, the heavy lifting happens through WebXR (on Android Chrome) or a commercial WebAR platform's own engine (needed on iPhone, where Safari does not support WebXR).
Second, rendering: the 3D content is drawn over the camera feed in real time using WebGL, the browser's 3D graphics API. This is why 3D optimisation matters so much in WebAR — a phone browser has far less headroom than a games console, so models must be built to strict polygon and texture budgets. Well-made real-time 3D models look superb; unoptimised CAD exports judder.
Third, interaction: touch gestures (tap, pinch, drag) let users place, rotate, resize and configure the virtual object. Good WebAR design keeps this to the essentials — the customer is holding a phone up, often one-handed, and will not tolerate a complicated interface.
All of this runs on the device. The 3D assets download when the experience opens (which is why keeping file sizes small matters for load times), but the camera processing and rendering happen locally — your customer's living room is not streamed to a server.
WebAR vs native AR apps: an honest comparison
Native apps still exist and still have a place, so the comparison is worth making properly.
Reach. This is WebAR's decisive advantage. A link reaches everyone; an app reaches only the people willing to install it. For marketing campaigns, retail and events — anywhere the audience is broad and the interaction is short — WebAR wins by an order of magnitude on participation. The drop-off at download our app is brutal and well documented across the industry.
Capability. Native apps win here. They get deeper access to sensors, can use the full power of ARKit (iOS) and ARCore (Android), handle larger and more complex scenes, and work offline. If you are building persistent multi-user AR, complex occlusion, or experiences that run for an hour, native is the right call.
Cost and speed. WebAR is typically faster and cheaper to build and far cheaper to maintain: one codebase for all devices, instant updates, no app-store review cycles. Native means two codebases (or a cross-platform framework), store submissions, and update friction.
Discovery. Apps are discovered in app stores; WebAR is discovered through links, QR codes, search and social. For a retailer, scan the QR code on the shelf edge is a more natural discovery path than find our app.
The rule of thumb: if the experience is short, the audience is broad, and the goal is engagement or sales, choose WebAR. If the experience is long, complex, or needs device capabilities the browser cannot reach, choose native. Most business AR briefs we see land firmly in the first camp.
The platform landscape in 2026
You do not build WebAR from scratch — you build on a platform. The landscape has settled into a few clear options.
WebXR is the open web standard, supported in Chrome on Android. It is free and capable, and it is the right foundation for Android-first or Android-only projects. Its limitation is Safari: with no WebXR on iPhone, a WebXR-only build does not serve iOS users, which in the UK is roughly half the smartphone market — not a compromise most businesses can make.
Commercial WebAR platforms — led by 8th Wall, with others including Zappar's Zapworks and Vectary-style tools at the simpler end — solve the iOS problem with their own tracking engines and wrap the whole thing in development tools, hosting and analytics. They charge for it: typically a monthly platform fee plus usage-based pricing. For most commercial projects, this is the pragmatic choice — cross-device compatibility out of the box, in exchange for an ongoing platform cost that must be factored into the business case.
model-viewer and AR Quick Look cover the simplest case: view this 3D model in my space. Google's model-viewer web component shows interactive 3D on the page and hands off to AR on the phone; Apple's AR Quick Look does the same on iOS from a USDZ file. For basic see it in your room product visualisation, this free, lightweight route is often all you need — no platform fees, no complex build.
Choosing between them comes down to the experience you need: simple product view (model-viewer), branded cross-device campaign with analytics (commercial platform), Android-only technical deployment (WebXR). An honest agency will recommend the cheapest option that does the job — beware anyone who reaches for the most expensive platform by default.
Business use cases in 2026
WebAR has moved well past novelty. The use cases with real commercial traction:
- Retail product visualisation: view in your room for furniture, appliances and homeware; virtual try-on for eyewear, jewellery and cosmetics. The pattern is always the same — answering a fit or scale doubt that blocks purchase.
- 3D product configurators: configure a product in 3D, then drop the configured version into your space. Our 3D configurator work for manufacturers pairs naturally with WebAR viewing — design it, then see it at full scale.
- Packaging and print: QR codes on packaging that launch assembly instructions, product stories or reorder pages in AR. High scan rates because the context (holding the product) is perfect.
- Events and out-of-home: posters, billboards and exhibition stands that come alive when scanned. No app download means the participation rate is a multiple of what app-based AR ever achieved.
- Property and construction: viewing off-plan developments at the site, or visualising renovations in the actual rooms.
- Training and manuals: AR instructions anchored to real equipment — particularly effective for installation and maintenance, where the alternative is a paper manual.
- Tourism and wayfinding: historical reconstructions at heritage sites, navigation overlays in venues — world-tracked WebAR territory when content must persist in space.
Benefits for businesses
The business case for WebAR rests on four pillars. Reach: no download means participation rates far above app-based AR — campaigns routinely reach multiples of the audience an app could. Speed to market: web deployment means updates in minutes, not app-store review cycles. Cost: one build serves all devices, and simple use cases need no platform fees at all. Measurability: standard web analytics show exactly what users did — scans, interactions, dwell time, click-through — tying the experience to commercial outcomes.
There is a softer benefit too: novelty that has matured into utility. In 2020, AR was a gimmick brands tried for press coverage. In 2026, customers encountering a view in your room button expect it to work and judge the retailer if it does not. WebAR has crossed from innovation budget to conversion infrastructure — which changes how it should be evaluated. Judge it like any conversion tool: does it lift the metrics that matter?
Limitations to know about
An honest guide includes the constraints. Capability ceiling: the browser cannot match native AR for complex scenes, advanced occlusion or long sessions. iOS fragmentation: Safari's lack of WebXR means cross-platform builds depend on commercial platforms or lowest-common-denominator approaches. Performance discipline: 3D assets must be aggressively optimised, and load times on mobile networks must be designed for — a 50MB model will lose most users before it renders. Tracking environments: poor lighting, blank walls and crowds degrade tracking, as with all camera-based AR. Privacy UX: camera permission prompts need careful handling — users should understand why the camera is needed before the browser asks.
None of these are fatal. They are the normal engineering constraints of the medium, and they are all manageable with proper scoping — which is precisely why the scoping conversation matters more than the technology choice.
Getting started
Start with the use case, not the technology. Identify the customer doubt your WebAR experience will answer, the context in which customers will encounter it (product page? packaging? event?), and the metric that will prove it worked. Then pick the lightest platform that delivers that experience, build optimised 3D assets, and pilot with real users before scaling.
The most common failure mode is building an impressive AR demo with no distribution plan — a brilliant experience that nobody finds. The link, the QR code placement, the call to action on the product page: these unglamorous details determine whether WebAR performs. Plan them first, not last.
If you are considering WebAR for your business, get a free consultation. We will help you identify the use case, recommend the right platform honestly — including when the answer is the free, simple option — and scope a pilot you can measure.
For more information, see GOV.UK.