How to Import Blender Models Into Unity
StyleFrame Team7 min read
The most reliable way to import a Blender model into Unity is to export it as an FBX with transforms applied, drop the file and its textures into your Unity Assets folder, then extract and reassign materials in the Model import settings. Unity can also read a saved .blend file directly, but it relies on Blender being installed on the same machine. That makes FBX the safer choice for team projects and build machines. Meshes, UVs, rigs, and animation carry over well. Blender's shader node materials do not, so plan to rebuild materials in Unity.
Choose a format: .blend, FBX, or glTF
You have three realistic options.
- .blend file: Save into your Unity project's Assets folder and Unity imports it. It is fast for prototyping, but it needs Blender installed everywhere the project opens. Cameras may come in too.
- FBX: The standard route. It is self-contained, widely supported, and gives you explicit control over scale, axes, animation, and which objects are exported.
- glTF/GLB: Good for PBR-oriented assets, but it may require additional tooling or packages in Unity. Use it if your pipeline already centers on glTF.
For most production work, use FBX.
Prepare the model in Blender first
Most import problems come from the Blender scene, not from Unity. Spend two minutes on cleanup before exporting.
- Set sensible units. Leave the scene's unit scale at 1.0 and model at real-world size. One Blender unit then maps cleanly to one Unity meter.
- Apply transforms. Select your objects and use Object > Apply > All Transforms (or at least Rotation & Scale). Unapplied scale is a common cause of strange sizing and physics behavior in Unity.
- Check normals. Turn on Face Orientation in the viewport overlays. Blue is correct. Red faces will render inside-out or look dark.
- Name things clearly. Object, material, and armature names carry into Unity. "Cube.014" is a headache in a scene with fifty assets.
- Set the origin. The origin becomes the pivot in Unity. Place it where you want to rotate or snap the object, usually at the base.
- Manage modifiers. Subdivision, Mirror, and Boolean modifiers need to be applied (or the export set to apply them) so the exported mesh matches what you see. Keep a non-destructive copy of the original.
- Keep the polygon count realistic. Real-time engines handle far less geometry than offline renderers. Decimate or retopologize heavy sculpts, and bake detail into normal maps.
Export from Blender as FBX
Go to File > Export > FBX (.fbx) and use these settings as a starting point:
- Limit to > Selected Objects: Export only what you need, not the entire scene.
- Object Types: Choose Mesh and Armature as needed. Deselect Camera and Light unless you want them in Unity.
- Apply Scalings: FBX All is the usual choice for Unity, and it avoids unit-scale mismatches.
- Forward / Up: Blender's defaults of -Z Forward and Y Up work with Unity.
- Apply Transform: Enable it if your model arrives rotated by 90 degrees on the X axis. It bakes the axis conversion into the mesh. Note that it can cause problems with armatures and animation, so test on a simple asset before applying it across a project.
- Apply Modifiers: Enable it to export the evaluated mesh.
- Path Mode: Set it to Copy and turn on the Embed Textures button if you want textures bundled inside the FBX. Many teams prefer to keep textures as separate files in a Textures folder for easier editing.
Save the FBX inside your Unity project's Assets folder, ideally in a clear structure such as Assets/Models/Chair/.
Bring the file into Unity
Drag the FBX into the Project window, or right-click in the Assets folder and choose Import New Asset. Unity creates a model asset with a set of import settings in the Inspector. Select it and review three tabs.
Model tab
- Scale Factor: Confirm the object appears at the correct size next to a 1-meter default cube. Adjust here if needed.
- Mesh Compression, Read/Write, and Optimize Mesh: Leave Read/Write off unless scripts need to modify the mesh at runtime, since enabling it increases memory use.
- Normals and Tangents: Import is usually right if you have authored normals in Blender. Calculate is a fallback.
- Generate Lightmap UVs: Enable this if the object will be baked into Unity lightmaps and you do not have a dedicated second UV channel.
- Generate Colliders: Use it for simple static geometry. For complex objects, add primitive colliders manually.
Rig tab
- Set Animation Type to Humanoid for biped characters you want to retarget, Generic for creatures, props, and mechanical rigs, or None for static meshes.
- Click Configure to verify bone mapping on Humanoid rigs.
Animation tab
Blender actions arrive as clips. If you used the NLA editor, bake or push down your actions before export so they appear as expected. Split long timelines into named clips by frame range, and set Loop Time for cycles such as walks and idles.
Fix materials and textures
This step trips up most people. Blender's Principled BSDF and node-based materials do not convert into Unity shaders. What comes through is usually the material name and, at best, a base color. Unity then assigns a default shader.
The reliable workflow:
- Get your textures into Unity. If images are packed in the .blend file, use File > External Data > Unpack All Into Files in Blender, then copy the images into your Unity project. Alternatively, embed them in the FBX.
- Extract materials. In the model's Inspector, open the Materials tab, and use Extract Materials (and Extract Textures if you embedded them) to create editable assets in a folder.
- Switch to the correct shader. Use Lit in URP or HDRP, or Standard in the Built-in Render Pipeline. Pink materials mean the shader does not match your active render pipeline.
- Assign maps. Put base color into Base Map or Albedo, normal maps into Normal Map (set the texture type to Normal Map when Unity prompts), and metallic/roughness data into the Metallic and Smoothness inputs. Remember that Unity uses Smoothness, which is the inverse of Roughness, and often expects it in the alpha channel of the metallic map.
- Bake procedural textures. If you built the look with Cycles nodes (noise, color ramps, procedural patterns), bake them to image maps in Blender first. Unity cannot read those node trees.
If the texture still seems wrong, check that the UV map exists and that the object was not exported with overlapping or missing UVs.
Troubleshoot common problems
- Model is rotated 90 degrees: Use Apply Transform on export, or apply rotation in Blender before exporting. Avoid hand-correcting rotation on the Unity prefab if you can fix it at the source.
- Model is 100x too large or small: Check the Apply Scalings and Scale Factor settings and your Blender unit scale.
- Faces look missing or inside-out: Recalculate normals in Blender (Shift+N in Edit Mode). If the material is single-sided, flip the faces or enable double-sided rendering where appropriate.
- Materials are white or blank: Textures were not linked. Extract materials and reassign maps.
- Extra cameras or lights appear: Deselect those object types in the Blender export panel.
- Animations are missing or doubled: Confirm that actions are baked and that the Animation tab lists your clips. Unity can only play what was exported.
- Shape keys do not behave: Blender shape keys import as blend shapes. Check that the mesh exports with them and that the SkinnedMeshRenderer shows the sliders.
Build a repeatable pipeline
If you move assets between Blender and Unity regularly, standardize it. Keep one folder convention, one export preset (Blender lets you save operator presets in the FBX dialog), and a short checklist covering scale, transforms, naming, and texture paths. Using version control for both the .blend source and the exported FBX makes it easy to roll back if a change breaks the Unity side.
Quick checklist
- Clean up the Blender scene: units, transforms, normals, naming, origin.
- Export as FBX with the right object types, scaling, and modifier settings.
- Save the FBX and texture files into your Unity Assets folder.
- Review Model, Rig, and Animation settings in the Inspector.
- Extract materials, switch to the correct render pipeline shader, and assign texture maps.
- Bake any procedural Blender textures to images beforehand.
- Test in a scene with a reference cube and lighting, then save an export preset for next time.
Once you have done this a few times, the process takes only a few minutes per asset, and most surprises can be traced back to a short list of causes: scale, rotation, normals, and materials.