In my daily work, the choice between USD and USDZ isn't academic—it's a critical publishing decision that determines where and how your 3D assets will be used. Here’s my take: Use USD for professional, desktop-based pipelines in film, VFX, and game development where scene assembly and non-destructive editing are key. Use USDZ for delivering final, optimized assets to AR experiences, iOS apps, and web viewers where a single, compressed file is mandatory. This guide is for 3D artists, technical artists, and marketplace publishers who need to ship assets that actually work for their intended audience.
Key takeaways:
Universal Scene Description (USD) is fundamentally a framework for describing, assembling, and editing 3D scenes. I think of it less as a "model format" and more as a composition system. Its power lies in features like layering, where multiple artists can work on different aspects (animation, shading, layout) in separate files that combine non-destructively. In my workflow, I use USD as the master source when an asset needs to be integrated into a larger, evolving production pipeline. It's the format of choice for collaboration.
USDZ is essentially a USD archive. It takes a USD scene and its all external dependencies—textures, materials, animations—and packages them into a single, uncompressed .usdz file. This packaging is its greatest strength and constraint. It's read-only, making it perfect for secure, reliable distribution. Apple's AR Quick Look made it a de facto standard for mobile AR, but its use has expanded to web-based 3D viewers. When I need to send a client a final, self-contained asset they can drop into an app or website, USDZ is my go-to.
.usd, .usda, .usdc) with external references. USDZ is a single ZIP archive (use unzip on it to see contents).If your marketplace targets 3D generalists, VFX artists, or game developers working in software like Blender, Maya, Houdini, or NVIDIA Omniverse, you should prioritize USD publishing. These users need assets they can modify, re-shade, and integrate into layered scenes. I always ensure my USD uploads are cleanly structured, with materials using USD's Preview Surface standard and textures in logically named directories. This professional audience expects assets that play well with a pipeline.
For marketplaces focused on AR/VR developers, e-commerce (3D product views), or web3 experiences, USDZ is often the required format. Platforms like Apple's App Store and many web-based 3D viewers mandate it. When I prepare assets for these markets, I focus on ultra-clean topology, compressed textures (often 2K or 4K max), and baked PBR materials to ensure fast loading and reliable rendering on less powerful devices. The asset must work perfectly out of the box.
I use a simple flowchart: 1) Is the final destination a mobile AR experience or web viewer? → Use USDZ. 2) Will the asset be opened in a professional DCC tool for further work? → Use USD. 3) Do I need to support both? → I create and optimize a master USD asset first, then generate the USDZ from it as the final export step. This two-format approach covers the widest audience. In my work with Tripo AI, starting from a generated 3D model, I immediately focus on retopology and material cleanup—this foundational optimization is critical for both final formats.
My USD preparation starts long before export. A messy model creates problems in both formats.
/textures/) and use relative paths in the USD file. Absolute paths will break for your customers..usdc (binary, efficient) and open it in a viewer like Omniverse Viewer or Apple's usdzconvert preview to check material fidelity.I never author directly in USDZ. I always create it from a validated USD source.
usdzconvert (xcrun usdzconvert) for the most reliable results. The -l (loop) flag is essential for animated USD files.usdzconvert -validate input.usdz. This checks for compliance and flags critical issues like unsupported shaders or texture formats..usdz file directly on an iOS device via AR Quick Look (email it to yourself) and in a web viewer like <model-viewer>. Desktop previews can lie.C:\Users\You\textures\.... This will fail for everyone else. Always use relative paths.Geometry optimization is universal. I decimate where possible and use efficient UV unwrapping. For materials, I standardize on a metallic-roughness PBR workflow, as it's the best-supported across all USD and USDZ viewers. I bake complex procedural materials into texture maps (1024x1024 or 2048x2048 for USDZ). For USD, I might keep higher-res textures (4K), but I always provide the option.
Compatibility is about lowest common denominator. I test my USDZ files on an iPhone (via AR Quick Look) and a web <model-viewer> component. For USD, I test import into Blender (with USD plug-in) and Omniverse Create. A reliable asset works in all target environments. I document the tested platforms in my marketplace listing.
usdzconvert -validate, opens in iOS AR Quick Look without rendering errors.moving at the speed of creativity, achieving the depths of imagination.