Image generated with AI

What Is OpenUSD? Layers, References and Variants

Diego Cortés

Diego Cortés

Author

11 August, 2026

A USD file can open a whole scene while barely containing geometry: it stores the instructions to compose it from other layers. That is the short answer to what is OpenUSD, and the reason it changes how you work.

What Is OpenUSD and What It Is Not

OpenUSD encodes hierarchical, static and time-sampled data so it can be exchanged between digital content creation applications. Its composition operators (file and asset references, variants, inherits) let you bring many assets into one scenegraph and spread overrides without touching the originals.

It carries geometry, materials and shading, lights, render data, linear-blend skinning, blend shapes and rigid body physics: almost everything you need to describe a scene.

.usda, .usdc and .usd

There are three native extensions: .usda is UTF-8 text, easy to read by hand; .usdc is binary Crate, random access, the one that survives production; .usd can be either. On top of that, plugins read and write Alembic and read MaterialX.

USD Is Not Just Another File Format

FBX, OBJ and Alembic exchange flat or cached geometry: they arrive, they get imported, and they stay put. USD is built to compose a scene description spread across many files and formats and give you a single hierarchical view. The scene is not in a file: it is computed.

Stage, Prim and Layer: The Minimum Vocabulary

The stage is the composed scene you open. Each entity inside it (mesh, light, camera, group) is a prim, organized hierarchically. Each layer is a file that contributes opinions about those prims, and the layer stack is the pile of layers that talk about the same prim.

No layer destroys another: they all have opinions and the result is computed at composition time. Think of adjustment layers stacked on the same photo, which stays intact underneath even if you pushed the contrast up top. In Maya, learn early to tell file-backed layers, saved to disk, from anonymous ones, which are not.

Composition: Why One Layer Wins (LIVERPS)

Composition assembles the layers through composition arcs and produces an ordered list of nodes, from the strongest opinion to the weakest: the prim index.

The order is LIVERPS: Local, which includes sublayers, wins; then Inherits, VariantSets, References, Payloads and finally Specializes. What you author in a sublayer is stronger than a variant's opinion, and what you write on the prim beats any variant. That is why the official advice is to prefer a sublayer over a reference when it does the job: it is simpler and sits higher in strength.

Composition is also encapsulated: you cannot remove a reference that was introduced inside another reference, except by selecting a variant. And when a change does not show up, there is almost always a stronger local opinion covering the reference: check which layer opines on that property before rewriting the asset.

References and Payloads: Reuse Without Copying

A reference brings another asset in as part of the scene: the asset lives in one place, scenes reuse it, and overrides are authored on the referencing layer. Declare defaultPrim, the metadata that names the root prim to reference; without it, whoever references has to point at the prim path by hand.

A payload packages heavy assets and loads them on demand, as the OpenUSD performance guide recommends. Do not confuse it with a simulation cache: a payload points at composable content, a cache is geometry already computed frame by frame.

Instancing

Many copies of a prim share one composed representation in the stage. That is the real reason USD holds up with huge scenes.

Variants: One Asset, Several Versions

A variantSet groups versions of a prim and lets you pick one: LODs, material finishes, set seasons or product configurations. Change the selection and the scene recomposes without replacing files. The classic trap is leaving a local opinion on the property the variant drives: that opinion wins and the variant never shows. Apple ships USDZ models with variants so people can pick a version in Quick Look.

Schemas, Primvars and Hydra

Schemas are the typing of the data: UsdGeomMesh for meshes, the UsdLux family for lights, UsdVol for volumes, UsdPreviewSurface for materials. Typing stops every application from guessing what a prim holds. Primvars are per-element attributes with a declared interpolation (colors, UVs, velocities) and they can be animated. Hydra is the rendering architecture of USD, built for very large scenes and for incremental change processing: it drives the viewers and feeds the renderers that read the stage.

USDZ: The Package for Web and AR

USDZ is a zip package with no compression and no encryption, with the MIME type registered at IANA as model/vnd.usdz+zip. The current spec is 1.3, which adds AVIF image support. A package can contain other packages, and files inside can be referenced from outside.

Safari, Messages, Mail, News and Notes display USDZ on iPhone, iPad and Vision Pro, and Safari on visionOS 26 supports the HTML <model> element. In Blender, exporting to .usdz produces a zip with the USD and its textures.

USD in Blender 5.3: What It Does and What It Does Not

Importing

The importer turns prims into an object hierarchy: Xform becomes an empty, Scope becomes an empty at the global origin (Blender has no scope equivalent) and UsdGeomPointInstancer becomes a point cloud with Geometry Nodes and Instance on Points. Transform animation comes in as a Transform Cache constraint and geometry animation as a Mesh Sequence Cache modifier; animated primvars too. What it does not support is USD file sequences, one file per frame.

The Limitation Worth Saying Out Loud

The importer and exporter still do not handle some USD composition concepts, such as layers and references: a file that depends on references can arrive incomplete. If you need reliability, export flat USD or caches.

Options That Do Exist

On import you get Path Mask, Only Visible Prims, Only Defined Prims, Set Frame Range, Create Collection, Relative Paths, Apply Unit Scale Conversion (metersPerUnit), Scale, Light Intensity Scale, Custom Properties and Dome Light, which turns the first UsdLuxDomeLight into the world background.

Exporting

On the other side: Top Level Primitive, animation of the full range or the current frame only, incremental save, transform operators, Convert Orientation (Blender works Y forward, Z up), Meters per Unit, Rename UV Maps to the standard st name and Triangulate. Shape Keys go out as USD blend shapes, absolute ones are not supported; skeletons export only deform bones and their parents; materials go through USD Preview Surface or MaterialX networks; hair exports as primary strand curves without color, and cameras only as perspective.

What Is New in 5.3

Blender 5.3 adds a USD Collection Importer: the import is added to a collection and configured in its properties, with settings stored in the .blend, and it only covers the USD format for now. It also adds Gaussian Splats import from USD, using the UsdVolParticleField3DGaussianSplat schema. The rest is in the Blender 5.3 release notes.

OpenUSD in Maya, Houdini and Unreal

Maya works with USD for Maya and its USD Layer Editor: you tell file-backed and anonymous layers apart, set a target layer for everything you edit, can lock and mute layers (a muted layer takes part in neither value resolution nor composition) and save the stage with its pending edits.

Houdini integrates it in Solaris, where LOP nodes generate and modify USD and Karma is its USD-based renderer; the Component Builder assembles a model from SOPs with materials, variants, payloads and layers. Houdini is thought in nodes.

Unreal documents its USD support as a Beta import and export feature: it works, but know that before you build critical dependencies on it.

When USD Is the Right Tool (and When It Is Not)

Yes, when a pipeline spans several DCCs, when an asset is reused across many scenes, when work is split by department, when scenes are large and need on-demand loading, or when you need web and AR delivery through USDZ.

And no, or not yet, when you just want to move a static mesh between two applications: glTF does that better. Nor when all you need is a heavy simulation cache, because Alembic is still the answer. And Blender, Maya and Houdini do not treat USD the same way.

Conclusion

USD clicks the day you stop asking it to export and start thinking in layers, references and overrides. It does not store the scene: it stores the instructions to compose it. To see it in motion, the platform has curated tutorials: USD vs Alembic when bringing Maya animation into Blender, Arnold with USD and a first day in Houdini. To organize the scene in the meantime, collections and the Outliner.