How to Move Blender Assets to Unreal Engine with blender-unreal-asset-bridge

What blender-unreal-asset-bridge does

blender-unreal-asset-bridge is a Blender add-on that streamlines the transfer of complete scenes into Unreal Engine. Instead of exporting assets individually and rebuilding settings by hand, you can mark assets in Blender, run one batch export, and produce a folder tree designed for the Unreal Engine pipeline.

The add-on can export static meshes, skeletal meshes, Action animations, NLA tracks, Alembic caches, splines, cameras, collisions, sockets, and Sequencer content. It also generates a Python import script that reconstructs the exported structure in the Unreal Engine Content Browser.

The project targets Windows x64, Blender 4.2 or later, and Unreal Engine 4 or 5. Generated import scripts require Unreal Engine 4.26 or later.

Key features

• Batch scene export: Export an entire environment, character set, or cinematic scene in one operation.
• Mesh and animation support: Export static meshes, skeletal meshes, selected Actions, NLA tracks, morph targets, and Alembic caches.
• Blender-authored collisions and sockets: Create box, convex, sphere, or capsule collision shapes and sockets before export.
• Pre-export validation: The error checker identifies naming, scale, material, and animation problems and can fix some issues with one click.
• Generated Unreal import scripts: Rebuild the Content Browser structure from a generated Python script.
• Cinematic transfer: Export cameras and Sequencer content as a Level Sequence with cuts, aspect ratio, focal distance, and lens shift intact.
• Clipboard workflows: Copy cameras, splines, and sockets for direct pasting into Unreal Engine.
• AI assistance: Connect an OpenAI-compatible provider and model so routine naming, checking, and export tasks can be handled from a conversation.

Install the Blender add-on

1. Download the Windows release

Download the release ZIP from the project releases page. The bundle is intended for Windows x64 and Blender 4.2 or later.

2. Unblock the ZIP file

Windows may mark downloaded ZIP files as blocked. Open PowerShell and run the following command, adjusting the path if the file is stored somewhere else:

powershell Unblock-File -Path "$HOME\Downloads\blender-unreal-asset-bridge.zip"

3. Install from Blender preferences

1. Open Blender.
2. Navigate to Edit > Preferences > Get Extensions.
3. Open the extensions menu and choose Install from Disk.
4. Select the downloaded ZIP file.
5. Enable blender-unreal-asset-bridge.

After enabling the add-on, open the Blender 3D Viewport, press N to display the sidebar, and select the blender-unreal-asset-bridge panel.

4. Configure the assistant connection

Choose an AI provider, enter the connection details, and select a model. The configuration panel holds the provider endpoint and key. You can send messages inside Blender or select Open Studio Window.

Keep Blender running while using the Studio Window or an external client. Both workflows communicate with the active Blender session.

Prepare a scene for export

Organize the Blender scene into the assets and collections you want to send to Unreal Engine. This may include environment props, character meshes, animation Actions, collision objects, sockets, cameras, and cinematic data.

Before exporting, decide which options match the destination project:

• Set the target engine to Unreal Engine 5, or select Unreal Engine 4 when required. Unreal Engine 4.26 and later is supported for generated import scripts.
• Use FBX for the standard mesh workflow, or choose Alembic for caches and simulation-driven meshes.
• Leave Unit scale set to Auto to convert Blender units to Unreal Engine scale.
• Leave Axis transform set to Auto to transform rotations, pivots, and other transforms for Unreal Engine conventions.
• Choose Actions for individual animation exports, or switch to NLA when one mixed track should be exported.
• Enable the Error checker and Import script options unless your workflow specifically requires otherwise.

Run a basic batch export

Export an environment pack

1. Mark or select the collection containing the environment props.
2. Review the unit scale, axis transform, naming, collision, and socket settings.
3. Run the error checker before exporting.
4. Resolve the reported issues or use an available one-click fix.
5. Start the batch export.
6. Open the generated output folder and verify that the assets are arranged in the Unreal-ready folder tree.

The export writes the scene assets to disk in a structure intended for Unreal Engine. Static meshes can include their Blender-authored collisions and sockets, avoiding a second collision-building pass in the engine.

Export a character and animations

1. Select the skeletal mesh and the Actions you want to export.
2. Choose Actions for separate selected animations, or select NLA for a single mixed animation track.
3. Run the error checker to catch animation, scale, naming, or setup problems.
4. Start the export and inspect the generated skeletal mesh, skeleton, animation, and morph-target files.
5. Use the generated import script to reconstruct the corresponding Unreal Engine content structure.

Export cameras and cinematic content

Include the camera rig and its Sequencer content in the export. The generated Unreal import script can rebuild the cinematic as a Level Sequence, preserving cuts, aspect ratio, focal distance, and lens shift. Alternatively, copy a camera to the clipboard and paste it directly into the Unreal Engine Sequencer.

Import the generated files into Unreal Engine

1. Open the Unreal Engine project that will receive the assets.
2. Locate the Python import script generated by the add-on.
3. Open the Unreal Engine Python console.
4. Run the generated script.
5. Check the Content Browser for the recreated folder structure and imported assets.

Generated scripts require Unreal Engine 4.26 or later. If the script appears to do nothing, confirm that it is being run inside the engine's Python console and that the engine version meets the requirement.

Configuration reference

• Target engine: Unreal Engine 5 by default, with Unreal Engine 4 support.
• Export format: FBX by default; Alembic is available for caches and simulation-driven meshes.
• Unit scale: Auto by default, converting Blender units to Unreal Engine scale.
• Axis transform: Auto by default, adapting transforms and pivots to Unreal Engine conventions.
• Animation mode: Actions by default, with NLA available for mixed tracks.
• Collision shapes: Box, Convex, Sphere, and Capsule.
• Import script: Enabled by default to generate the Unreal Engine Python script.
• Error checker: Enabled by default to inspect naming, scale, materials, and animation setups.
• Provider: OpenAI-compatible by default, with an endpoint URL and key configured in the panel.
• Model: Select the model used for chat-driven operations.

Advanced workflow tips

Validate before troubleshooting Unreal imports

Run the error checker before every substantial export. Problems with units, axes, pivots, naming, materials, or animation setup are easier to fix in Blender before files reach the engine. When possible, use the checker's one-click repair rather than diagnosing the resulting import behavior in Unreal Engine.

Use automatic transforms as a baseline

For most projects, keep unit scale and axis transform on Auto. If an asset arrives at the wrong scale or rotation, re-run the error checker and inspect the object it identifies instead of manually correcting every imported asset.

Choose the animation mode deliberately

Use Actions when you want selected animations to travel with a skeletal mesh as distinct exports. Use NLA when the source scene represents one mixed track that should be exported as a combined animation sequence.

Keep naming and destination structure consistent

The add-on preserves naming nomenclature and creates an Unreal-oriented folder tree. Consistent names for meshes, collisions, sockets, animations, and collections make the generated import script easier to review and the resulting Content Browser easier to maintain.

Use the AI assistant for routine operations

After configuring a provider and model, describe routine tasks such as naming, checking, or export-setting adjustments in Blender. Keep Blender open when working through the Studio Window or an external client so the assistant can communicate with the active add-on session.

Troubleshooting

The ZIP will not install

Unblock the downloaded file with:

powershell Unblock-File -Path "$HOME\Downloads\blender-unreal-asset-bridge.zip"

Then return to Blender's extension installer and install the ZIP again.

The panel is missing

Confirm that the add-on is enabled in Edit > Preferences > Get Extensions. Also verify that you are using Blender 4.2 or later on Windows x64.

Assets have the wrong scale or rotation

Keep unit scale and axis transform set to Auto, then run the error checker again. It is designed to identify the object that breaks the transform chain.

The import script does nothing

Verify that the Unreal Engine version is 4.26 or later and run the generated script from the engine's Python console.

The AI assistant does not respond

Check the provider endpoint, API key, and model name in the N-panel. Blender must remain open while Studio or an external client is communicating with the add-on.

Conclusion

blender-unreal-asset-bridge turns a manual Blender-to-Unreal transfer into a repeatable pipeline. Install the Windows add-on, prepare and validate your scene, batch-export the required assets, and run the generated Unreal Engine Python script. With automatic transforms, Blender-authored collisions and sockets, animation support, cinematic transfer, and optional AI assistance, the workflow reduces repetitive import and setup work while keeping asset preparation in Blender.