Reference Formats
USDZ
An uncompressed-zip packaging of USD created by Apple and Pixar for augmented reality, bundling geometry, materials, and animation into one file that iOS can preview natively without a separate app.
Extension
.usdz
Full name
Universal Scene Description Zip
Introduced
Announced June 4, 2018 at Apple's WWDC, alongside ARKit 2 and AR Quick Look
Vendor
Pixar Animation Studios and Apple
What is inside the container
USDZ is a constrained, single-file profile of USD specifically designed for AR delivery: it packages the USD scene description along with all its referenced textures and audio into one uncompressed zip archive (uncompressed deliberately, so iOS can memory-map and read assets directly without unzipping first). Apple's specification restricts USDZ to features that render predictably across devices, which is a narrower feature set than full USD supports — it's meant purely as a delivery/viewing package, not an editing format.
How to open it
For archives
USDZ should be treated in a DAM as an AR-delivery derivative, not a source master — Apple's specification intentionally constrains it to a predictable, renderable subset of full USD, so the richer authoring file (a full .usd/.usda scene, or the original DCC source) should remain the editable archival master with USDZ generated specifically for iOS AR Quick Look delivery. Product-visualization and e-commerce DAMs targeting Apple's AR ecosystem should plan to generate both a GLB (for Android/web) and a USDZ (for iOS) from the same source model, since neither platform's native AR viewer accepts the other's preferred format. As with other 3D formats, most DAMs cannot preview USDZ inline without an embedded viewer, though macOS Quick Look support at least makes desktop-side QA straightforward for Mac-based teams.
Apple announced USDZ at its Worldwide Developers Conference on June 4, 2018, developed jointly with Pixar and introduced alongside ARKit 2 and a new system-wide AR Quick Look feature. The goal was specific and practical: give iOS a single, self-contained 3D file format that Safari, Messages, Mail, and Files could all open directly into an augmented-reality preview without requiring a dedicated app, something no existing 3D format was optimized to do at the time.
USDZ achieves that by packaging USD scene data, textures, and audio into a single uncompressed zip archive — uncompressed specifically so iOS could read the contents directly via memory-mapping rather than needing to unzip the file first, keeping AR Quick Look responsive. At launch, Apple also announced that Adobe, Autodesk, and Sketchfab would add USDZ creation or export support, positioning it immediately as a cross-tool AR delivery target rather than an Apple-only curiosity.
For a DAM serving retail, product visualization, or e-commerce use cases, USDZ is now a required delivery derivative wherever "View in AR" needs to work on an iPhone or iPad — Apple’s ecosystem specifically expects it, the way Android/web AR expects GLB. A mature product-asset DAM pipeline typically generates both from the same source model automatically, since USDZ and GLB aren’t interchangeable and neither platform’s native AR flow will substitute the other.
Frequently asked
Why does an e-commerce DAM need to generate USDZ separately from GLB?
Apple's AR Quick Look on iOS/iPadOS specifically expects USDZ, while Android and most web AR viewers expect GLB — a DAM serving both platforms' 'View in AR' features needs to generate and manage both derivatives from the same source model.
Can USDZ be edited directly, or is it only for viewing?
It's designed as a delivery/viewing package — Apple's specification constrains USDZ to a predictable, renderable subset of full USD, so serious editing should happen in the source USD scene or original DCC file, with USDZ regenerated afterward.
Why is USDZ's zip archive uncompressed rather than compressed like a normal zip?
Apple deliberately left it uncompressed so iOS can memory-map and read the contents directly without first unzipping the file, keeping AR Quick Look's load time fast — this is a specific engineering choice, not an oversight.
What relationship does USDZ have to the full USD format?
USDZ is a constrained, single-file packaging profile of USD (Pixar's Universal Scene Description) created by Apple specifically for AR delivery — it's a narrower, delivery-focused subset rather than a separate format from scratch.
Can a Mac-based DAM team preview USDZ without any special software?
Yes — macOS Quick Look (pressing spacebar on a selected file in Finder) renders USDZ natively, making desktop-side QA straightforward for Mac users even without opening a dedicated 3D application.
Does USDZ support animation, or only static models?
It supports animation, including simple looping animations suitable for AR presentation, though the feature set is deliberately narrower than what full USD or FBX can carry, focused on what renders predictably in AR Quick Look.
Which major software vendors added USDZ support at launch?
Apple announced at the June 2018 WWDC that Adobe, Autodesk, and Sketchfab would add USDZ creation or conversion support, positioning it as a cross-vendor AR delivery target from the start rather than an Apple-only format.
Should a DAM archive USDZ long-term, or regenerate it on demand?
Regenerating on demand from a richer source master is generally more resilient, since USDZ's constrained AR-focused feature set makes it a lossy derivative relative to a full USD scene or original authoring file.
Sources
- Apple announced the USDZ file format at WWDC on June 4, 2018, developed jointly with Pixar for augmented reality checked 2026-08-07 — MacRumors — Apple Announces New USDZ Augmented Reality File Format Coming in iOS 12
- USDZ supports sharing AR objects in apps like Messages, Safari, and Mail, with Adobe, Autodesk, and Sketchfab announced as supporting the format checked 2026-08-07 — Apple Newsroom — Apple unveils ARKit 2