Blender to Unity: Export Models Without Breaking Scale, Rotation, or Materials

You modeled something clean in Blender. The proportions looked right, the pivot sat where you wanted, everything was fine. Then you dragged the FBX into Unity and your character is now the size of a skyscraper, lying flat on its back, and tinted Unity default grey. Welcome to the single most common rite of passage in game art. The good news is that almost none of it is random. Once you understand why it breaks, the fixes take about thirty seconds each.

Why your model breaks the second it hits Unity

Blender and Unity disagree about two fundamental things, and that disagreement causes roughly 90 percent of the pain.

The first is which way is up. Blender treats the Z axis as up. Unity treats Y as up. So when an FBX crosses over, the importer has to spin your model to translate one convention into the other, and if the transform data baked into the file is messy, you get that classic "lying on its face" rotation where the object reads as negative 90 degrees on the X axis.

The second is how big a unit is. Both apps say "1 unit equals 1 meter," but FBX historically stores scale in centimeters, so a naive export can land in Unity at 100x or, depending on settings, at 0.01x. That is why your prop shows up either microscopic or absolutely enormous with no in-between.

The model isn't broken. Blender and Unity just speak different dialects of the same language, and the FBX is a bad translator unless you tell it exactly what to do.

Kill the scale problem at the source

Do not fix scale by typing 0.01 into the Transform field in Unity. That hides the problem and it will bite you later when physics, nav meshes, and child objects all inherit weird numbers. Fix it in Blender instead.

In Blender, select your object and hit Ctrl+A, then choose All Transforms (or at minimum Rotation & Scale). This bakes your current location, rotation, and scale into the mesh data so the object's transform values read as clean zeros and ones. In the FBX export panel, open the Transform subsection and set Apply Scalings to "FBX Units Scale," leave the Scale value at 1.00. With applied transforms plus that setting, your model arrives in Unity at a sane 1:1 size.

The rotation gremlin, explained for real

This is the one that makes people lose an afternoon. Because of the Z-up versus Y-up mismatch, your model can look perfect in the Scene view but be quietly rotated 90 degrees in its local transform, which wrecks animation, parenting, and anything that reads "forward."

There are two reliable ways to handle it. The old-school trick: in Blender, rotate the object negative 90 degrees on X, apply Rotation & Scale, then rotate it positive 90 back on X without applying. Unity then bakes the correct orientation and your transform reads a tidy 0,0,0. The newer way: in Unity's FBX importer, tick "Bake Axis Conversion." It works, though heads up, it has been historically buggy and conflicts with some export settings, so test it on one asset before you commit a whole library to it.

One trap to avoid: the "Apply Transform" checkbox in Blender's FBX exporter looks like a magic button, but Blender does not reliably apply transforms to objects more than two levels deep in a hierarchy. For a lone prop it is fine. For a rigged character with nested bones and parented attachments, skip it and apply transforms manually instead.

FBX or glTF in 2026?

For years FBX was the only real answer. It still carries mesh, UVs, materials, skeletons, and animation in one file, and every importer on earth understands it, which is why it remains the default for rigged characters and animation-heavy work. Unity 6 imports it natively with no extra setup.

But glTF (and its binary cousin GLB) has quietly become the better choice for a lot of static and PBR-heavy assets. It was designed for real-time from day one, it stores materials in a predictable PBR layout, and it tends to be far more "what you see is what you get" on import than FBX, which can drift depending on the engine's interpretation. Blender 5.1, the current stable release as of early 2026, ships with a solid glTF 2.0 exporter built in. If you are moving environment props, hard-surface kits, or anything where material fidelity matters more than a complex rig, try GLB first. You will often skip the rotation and scale circus entirely because glTF already speaks Y-up.

If you want the deeper version of what "clean mesh, good UVs, proper PBR" actually means before any of this, we broke it down in what game-ready actually means.

What about importing the .blend directly?

Unity can read a raw .blend file if Blender is installed on the same machine, because it quietly runs an FBX export in the background. It is convenient for solo prototyping since saves auto-update in Unity. For a team or a build server, do not rely on it. It needs Blender present, it is slower, and you get zero control over export settings. Export real FBX or GLB files and commit those.

Materials do not come along for free

Here is the part nobody warns you about: your gorgeous Principled BSDF material from Blender mostly does not survive the trip. FBX and glTF carry texture references and basic PBR values, but Blender's node graph does not map one-to-one onto Unity's shader system. Procedural textures, custom node setups, and anything fancy will simply not appear.

The honest workflow is to bake your procedural work down to image textures (base color, normal, metallic, roughness, ambient occlusion), keep those textures in a folder next to your model, and reassign them to a Unity material on the other side. Unity auto-detects textures sitting in a sibling "Textures" folder, which saves you some clicking. Treat materials as something you finish in Unity, not something you expect to teleport.

Clean triangulated topology like this is what actually gets baked into your export. Credit: Wikimedia Commons.

A 60-second checklist before every export

1. Apply All Transforms in Blender (Ctrl+A). Your object should read 0 rotation, 1 scale.
2. Set the origin where you actually want the pivot in Unity (Object, Set Origin).
3. Triangulate if your engine is picky, or let the exporter do it. N-gons can shade weirdly.
4. In FBX export, set Apply Scalings to "FBX Units Scale," Scale 1.00. For glTF, just export, it handles axes for you.
5. Export only what you need (use "Selected Objects" so you don't drag the camera and lights along).
6. Bake procedural materials to textures and keep them in a sibling Textures folder.
7. Drop it into Unity, check scale against a 1x1x1 cube, and confirm the transform reads clean.

Get those seven right and the Blender to Unity handoff stops being a guessing game. If you would rather skip the pipeline entirely for certain assets, buying pre-built game-ready models that already import clean is a perfectly valid time trade, and we covered how to do that without getting burned in where to buy game-ready 3D characters for Unity. Whether you build them or buy them, the same rule holds: get the transforms clean at the source and Unity stops fighting you. You can find game-ready models and kits that follow these conventions over on DevLoot when you want a head start.