Pipeline & formats
iPhone scan to GLB
Capture on a phone, ship to the web and to AR — and meet the USDZ tax.
What this is
Walk a phone scan from capture through cleanup, decimation, baking and compression to a file a product page can load. The mesh on screen is rebuilt at whatever triangle budget the pipeline lands on.
The uncomfortable finding is the cross-target table. iOS AR Quick Look wants USDZ, and USDZ supports neither Draco geometry compression nor KTX2 textures — so the identical asset ships four to six times larger for AR than for the web. There is no single file that serves both. You build two, and you budget for two.
Things worth trying
- Set the target to iOS AR Quick Look and watch Draco and KTX2 grey out
- Compare the same asset across all four targets in the panel
- Turn on the wireframe and take decimation to 5% — the silhouette goes before the surface
- Switch to a photogrammetry-only device and lose metric scale entirely
More in this group
Pipeline & formats
Bring us the product you were told could not be configured.
Tell us the option count, the CAD you already have and the frame budget you need to hit. An engineer reads it and replies with a straight answer — including when the answer is that good photography would serve you better.
We reply to every enquiry within one business day, in your timezone — with a frame budget, not a brochure.