Export USDZ for Apple AR Quick Look
Use USDZ when the receiving experience is Apple AR Quick Look. Pro lists USDZ export, but the file still needs checks on the supported device and delivery path. Verify physical scale, materials, and placement in the real viewing environment. A USDZ extension alone does not prove that an asset is ready for an AR launch.
Choose the right starting point
Apple documents USDZ viewing through Quick Look in supported apps and devices. Choose it when that experience is your destination, rather than sending FBX and hoping a browser converts it. Keep a separate working mesh if you also need DCC editing, because a viewing package is not a substitute for the source workflow.
Work through the handoff
Export the USDZ and preserve the source mesh. Open the file on the actual supported Apple device through the intended app or website. Place it beside a familiar physical object to inspect scale. Compare the material appearance with the approved reference under realistic lighting and revisit the export when the result differs.
Limitations and failure cases
Device, operating system, browser, and delivery configuration affect the viewing experience. A supported container does not guarantee every material or animation feature survives a particular export. No Objectify USDZ device test is reported here. Avoid promising dimensional accuracy or performance from a desktop render alone.
Acceptance checklist
Confirm scale, orientation, surface shading, and placement behavior on the target device. Test the same URL or file delivery path your audience will use. Check that the asset remains legible at intended viewing distances. Record the device and OS version, export settings, and any visual corrections before publishing the AR experience.
Evidence and review
Documentation-based guide · Documentation review ·
Documentation-based guidance, not a tested Objectify output or benchmark. Importer support and settings depend on your tool version; validate your actual exported file before production use.