A texture set that looks flawless in Blender can arrive in Unreal looking washed out, too dark, or subtly wrong. The model is fine. The problem is almost always colour space, scale or the export itself.
1. Colour Space on Non-Colour Maps
The single most common error. Roughness, metallic, normal, displacement and ambient occlusion maps are data, not colour. If they are interpreted as sRGB, every value is wrong.
In Blender, set those image nodes to Non-Color. In your engine, ensure sRGB is disabled on the same maps. Only base colour and emission should be treated as colour.
2. Scale Is Not Applied
Unapplied scale breaks normals, physics, modifiers and export. Select your object and press Ctrl+A, then Apply Scale, before exporting anything.
Blender defaults to metres and most engines expect centimetres, so also check your unit scale rather than discovering the problem after import.
3. Normal Map Green Channel
OpenGL and DirectX normal maps differ in green channel direction. Blender and Unreal disagree here.
If your surface detail looks inverted — dents reading as bumps — flip the green channel. Most baking tools offer this as an option, and getting it right at bake time is easier than fixing it later.
4. Overlapping UVs
Fine for tiling. Fatal for baking and lightmaps. If your bake has artefacts or your lighting looks blotchy in-engine, check for overlapping islands and give lightmaps a dedicated non-overlapping UV channel.
5. Exporting Everything as One Object
Merged meshes with a dozen materials are painful to work with downstream. Export logically separated objects with sensible names and material slots — your future self, and anyone else on the project, will thank you.
The Habit That Prevents All of This
Test-import early. Bring a rough version into your engine before you finish texturing. Finding a scale or colour-space problem on a grey blockout takes minutes. Finding it after a full texture pass costs a day.
More free tools in the 3DxDEV Library.
