// Tech

<model-viewer> AR — Augmented Reality with One Attribute

model-viewer adds AR support with a single HTML attribute — visitors view your 3D model in their physical space via mobile camera.

Get a quote All 3D services

model-viewer's AR feature is one of the simplest paths to WebAR. Add `ar` attribute and `ios-src="model.usdz"` (Apple Quick Look format) to your model-viewer tag, and mobile visitors get an "View in AR" button. Tap takes them out of the browser into native AR (Scene Viewer on Android, Quick Look on iOS), they place your model in real space. Use cases: furniture e-commerce ("see this couch in your living room"), fashion try-on for jewelry/watches, educational content (anatomical models, historical artifacts). Pros: simplest setup possible. Cons: limited to single-model AR, no custom AR interaction logic.

When this is overkill

If the goal is a simple e-commerce listing or content blog, a full model viewer ar setup is overkill — a CSS-driven hero plus static images converts just as well at 1/10 the cost. model viewer ar earns its keep when the brand needs a memorable visual moment or when 3D actually clarifies the product (configurators, tours, demos).

What you get hands-off

After delivery: source repository on GitHub (private), commented code, a 5-min Loom walkthrough explaining the scene logic, and the asset pipeline documented. First year of hosting and minor revisions is included. After that we agree on a maintenance plan if needed.

What this delivers

Concrete output: a working model viewer ar integration on a real production site, not a demo. The integration includes device-tier detection so weak phones get a lighter version automatically. Source files are handed over in their original formats — Blender, GLSL, glTF — so any future developer can continue where I stopped.

How I work with it

On a typical project, model viewer ar ships as a self-contained module: one entry-point JS file, one CSS file, asset bundle below 1.5MB total. I keep the integration sandboxed so the rest of the site stays SEO-friendly classical HTML. Frame budget targets 60 FPS on a mid-range Android, with a measurable fallback below.

Frequently asked questions

Why pick this technology over alternatives?

It has the largest production-quality ecosystem, the most documentation, and the most experienced developers available. For a site you want to maintain for 3+ years, ecosystem maturity matters more than feature peak.

What if a newer tool comes out next year?

I track new tooling and migrate when it makes sense, but only after the new tool ships stable production releases for at least 6-9 months. I don't rebuild client sites on bleeding-edge tools — that's the path to broken sites.

How long does this take?

Standard scope: 4-6 weeks from contract signature to live site. Larger scope (configurator, multi-scene scrollytelling) takes 8-12 weeks. Rush projects (2-3 weeks) are accepted with a 30-40% rush surcharge.

What does it cost?

Hero-section 3D upgrade: \$1,500-\$2,500. Full multi-scene 3D site: \$3,500-\$8,000. Configurator with custom shaders: \$5,000-\$12,000. All fixed-price, source code included. EUR equivalents on request.

What if my visitors are on weak phones?

The site detects device tier before the first scene loads and serves a lighter version on weak hardware (fewer particles, simpler shaders). Devices without WebGL get a static fallback that preserves the visual language and conversion path.

Ready to ship a 3D experience?

Tell me what you need — fixed price, fixed deadline, no surprises.

Get a quote +381 61 224 8989