ProductivityFree

Send to Unreal

Official Blender-to-Unreal Engine bridge plugin by Epic Games. Transfers static meshes, skeletal meshes, animations, and morph targets from Blender directly into UE5 with a single click. Eliminates manual FBX export/import steps and preserves naming conventions, armature hierarchies, and material slots. A must-have for any Blender artist working in an Unreal Engine game production pipeline.

Open Website Official Docs

Best For

Eliminating manual FBX export/import steps by sending Blender assets directly into a live Unreal Engine 5 scene with one click, preserving mesh, armature, and material data.

Primary Use Cases

- Sending a game-ready character mesh and skeleton from Blender directly into UE5's Content Browser for immediate animation retargeting
- Iterating on environment props by pushing mesh updates from Blender to an open UE5 scene without closing either application
- Transferring a complete modular kit of static meshes in a single batch send, preserving Blender collection hierarchy as UE5 folder structure
- Syncing a Blender-animated cinematic sequence (cameras, objects, lights) directly into UE5 Sequencer for final lighting and rendering
- Exporting and re-importing revised LOD meshes into an existing UE5 Static Mesh asset without losing existing collision or physics settings

Pros & Cons for Game Art

Pros

+ Eliminates the FBX export dialog entirely — a single button push completes what previously took 6–10 manual steps per asset
+ Live link between Blender and UE5 allows sub-minute iteration cycles on mesh changes, transforming how environment art is refined in-engine
+ Preserves Blender collection hierarchy as UE5 folder structure, enforcing consistent asset organization across the pipeline
+ Auto-generates UE5 collision shapes, LOD slots, and Physics Assets from Blender data, removing tedious post-import setup
+ Free and officially maintained by Epic Games, ensuring compatibility updates track UE5 major releases

Cons

− Requires both applications running simultaneously on the same machine, which demands significant RAM — 32 GB minimum for comfortable use
− Complex Blender material node setups do not transfer; only basic Principled BSDF parameters map to UE5 material properties
− Occasional version mismatches between Blender LTS and the addon release cycle can break the connection until an update ships
− Does not support Blender's geometry nodes or procedural modifiers — all geometry must be applied before sending

Suggested Learning Path

1.Install the Send to Unreal addon via Blender's preferences and enable the UE5 Python remote execution plugin on the engine side to establish the live connection
2.Send a single static mesh prop and verify it arrives in the correct UE5 content folder with auto-generated collision and correct scale (1 Blender unit = 1 UE5 cm)
3.Send a skeletal mesh with its armature and confirm the skeleton asset, SkeletalMesh, and Physics Asset are all auto-generated in UE5
4.Set up a path mapping configuration so Blender collections map to specific UE5 content subfolders matching your project's asset organization convention
5.Test the round-trip workflow: edit a mesh in Blender, re-send, and verify UE5 automatically updates the existing asset without creating a duplicate

Quick Tip

Use the "Send to Unreal" collection workflow: place all assets in a Blender collection named "Export" and map it to a UE5 content path — this lets you batch-push an entire modular kit with one button instead of sending assets one at a time.

Setup Notes

- UE5 must have the Python Editor Script Plugin and Remote Execution enabled in Plugins before Send to Unreal can communicate with the engine
- Set Blender's scene unit scale to 0.01 (centimeters) or configure Send to Unreal's scale multiplier to 100 so assets arrive at correct real-world scale in UE5
- Disable "Use Sockets" in Send to Unreal settings unless your mesh intentionally uses Blender empty objects as UE5 socket markers — accidental sockets break collision
- Keep both Blender and UE5 open on the same machine; the plugin communicates over localhost and does not support remote or network-drive project paths

How N-hance Uses It

Send to Unreal is a core pipeline tool in N-hance's 3D Art for Modern Games course, taught as the standard method for moving environment art from Blender into UE5 scenes, letting students spend class time on art decisions rather than manual export configuration.

Send to Unreal

Primary Use Cases

- Sending a game-ready character mesh and skeleton from Blender directly into UE5's Content Browser for immediate animation retargeting

- Iterating on environment props by pushing mesh updates from Blender to an open UE5 scene without closing either application

- Transferring a complete modular kit of static meshes in a single batch send, preserving Blender collection hierarchy as UE5 folder structure

- Syncing a Blender-animated cinematic sequence (cameras, objects, lights) directly into UE5 Sequencer for final lighting and rendering

- Exporting and re-importing revised LOD meshes into an existing UE5 Static Mesh asset without losing existing collision or physics settings

Pros & Cons for Game Art

Pros

+ Eliminates the FBX export dialog entirely — a single button push completes what previously took 6–10 manual steps per asset
+ Live link between Blender and UE5 allows sub-minute iteration cycles on mesh changes, transforming how environment art is refined in-engine
+ Preserves Blender collection hierarchy as UE5 folder structure, enforcing consistent asset organization across the pipeline
+ Auto-generates UE5 collision shapes, LOD slots, and Physics Assets from Blender data, removing tedious post-import setup
+ Free and officially maintained by Epic Games, ensuring compatibility updates track UE5 major releases

Cons

− Requires both applications running simultaneously on the same machine, which demands significant RAM — 32 GB minimum for comfortable use
− Complex Blender material node setups do not transfer; only basic Principled BSDF parameters map to UE5 material properties
− Occasional version mismatches between Blender LTS and the addon release cycle can break the connection until an update ships
− Does not support Blender's geometry nodes or procedural modifiers — all geometry must be applied before sending

Suggested Learning Path

1.Install the Send to Unreal addon via Blender's preferences and enable the UE5 Python remote execution plugin on the engine side to establish the live connection

2.Send a single static mesh prop and verify it arrives in the correct UE5 content folder with auto-generated collision and correct scale (1 Blender unit = 1 UE5 cm)

3.Send a skeletal mesh with its armature and confirm the skeleton asset, SkeletalMesh, and Physics Asset are all auto-generated in UE5

4.Set up a path mapping configuration so Blender collections map to specific UE5 content subfolders matching your project's asset organization convention

5.Test the round-trip workflow: edit a mesh in Blender, re-send, and verify UE5 automatically updates the existing asset without creating a duplicate

Setup Notes

- UE5 must have the Python Editor Script Plugin and Remote Execution enabled in Plugins before Send to Unreal can communicate with the engine

- Set Blender's scene unit scale to 0.01 (centimeters) or configure Send to Unreal's scale multiplier to 100 so assets arrive at correct real-world scale in UE5

- Disable "Use Sockets" in Send to Unreal settings unless your mesh intentionally uses Blender empty objects as UE5 socket markers — accidental sockets break collision

- Keep both Blender and UE5 open on the same machine; the plugin communicates over localhost and does not support remote or network-drive project paths