Interactive 3D that loads fast on a phone.
Product configurators, viewers and scenes that run in the browser, with no plug-in to install.
A 3D vase turning in a browser viewport while its glaze is switched in a material picker.
Overview
WebGL draws 3D graphics directly in the browser. We use it to build product configurators, model viewers and interactive scenes that people can turn, zoom and customize. We set a performance budget for mobile before modeling starts, because a beautiful scene that stalls on a phone is a broken scene.
A good fit if
- Customers ask what it looks like in another finish, or returns say "not as expected".
- There are more combinations than photos can cover.
- Products are made to order or sold by quote.
- A launch needs a 3D moment that still loads on a phone.
Not the right start if
- The products are cheap or impulse buys that photos explain. Good photos and a 360° spin may be enough.
- Nobody can supply the option and price data. The configurator needs it. Start there.
- There's no product question behind it, only "it would look cool". Tell us what you want customers to understand, and we'll start there.
Performance
From an 80 MB CAD file to a phone
Factory files are built for accuracy, not phones. Apply each step and watch the download and the memory fall.
- Inside the 4 MB budget.
Inside the 4 MB budget.
80 MB to download and 340 MB of memory. Far over budget: a phone on a weak signal gives up first. 18 MB. Hidden parts removed and detail cut where nobody can see it. 6 MB. The geometry is packed with Draco or Meshopt. 3.2 MB, and memory falls from 340 MB to 85 MB. Download size and memory are different budgets. 3.4 MB. Small extra files let distant views draw fewer details, so it stays smooth. Inside the 4 MB budget.Every case
- CAD export
- 80 MB to download and 340 MB of memory. Far over budget: a phone on a weak signal gives up first.
- Clean up and reduce
- 18 MB. Hidden parts removed and detail cut where nobody can see it.
- Compress the shape
- 6 MB. The geometry is packed with Draco or Meshopt.
- Compress the textures
- 3.2 MB, and memory falls from 340 MB to 85 MB. Download size and memory are different budgets.
- Lighter versions for distance
- 3.4 MB. Small extra files let distant views draw fewer details, so it stays smooth.
- All steps applied
- Inside the 4 MB budget.
Sample values for one product. Real budgets are set per product in step 2.
Process
How it runs
You keep
- 01An asset inventory and a route for each product.
- 02A performance budget and a device test list.
- 03A compressed model and a material reference.
- 04The script and a validation report per model.
- 05An options-to-SKU map, with prices worked out on the server.
- 06Fallbacks that work without 3D.
- 07An analytics plan and a test plan to compare with and without 3D.
-
01 of 07
Audit the assets.
What files, photos and options you have, and which route fits each product.
You keep An asset inventory and a route for each product.
-
02 of 07
Set the budgets.
File size, texture size and frame rate, on a named mid-range Android phone.
You keep A performance budget and a device test list.
-
03 of 07
One product, all the way.
A hero product through the full pipeline, checked in AR at true size.
You keep A compressed model and a material reference.
-
04 of 07
The pipeline.
A repeatable script that cleans, compresses and checks every model.
You keep The script and a validation report per model.
-
05 of 07
Options and the shop.
Which options combine, what each costs, and the hand-off to your cart or quote form.
You keep An options-to-SKU map, with prices worked out on the server.
-
06 of 07
Fallbacks and access.
A still image first, keyboard controls, a plain list of the options, and AR on each platform.
You keep Fallbacks that work without 3D.
-
07 of 07
Measure it.
Views, option changes, AR launches and add-to-cart from the configurator.
You keep An analytics plan and a test plan to compare with and without 3D.
Risks
The model is usually the problem, not the code
-
Heavy factory files.
A model built for manufacturing can take seconds to download and stall a phone.
Prevented in step 4 -
Download isn't memory.
A small image file can take many times its size once it's on the graphics chip.
Prevented in step 2 -
Invisible to search and screen readers.
A 3D canvas has no text unless you add it.
Prevented in step 6
40 to 120 MB → 2 to 5 MB
One developer's CAD exports per product variant across 9 client configurators, before and after compression.
Independent evidence on 3D and sales is thin: a 2022 study in the Journal of Marketing found AR helped most for less popular brands and pricier products.
Deliverables
What you keep
-
Product configurator
Options such as color, material and size that update the model live.
-
3D models and textures
Optimized for the web, so files stay small.
-
WebGL scenes
Lighting, camera and interaction, drawn with WebGL.
-
Mobile performance budget
Targets for file size and frame rate, tested on real phones.
Done means
- Every model passes the glTF validator inside its budget.
- A still image shows before any 3D loads.
- The frame rate holds on the named phone for a full session.
- Every option combination resolves to a priced SKU or quote line, and a link restores it.
- AR works on iPhone and Android at true size.
- Controls work by keyboard, with a plain list of options beside the canvas.
Sample
Performance budget
| Model download | 4 MB or less |
|---|---|
| Textures | 2048 px or less, compressed |
| Draw calls | under 100 |
| Frame rate | 30 fps held for 5 minutes on a 2022 mid-range Android phone |
| First image | before any 3D bytes load |
FAQ
Questions about 3D & WebGL
Still deciding?
Ask the people who would build it. We reply within one business day.
Yes, within a budget we set at the start. Older or low-end phones may get a simpler version of the scene, which we design on purpose.
Only if the models are heavy or the 3D blocks the page. We set size and frame budgets first, and load the 3D after the page is usable.
We can, or we can optimize models you already have. Models made for film or print are usually too heavy for the web, so expect some reduction work.
Search engines don't read a 3D canvas, so product text stays in the page and we add 3D structured data where Google supports it.
With many products, simple options and a standard shop, maybe, and we'll say so. Custom pays off for flagship products, complex rules or a quote flow.
Sometimes, mostly where buyers are unsure about size, fit or finish. Platform claims of big lifts don't publish their method, so we'd rather measure it on your products against a version without 3D.
Yes. The configurator can pass the chosen options to your cart or quote form, so what the customer sees is what they order.
Contact
Have an idea or a stuck project? Let's talk.
We reply within one business day. If we're not the right team, we'll say so on the first call.
On the first call
- Which products and options, and what files you already have.
- Where it will live: your shop, a quote form or a launch page.
- The phones your customers use.