We use cookies to track which lectures you have completed and to measure how students navigate through course material. You can accept all cookies or choose what you allow below.
Game Development 3 min read

Blender to Unreal Engine: A Freelancer's Honest Take on the Workflow

Scale errors, material mismatches, and what the plugin actually fixes

Blender Workflow
Blender to Unreal Engine: A Freelancer's Honest Take on the Workflow

Blender has become the go-to tool for a lot of freelance 3D artists, partly because of the price and partly because it has genuinely caught up with paid software in most areas. But moving assets from Blender into Unreal Engine 5 still has friction points that catch people off guard, especially if your background is in product visualisation or film rather than games.

The scale problem nobody warns you about

Blender uses metric units by default, but Unreal works in centimetres and expects 1 Unreal unit to equal 1 centimetre. A character modelled at 1.8 metres in Blender will import as 1.8 centimetres in Unreal unless you scale on export. This sounds minor until your client messages you at 11pm asking why their character is the size of a thumbnail. Setting the FBX export scale to 100 in Blender fixes it, but you need to know to do it.

What works well

The Send to Unreal plugin, maintained by Epic, has genuinely improved the pipeline. You can push assets directly from Blender without touching an FBX file, and it handles skeletal meshes and animations with reasonable reliability. For static props, the workflow is now close to frictionless if your naming and pivot points are correct from the start.

What still causes headaches

Material translation is still rough. Blender's Principled BSDF does not map cleanly to Unreal's material system, so any complex node setups you built in Blender need to be rebuilt inside Unreal. For a freelancer, this is either extra billable work or a surprise you absorb. Rigged characters with shape keys also require manual conversion steps that add at least 2 to 3 hours per character to a project.

The clearest advice: agree on a technical delivery checklist with your client before modelling starts, not after the first import fails.

Common engine formats at a glance

Different engines have strong opinions about which file formats they'll handle gracefully. The table opposite summarises what you'll encounter most often when bringing 3D assets into production pipelines.

Format choice affects more than just import speed — it determines how much manual cleanup you'll do on materials, rigs, and animations after the fact.

Browse all guides

FBX vs glTF

FBX remains the default for Unity and Unreal, but glTF 2.0 is gaining ground fast — especially for web-based engines and tools that care about open standards.

Scale and axis mismatches

Blender exports in metres with a Z-up axis. Unreal expects centimetres with Z-up. Unity expects metres with Y-up. Knowing this before export saves considerable frustration.

Texture packing

Engines rarely agree on which channels to pack roughness, metallic, and occlusion into. Baking to engine-specific channel layouts before import avoids runtime shader surprises.

3D Format Compatibility Reference
Format Unity Unreal Godot
FBX Native Native Via plugin
glTF 2.0 2021+ 4.26+ Native
OBJ Native Native Native
COLLADA Limited Deprecated Native
USD Package 5.0+ Partial
Blend Via export Via export Via export
Support levels reflect stable release versions as of 2024. Always verify against your target engine version.