USDZ and AR Quick Look provide a route from a product page into a 3D or augmented reality preview on supported Apple devices. For an ecommerce team, the important hand-off is the exact product state: the finish, dimensions and orientation a customer chose before opening the preview.
Discuss your product rangeTry the demos
A successful file export is only one part of that hand-off. This guide includes an original scale worksheet and an acceptance register you can use to review the result. It does not claim that a desktop browser test proves the AR experience works on a phone.
What a USDZ file is
A USDZ file is a package format. In general terms, it bundles USD scene resources into one file. Apple supports it in Quick Look workflows.
I treat it as a delivery format, not as your main 3D asset. The details can vary by exporter and by source scene. Do not assume that every export contains the same data.
USDZ is a deliverable; Quick Look is the viewing route
USDZ packages USD scene resources. Apple supports it in Quick Look workflows and provides a gallery of examples. A web page can link a supported model through an AR link, which a compatible Apple viewing route can open. Your normal inline viewer and the AR preview are separate experiences.
A GLB export is not the same file as a USDZ export. Keep the editable source, then review each delivery format. Materials and lighting can look different across viewers. Do not assume that a successful conversion preserves every feature of the source scene.
Try Apple’s Quick Look gallery on a supported device to see the viewing route. Those models are Apple’s examples, not work created for this site.
USDZ vs GLB
GLB is the binary form of glTF and suits an inline web viewer. USDZ is the package Apple supports in Quick Look workflows. Each format suits a different viewer, so the right choice depends on where your customer will look.
Many teams keep both: GLB for the inline viewer and USDZ for the Apple AR route. That means two exports to review, each with its own checks.
New to GLB? Read my guide to GLB files. To open a GLB file in a browser, try the GLB viewer.
Check the units before the device test
Use a known physical dimension as a sanity check. This worksheet compares the real product width with the exported width you report. It does not read a USDZ file, change the model or validate its metadata. The scale factor is a diagnostic hint; the actual correction depends on the source scene and exporter.
The original starting example is a fictional 700 mm wide product reported as 0.7 metres in the export. Its ratio is 1×. If the same exported number were reported in centimetres, the ratio would be 100×. That reveals a unit mismatch in the supplied measurements; it does not prove where the exporter went wrong.
Common mistakes
Watch for these before you publish:
- Wrong units. A scale error can be large. Check a known dimension against the export.
- A silent default finish. If the preview shows a default finish, say so on the page.
- No fallback. Some devices will not open AR. Those customers still need a useful view or a clear alternative.
- Untested on real devices. A desktop check does not prove the phone experience. Test each target device.
Preparing the export
Good results start before export. Fix the scale in the source scene first. Then set the orientation so the object sits on its intended surface. A model that floats or tips over will look wrong on a phone.
Name each file with the product ID, finish ID and export version. The names should match the selection the customer made. This makes the identity check in the register much quicker.
Check the materials after export, not just before. Some surfaces may look flat, dark or too glossy in a different viewer. Keep notes on what you accept and what you change.
Keep an export log too. Write down the tool, the settings and the date for each file. When a customer reports a problem, that log shows you where to start.
An AR hand-off acceptance register
Use this register for each delivery. Record what you see, and keep the record with the export.
| Check | Procedure | Record |
|---|---|---|
| Identity | Choose a named product and finish, then open its AR preview. | Product ID, finish ID and export version match the selection. |
| Dimensions | Compare a known width, height and depth with the delivered model. | Source dimensions, units and observed result. |
| Orientation | Place the object on its intended support surface. | Base contact, upright direction and placement behaviour. |
| Appearance | Inspect recognisable finishes and important details. | Reference swatch, viewer differences and accepted compromises. |
| Loading | Open the exact delivery URL on each target device. | Device, OS, browser, connection and any failure. |
| Unavailable AR | Try the journey on an unsupported device or route. | Useful inline view or clear alternative remains available. |
| Return journey | Return to the product page after viewing. | The customer's selections and next action remain clear. |
Adding AR to a product page
The steps are short, but each one needs care.
- Export the model from the source scene. Keep the source file.
- Review the export against the acceptance register.
- Link the file from the product page. Use a clear AR button. A label such as "View in AR" is clearer than a bare icon.
- Give every device a fallback. Unsupported devices should still see a useful view.
- Test the exact delivery URL on each target device.
Tell the customer what the preview shows. Name the finish. Say which dimensions are shown. A short line of text stops confusion before the preview opens.
If your store also runs a configurator, my Shopify configurator integration page covers the cart side. For how models are prepared for configurators in general, see my 3D models for product configurators page.
Keep the buying state separate
For a fixed product, one reviewed model may be enough. A configurable range needs an explicit policy: an export for every valid state, a smaller approved set of states, or another supported workflow. Decide what happens if the customer chooses a configuration without a matching AR asset. Showing a default finish without saying so would make the preview misleading.
The cart or quote still needs validated commercial data. A successful AR preview does not confirm a price, stock position or manufacturing rule. Keep the configuration reference stable across the visual preview and the order hand-off.
Record actual device checks before calling the delivery accepted. No physical device AR test is represented by the worksheet on this page. For the web asset side, use the GLB viewer and material lab. For the complete journey, see configurator development.
Where AR fits in the buying journey
An AR preview helps a customer judge size and style in their own space. It does not replace product data. Price, stock and fit rules still come from your store systems.
If you sell configurable products, the preview must match the configuration. Read the 3D product configurator guide for the wider picture.
Frequently asked questions
What is a USDZ file?
It is a package format for USD scene resources. Apple supports it in Quick Look workflows. Check each export, because the contents depend on the exporter and the source scene.
Do I need a GLB file as well?
Not always. Many teams keep both, one for an inline viewer and one for the Apple AR route. Review each file on its own.
Is a desktop test enough?
No. A desktop browser test does not prove that AR works on a phone. Record checks on each device you support.
Next step
I led development of the Praxis Digital 3D configurator platform, used by 20+ UK businesses from 2021 to 2025. If you want a second look at your AR export or acceptance checks, contact me. I can tell you what I would check first. I cannot promise how any one device will show a model.
Selling on Shopify? The Shopify 3D models and AR guide covers upload rules, theme support and device testing for product media. Android shoppers use Scene Viewer or WebXR instead, and model-viewer can offer both routes from one button.
Related reading: 3D product visualisation.
Sources and review date
References: Apple's AR Quick Look integration documentation and example gallery. The worksheet and acceptance register are original project examples. Reviewed 13 October 2026.