A Guide to Importing and Exporting USD and USDZ Files in Blender

What will you learn in this guide?

Universal Scene Description (USD) is a file format for carrying scene elements and their hierarchy. Blender’s USD tools let you import a scene from another application or export supported elements from Blender as USD. This guide explains which settings matter when transferring architectural models, cameras, lights, materials, and animation data. The goal is not just to open the file, but to preserve the scene structure and visual elements as clearly as possible.

Don’t assume every detail will transfer exactly. Blender’s documentation notes that the importer doesn’t handle some USD composition features, and that material conversion may be lossy. The options in the Blender 4.0 documentation also differ from those in the current documentation. Check your workflow against the options available in the Blender version you’re using.

Requirements and getting started

The basic requirements are Blender and a USD file to transfer. USDZ is an archive format that can include USD content along with its texture dependencies. The source documentation doesn’t specify an account requirement, hardware requirements, or a single mandatory Blender version. One source covers the current Blender manual, while the other covers the Blender 4.0 manual, so keep in mind that options and data support may vary by version.

Before you start, check whether the file is USD or USDZ and whether it contains external textures. If you’re using USDZ, it’s important to choose how textures should be imported. If textures aren’t imported, material textures may not resolve in Blender. For a USD scene that references external files, also check how those file references are organized.

Step-by-step USD import

1. Choose the scope of the scene. If you only need part of the file, rather than the entire scene, use the Path Mask option to limit the import to content under a specific primitive. An option to exclude invisible elements is also documented; however, primitives with animated visibility data may still be imported despite this filter.

2. Review object types and coordinates. The documentation covers importing types such as cameras, curves, lights, materials, meshes, volumes, and point clouds; detailed support depends on the version. If the USD file uses Y-up, root objects can be automatically rotated to Blender’s Z-up coordinate system. Check the model’s orientation and hierarchy after import.

3. Preserve the hierarchy, but check the transformation. Xform elements in USD can carry transformation data and scene organization; Blender imports them as empty objects. Scope elements are also converted into empty objects to help preserve grouping. This mapping isn’t perfect: Scope itself carries no transformation data, whereas a Blender empty object does. In architectural scenes, inspect the object tree after import to check floor, block, or component groups.

4. Choose geometry and texture data. Consider the relevant import options for UV coordinates, color attributes, and mesh attributes. The documentation also describes an option to create a Subdivision Surface modifier from USD subdivision data. The option to validate malformed mesh data may slow down the import; the documentation recommends it because problems in invisible data can cause issues during editing or display.

5. Manage USDZ textures properly. Texture import options include skipping textures, packing them into the Blender file, or copying them to a selected folder. If you choose to copy them, specify the destination texture directory. The default relative directory may require the Blender file to have been saved. Also check how files with the same name are handled: whether to use the existing file or overwrite it.

6. Set realistic expectations for materials. USD Preview Surface materials can be imported. The relevant conversion option can turn them into Blender Principled BSDF node networks, but the result may be approximate because not every shader setting or type is supported. For material name conflicts, choose whether to use the existing material or create a unique material for each USD material. Compare the results, especially for glossiness, roughness, color, and transparency.

Exporting a Blender scene as USD

1. Simplify the scene and define the scope. Blender’s current documentation says visible, supported objects can be exported, with the scope limited to selected objects if needed. The current documentation lists meshes, cameras, curves, text (as a mesh), lights, hair, point clouds, metaballs, volumes, and armatures. Camera support is specified as limited to perspective cameras. Organize the scene hierarchy and select only the objects you need to export.

2. Decide whether you need animation. When animation export is enabled, the scene’s frame range can be written; when it’s disabled, only the current frame is exported. For animated exports, Blender writes the evaluated final mesh. The current documentation also describes deformation with unchanged topology and mesh animation with changing topology. Since animation can affect file size and export time, enable it only when it’s needed.

3. Create USDZ using the file extension. According to Blender’s documentation, giving the output file the .usdz extension creates a ZIP archive containing USD and its texture dependencies. However, the Blender 4.0 documentation says UDIM textures can’t be included in USDZ archives due to a limitation in the current USD library. If your workflow uses UDIMs, verify that the textures are actually present before delivering the archive.

4. Test in the target application. Don’t just reopen the exported file in Blender; inspect it in the application it’s intended for, too. Check materials, object names, coordinates, texture links, and the animation range. The Blender 4.0 documentation lists limitations involving features such as invisible objects, USD layers, and variants, while the current documentation describes a different export scope. Testing in the target application helps catch differences in versions and feature support.

Common mistakes and next steps

One of the most common risks is choosing not to import textures when importing USDZ, then discovering that material textures are missing. Another is treating USD Preview Surface conversion as a complete shader transfer. Also, don’t assume a feature or limitation described in the Blender 4.0 documentation applies in exactly the same way to the current version: the two documents differ in their descriptions of data types, animation, and export options.

For your next project, create a small test scene and import the same file with different texture and material settings. For export, start with selected objects and a single frame; if the result meets expectations, move on to a larger scene. For architecture and interior design teams, this approach helps verify geometry, textures, coordinates, and material compatibility before delivering a large model. Archviz artists using specialized data types such as animation or point clouds should also check support in the Blender version they’re using.

Sources and license

This guide is adapted from Blender’s current USD manual and the Blender 4.0 USD manual. Both sources are licensed under CC BY-SA 4.0; the content has been translated into Turkish and reorganized.