In brief
- Blender’s USD importer does not process some USD composition features, such as layers and references.
- Blender’s USD exporter can export visible, supported objects; layers and variants cannot be exported.
- Unreal Engine can display and edit USD data in the scene hierarchy with USD Stage, without converting it to native assets.
- Epic Games describes USD support in Unreal Engine as beta and recommends caution before deployment.
What will you learn in this guide?
USD (Universal Scene Description) is an interchange format for transferring and editing scene data created in different 3D applications. In this guide, you’ll learn how to evaluate Blender’s USD import and export options, open a USD file in Unreal Engine with USD Stage, and check which data needs attention during transfer. MDL material export and USD Collections features in Omniverse Kit-based applications are also covered as separate, optional workflows.
The goal is not to automatically achieve the same look in every application, but to transfer supported scene data in a controlled way and verify it in the target application. Results should be reviewed especially for materials, USDZ textures, animation, and composition features.
Requirements and preparation
The basic workflow requires Blender and Unreal Editor. On the Unreal Engine side, you’ll need to enable the USD Importer plugin. Since the source documentation does not specify a Blender or Unreal Engine version number, this guide does not list one for version compatibility. The sources also do not explain account requirements.
To try MDL export in Omniverse, you need the USD Material MDL Export extension and a Kit-based application. The USD Collections extensions described in the documentation can be used to work with collections, but they are in preview/beta and have limitations.
Before transferring, identify which objects and data you need. Blender’s exporter exports visible, supported objects, and you can limit the export to selected objects. If multiple people will work on the same USD project in Unreal Engine, everyone must access the files through the same file path. Epic Games recommends keeping target USD files in the project folder and managing them with source control.
1. Prepare the USD scene in Blender
Organize the scene hierarchy and the elements to be transferred in Blender. Blender’s USD exporter can export data such as meshes, cameras, curves, text, lights, hair, point clouds, volumes, and armatures. Text is written as a mesh, while hair export is limited to the main hair strands. Perspective cameras are supported, but orthographic cameras are not.
If you need animation, review the result before exporting. According to Blender’s documentation, the evaluated final mesh is written to USD for animated scenes. Supported export types include static meshes, meshes deformed without changes to their topology, and animated meshes whose topology can change over time. This does not mean animation will look the same in every application; it should also be checked in the target application.
Blender’s USD importer converts scene data into a hierarchy of Blender objects. It can import types such as meshes, cameras, lights, curves, materials, point clouds, basic shapes, and volumes. However, the importer does not yet process some USD composition features, such as layers and references. So don’t assume the source hierarchy will be preserved in its entirety in a complex scene.
2. Export a USD or USDZ file
Export a standard USD file from Blender, or set the output file extension to .usdz to prepare a USDZ archive. Blender’s documentation describes a USDZ package as a ZIP archive containing a USD file and its texture dependencies. The exporter does not export some features, such as layers, variants, and invisible objects, so set expectations for transferring this kind of data in advance.
When importing a USDZ file into Blender, choose an appropriate option for textures. None does not import textures, which can leave material textures unresolved. Packed embeds textures in the Blender file, while Copy copies files to the specified folder. According to Blender’s documentation, if you use a relative folder path, the file must have been saved beforehand.
Import options include controls for importing only a specific part of the scene, excluding invisible elements, creating a new collection, and converting units. The mesh validation option can slow down the transfer; the documentation recommends using it because data errors might not be visible. Choose options according to your needs, and make your first attempt on a copy rather than the original project.
3. Open USD Stage in Unreal Engine
In Unreal Editor, enable the USD Importer plugin from the Plugins menu and restart the editor. The USD Stage option then appears in the Level Editor’s Window > Virtual Production menu. The USD Stage Actor acts as a container for the contents of the opened USD file within the Level.
Epic Games’ documentation lists .usd, .usda, .usdc, and .usdz among the supported formats. The USD Stage workflow keeps USD data in its own scene structure instead of directly converting it into Unreal Engine’s native Static Mesh and Material assets. This approach lets you view the scene hierarchy and edit some attributes non-destructively; changes to the source USD file can also be tracked in the workflow.
The documentation offers several options when you need to convert content into Unreal Engine assets. File > Import Into Level or Action > Import in the USD Stage Editor can import both assets and Actors. The Add/Import button in the Content Browser, or dragging and dropping a file into the Content Browser, imports assets only. Once the import via the Stage Editor is complete, the USD elements in the scene are replaced with new Actors.
For a file containing animation, you can access animation data through the Level Sequence created with USD Stage. Also, if the scene looks dark when you build static lighting, keep in mind that Unreal Engine does not automatically generate lightmaps for assets loaded from USD Stage. Test the lighting result and scene appearance separately in your target workflow.
4. Optional: MDL material and collections workflows
To export a USD material in MDL format in Omniverse Kit-based applications, first enable the USD Material MDL Export extension in Extension Manager. The material must be assigned to geometry to be fully usable in renders and ready for export. After selecting a single Material Prim, you can choose the destination file with Export to MDL from the context menu.
If source files exported with the material already exist under the same names, they are not overwritten; new filenames are created. Also, general parameters connected to the Material Prim are not yet visible in MDL. Keep these limitations in mind before reimporting and applying the material.
The USD Collections extensions let you inspect collection contents in a tree view and drag and drop prims into collections. Expansion rules and the root prim can be set in the Property Panel. However, the documentation notes that these extensions are in preview/beta, have known limitations, and may change.
Common mistakes and next steps
Assuming the entire scene structure will be preserved: Blender’s importer does not process some USD composition features, such as layers and references. Blender’s exporter also does not export features such as layers and variants. Assess the limitations of each direction separately.
Taking the material appearance for granted: Blender can use USD Preview Surface values or approximate these materials with Principled BSDF nodes. Blender’s documentation notes that the conversion can be lossy; check the appearance in the target application.
Overlooking USDZ textures: How textures are imported depends on the selected option. For project portability, test the results of
PackedandCopywith a suitable sample file.Assuming USD Stage is ready for deployment: Epic Games describes USD support in Unreal Engine as beta and recommends caution in deployment. In multi-user editing, deleting a prim cannot be undone.
First, check geometry, textures, materials, animation, and hierarchy separately in a nonessential copy of the scene. Then decide how the team will share file paths and whether content will remain in USD Stage or be converted into Unreal Engine assets. If the project is moving to real-time presentation or production, include the beta warning and lighting requirements in your workflow testing.
Sources and license
The Blender Manual’s USD import and export guide is published under the CC BY-SA 4.0 license; this content has been adapted and summarized in Turkish. NVIDIA Omniverse’s USD Material MDL Export and USD Collections documentation, along with Epic Games’ Unreal Engine USD documentation, were used to explain the relevant features and limitations.
Sources
3 sourcesSource texts are not republished; short quotes are marked, everything else is our own summary and commentary.
For architecture and visualization teams in Turkey, USD offers a way to evaluate scenes created in different software through a shared structure. When moving from Blender to Unreal Engine, USD Stage’s ability to keep the hierarchy visible and make some edits non-destructively can be useful in iterative presentation workflows.
However, you shouldn’t assume that every material and scene feature will transfer exactly. Offices should run a small compatibility test with their own files, manage textures carefully, and check the need for lightmaps on the Unreal side. Since USD Stage is marked as beta, workflow stability should also be verified before deployment or delivery, alongside hardware and licensing plans.
Frequently asked questions
How do you transfer a USD scene from Blender to Unreal Engine?
Export the scene from Blender as USD, enable the USD Importer plugin in Unreal Editor, and open the file in the USD Stage workflow. You can also import the content as Unreal Engine assets if needed.
Can Blender import textures from USDZ files?
Yes. Blender offers options to skip textures, embed them in the Blender file, or copy them to a specified folder.
Can USD Stage be used in production in Unreal Engine?
Epic Games’ documentation describes USD support as a beta feature and recommends caution in deployment. It should therefore be tested in the target workflow.



