Reference Formats
USD
An open-source framework and file format from Pixar for composing, layering, and non-destructively editing extremely large, complex 3D scenes across many collaborating tools and artists at once.
Extension
.usd
Full name
Universal Scene Description
Introduced
Developed internally at Pixar over roughly two decades; open-sourced July 26, 2016
Vendor
Pixar Animation Studios
What is inside the container
USD is less a single file format than a scene-composition system: its core feature is 'composition arcs' that let many separate USD layers — geometry from one department, lighting from another, variants for different product configurations — be non-destructively combined, overridden, and referenced into one final scene without any single artist's file being directly edited by others. It ships in three interchangeable encodings: .usda (human-readable ASCII text), .usdc (efficient binary "crate" format), and .usd (either, auto-detected) — plus .usdz for the AR-delivery packaging. This layering/composition model is fundamentally different from, and more powerful than, simply importing/exporting geometry the way FBX or OBJ do.
How to open it
For archives
USD is increasingly the preferred long-term interchange master for complex, multi-department 3D production (VFX, animation, and large-scale product configuration), and a DAM serving those pipelines should treat the full USD composition — not a single flattened export — as the archival unit, since USD's whole value is in preserving the layered, non-destructive editing structure rather than a baked-down scene. Because USD ships in both human-readable (.usda) and binary (.usdc) encodings, a DAM should record which was used and can favor .usda for diffable, text-based version control workflows where that matters. As with other 3D formats, native visual preview requires a dedicated viewer (usdview or an Omniverse-based tool); USD's composition-arc complexity in particular makes a simple thumbnail an incomplete representation of what the asset actually contains.
USD grew out of nearly two decades of internal tooling at Pixar, addressing scene-description problems the studio had wrestled with as far back as A Bug’s Life in the late 1990s. The complexity crisis came to a head after 2012’s Brave, when Pixar concluded that the accumulated patchwork of internal formats and APIs for composing scenes across departments — modeling, layout, animation, lighting, effects — had become unsustainable, and set out to build one unified system.
Pixar announced its intent to open-source USD in August 2015 and delivered on that promise on July 26, 2016, releasing the full toolset publicly. USD’s defining technical idea is ‘composition’ — the ability to non-destructively layer and override many separate USD files into one final scene, so a lighting artist’s changes, an animator’s changes, and a modeler’s changes can all exist as separate, referenceable layers rather than requiring anyone to directly edit someone else’s file. That capability has made USD the backbone of tools like NVIDIA Omniverse and a rapidly growing standard across VFX, animation, and industrial digital-twin pipelines well beyond Pixar’s own use.
For a DAM, USD represents a step up in complexity from any format discussed so far: because a "USD asset" is often really a composed set of layered files referencing one another, DAM management needs to track the whole dependency graph, not just a single file, to preserve what the scene actually is. This makes USD most relevant to large studios and industrial/product-configuration teams managing complex, multi-contributor 3D scenes, with USDZ serving as its simpler, flattened single-file cousin for AR delivery to end users.
Frequently asked
What makes USD fundamentally different from a format like FBX or OBJ?
USD is a scene-composition system, not just a geometry container — its core feature lets many separate layers (geometry, lighting, animation, variants) be non-destructively combined and overridden into one final scene, rather than requiring a flattened single-file export/import.
What's the difference between .usd, .usda, and .usdc file extensions?
.usda is the human-readable ASCII text encoding, .usdc is the efficient binary 'crate' encoding, and .usd is a generic extension that auto-detects either — a DAM should record which encoding is used since it affects whether the file is diffable in text-based version control.
Why is a single USD asset in a DAM sometimes actually a set of many linked files?
Because USD's composition model lets a final scene reference multiple separate USD layers (from different departments or contributors), a DAM needs to track the full dependency graph of referenced files, not just one file, to preserve what the asset actually represents.
How does USD relate to USDZ?
USDZ is a constrained, single-file zip packaging of USD created specifically for AR delivery on Apple platforms — it's a simplified, flattened derivative meant for viewing, while full USD supports the richer, layered composition model used in production.
Who open-sourced USD, and when?
Pixar Animation Studios announced its intent in August 2015 and completed the open-source release on July 26, 2016, after developing the underlying technology internally for roughly two decades.
What industries beyond film/animation are adopting USD in DAM pipelines?
Industrial digital-twin and product-configuration workflows increasingly use USD, particularly through platforms like NVIDIA Omniverse, extending it well beyond its original VFX/animation origin at Pixar.
Can a DAM preview a USD scene's full composed result, or just individual layers?
A proper preview requires a USD-aware viewer like Pixar's usdview or an Omniverse-based tool that resolves the composition arcs across all referenced layers — viewing a single layer in isolation won't show the actual final composed scene.
Is USD backward compatible across different versions of the toolset?
Pixar maintains active compatibility efforts as USD evolves, but because it's a fast-moving, actively developed open-source project, a DAM archiving USD assets should record the USD toolset version used to author them for troubleshooting future compatibility.
Sources
- Pixar Animation Studios announced the official open source release of Universal Scene Description on July 26, 2016 checked 2026-08-07 — Computer Graphics World — Pixar Animation Studios Open Sources Universal Scene Description
- Pixar announced its intent to open-source USD on August 10, 2015, ahead of the 2016 release checked 2026-08-07 — Animation World Network — Pixar's Universal Scene Description to be Open-Sourced