A sofa that opens on a phone
Most shoppers meet a configurator on their phone, often on a weak connection. Here's how we keep detailed 3D products fast enough to use there.
A 3D model made for a render can be hundreds of megabytes. A shopper on a phone, on a train, will give a product page a few seconds. Those two facts have to meet somewhere, and that somewhere is our job.
Compress on the way in
When you upload assets, Amaspace asks how to compress them, per file or in bulk, and textures move to formats built for the web. We use KTX2 for textures where devices support it, and we fixed a bug last year where some assets fell back to WebP when they shouldn't have.
The goal isn't the smallest possible file. It's the smallest file that still looks right at the size a shopper actually sees it.
Load what the device can handle
Not every phone needs the same model. We load the product at a level of detail that suits the device and adjust texture quality to the connection. A new phone on Wi-Fi gets the full detail; an older phone on mobile data gets a lighter version that still turns smoothly.
Convert in batches
Large catalogues don't get converted one model at a time. Batch conversion takes a set of models through the same settings together, so a whole range ends up equally light, not just the products someone remembered to optimise.
Where it stops
Compression has limits. A product with very fine detail, such as intricate engraving or a dense fabric weave, will always be heavier than a plain one. When a model is too heavy to work well on a phone, we'd rather tell you and simplify it with you than ship something that stutters.
Next step
Open any demo on our Showcases page on your phone, on mobile data. That's the experience we tune for.
