Importing and Exporting USD in Blender: A Step-by-Step Guide for Architectural Scenes

What will you learn in this guide?

Universal Scene Description (USD) is a file format used to transfer scene data between different 3D applications. Blender’s official manual explains that USD files can organize information such as geometry, lights, cameras, and transform hierarchies into elements called prims. Blender can import this structure by converting it into its own object hierarchy; when exporting, it writes supported, visible scene elements to USD.

This guide explains how to assess the key options when importing a USD or USDZ file into Blender, how to prepare a Blender scene for USD export, and what information may be lost during transfer. For anyone working with architectural models, interior scenes, and visualization assets, geometry, coordinate orientation, materials, and texture checks are especially important.

Requirements and pre-transfer checks

The basic requirements are Blender and the USD or USDZ file you want to transfer. The official manual does not specify a particular Blender version, user account, or special hardware requirement, so no version number or system requirement should be assumed here. Check the options available in your version of Blender against that version’s documentation.

Before transferring, determine whether the file is a standalone USD scene or a USDZ archive that may also contain textures. If the source scene uses layers or references to other files, do not assume these will be fully preserved in Blender. Blender’s importers and exporters do not fully handle these USD composition features.

Also clarify which elements you need from the scene: geometry, cameras, lights, curves, volumes, point clouds, or animation. Choosing options to match your needs makes it easier to control the transfer without bringing unnecessary data into the scene.

Importing a USD file into Blender

1. Start the USD import. Use the USD option in Blender’s file import workflow and select the source file. USD prims are converted into Blender objects. Xform prims come in as empty objects that carry transform information and hierarchy. Scope groups with no transform information are also represented as empty objects at the origin to help preserve the scene structure.

2. Set the scene scope and coordinate scale. Use Path Mask to import only a specific branch. Consider Visible Primitives Only to exclude invisible prims; this option applies to non-animated visibility attributes. Set Frame Range updates the scene’s start and end frames to match the range in the USD stage. Apply Unit Conversion Scale and Scale control how objects are scaled. If the USD file is Y-up, Blender automatically rotates the root objects to match its Z-up orientation.

3. Choose the object and geometry data you need. Import can include types such as cameras, curves, lights, materials, meshes, volumes, point clouds, and basic shapes. Check the relevant options for mesh UV coordinates, color attributes, and mesh attributes. Subdivision Surface modifiers can be created based on USD subdivision data. Validate Meshes is useful when malformed data is a concern: the manual notes that this check can slow down the import, but that invalid data may cause problems during editing or display.

4. Review materials and USDZ textures. USD Preview Surface materials can be imported. When Import USD Preview is enabled, these materials can be converted into Principled BSDF node networks; the conversion may be approximate because it may not cover every shader setting. For USDZ files, you can choose not to import textures, pack them into the Blender file, or copy them to a specified folder. Skipping textures may leave material textures unavailable in Blender. The default relative folder path for the copy option is //textures, and the Blender file must already be saved for the relative path to resolve.

5. Check the imported result. Review the object hierarchy, scale, material names, UVs, and texture connections. USD transform animation can be represented with a Transform Cache constraint; animated mesh, curve, and point-cloud geometry can be represented with a Mesh Sequence Cache modifier. However, file sequences made up of separate USD files for each frame are not supported.

Exporting a Blender scene as USD

1. Simplify the scene for transfer. Blender’s exporter writes visible, supported objects; you can optionally limit the export to selected objects. Supported types include meshes, perspective cameras, curves, text (as a mesh), lights, hair (as curves, main strands only), point clouds, metaballs, volumes, and armatures. If a project contains an object type not on this list, do not assume it will be represented the same way in the USD file.

2. Set the selection and frame range. Use Selection Only to export selected objects only. When Animation is enabled, the entire scene frame range is written; when disabled, only the current frame is exported. For animated meshes, the evaluated final mesh is written to USD. This can include both deformations that do not change topology and animated meshes whose topology can change.

3. Save the file and verify the result in another application. Setting the output extension to .usdz creates a USDZ archive; the package can contain USD data and texture file dependencies. Keep in mind that Blender’s exporter does not export invisible objects, USD layers, or variants. Checking that the intended scene structure and materials open as expected in the target application is part of verifying the transfer.

Common issues and next steps

If the material appearance changes: Blender’s USD Preview Surface conversion may not cover every setting. Exported materials may also be simplified versions limited to Blender’s viewport color, metallic, and roughness information. You may need to adjust materials again in the target application.

If textures are missing: Check how textures are handled when importing the USDZ file. Use the pack or copy option, and make sure the Blender file is saved before copying textures.

If the hierarchy or animation differs from what you expected: Remember that layers and references are not fully handled during import, and USD file sequences are not supported. Invisible objects, layers, and variants are also not preserved on export.

In architecture, interior design, and archviz workflows, USD can be used to transfer scene geometry and data such as cameras and lights between applications. Teams that plan to use it should first identify which object types and material information need to be transferred in both directions. After transfer, check scale, coordinate orientation, hierarchy, and textures. The cited manual provides no specific information about large-scene performance or licensing terms, so these points should be assessed separately based on the software and files in use.

Source and license

This guide has been adapted into Turkish using Blender’s USD import and export documentation. The source document is published under the CC BY-SA 4.0 license: https://docs.blender.org/manual/en/latest/files/import_export/usd.html