Universal Scene Description came out of film production to solve a problem other formats do not address: many people working on one enormous scene at once.
What makes it different
- Layering and composition. A scene is assembled from layers that override each other, so a lighting artist and a set dresser can work on the same shot without touching each other's files.
- References and instancing. An asset is referenced rather than copied, so updating it updates every use.
- Variants. One asset can carry multiple configurations — a car in three colours, a building in two states.
- Non-destructive overrides. Change something in a downstream layer without modifying the source.
That is a pipeline architecture, not just a file format, and it is why USD adoption tends to be a studio-level decision.
USDZ
A zipped, uncompressed USD package designed for AR delivery — specifically Apple's AR Quick Look. Single file, quick to stream, and the standard way to put a 3D model into an iOS AR experience.
Where USD is worth it
- Large scenes assembled by multiple people
- Pipelines with heavy asset reuse across shots or levels
- Anywhere the same asset appears in many contexts and must stay in sync
Where it is not
A single prop moving between two applications. The composition machinery is overhead you do not need, and GLB or FBX will be simpler.
Support
Strong and growing in film and in the major DCC tools; more variable in game engines, where it is often an import path rather than a native scene representation. Worth checking what your specific tools do with it rather than assuming.