Unity is Y-up and left-handed, Blender is Z-up and right-handed, and the file in between has to survive both. Two export routes, the import fields worth changing, and a repair table for the first import.
Moving a model out of Unity is not a format conversion; it is a negotiation between two engines that disagree about units, handedness and materials. Unity is Y-up and left-handed, Blender is Z-up and right-handed, and the FBX file between them may describe either. Almost every first-import failure is one of four things: a factor of 100 in scale, a 90 degree rotation, textures that never travelled, or a skeleton left behind.
This tutorial covers both export routes, the FBX Exporter package that Unity publishes and glTF through glTFast, then the Blender import fields worth changing and a table for the symptoms that appear in the viewport. It closes with where Open3DAI sits in the pipeline.
Unity keeps no portable copy of an imported model. The .fbx, .obj or .blend you dragged into Assets is the source; what the Scene view shows is a derived mesh cached in the project's Library folder, and that cache is build output, not an asset. If the model came from an Asset Store package, a client or a generator, the original file is usually still in the project. Find it before opening an exporter.
| Export option | What it writes | When to change it |
|---|---|---|
| Format | ASCII text or compact binary | Binary for shipping; ASCII only for readable diffs |
| Convert Units | Unity metres against FBX centimetres | Keep both ends consistent; one-sided toggling causes the 100x error |
| Axis conversion | The up axis the file declares | Match the reader; never fix the axis at both ends |
| Embed media | Textures packed in, not referenced | On for travelling files, off for local iteration |
| Skinned mesh export | Skeleton, weights, blend shapes, clips | Required for rigged meshes; without the armature it arrives static |
Prefabs are where this gets awkward. Unity assigns materials per Renderer rather than per mesh, so one mesh reused by five renderers becomes five sub-meshes with duplicated vertex data. A LODGroup exports only the level you select, and the rest must be exported separately and reassembled by hand. Meshes a script builds at runtime exist only while the game runs, and the exporter sees them only if the object is in the scene.
Take glTF when the asset is unrigged or lightly rigged and materials matter. Unity's glTFast package, com.unity.cloud.gltfast, gained export support in its 5.x line and exposes a GameObjectExport API, so an editor menu and a build script share one code path. Material fidelity is the payoff: metallic-roughness maps onto Blender's Principled BSDF almost one-to-one, and a GLB keeps its textures inside the binary chunk. The cost is that Shader Graph, HDRP and URP materials have no glTF equivalent, so a look built on a custom shader arrives as a plain surface.
| Aspect | FBX via FBX Exporter | glTF or GLB via glTFast |
|---|---|---|
| Rigs | Full skeleton, weights, blend shapes, clips | Supported, but complex rigs are safer in FBX |
| Materials | Phong-style descriptions, custom shaders flattened | Metallic-roughness, closest to Principled BSDF |
| Textures | External by default, embeddable | Inside the GLB chunk, or beside it |
| Blender import | Mature, with axis, scale and bone options | Simple; glTF is metres and Y-up by definition |
| Typical use | Anything returning to Unity | Static props, generated meshes, viewer checks |
| Import field | Typical default | What it does | Change it when |
|---|---|---|---|
| Scale | 1.00 | Multiplies every imported length | A centimetre file arrives 100 times too big |
| Forward / Up | -Z forward, Y up | Rotates Y-up data onto Blender's Z-up world | Only if the model lands on its back |
| Apply Transform | Off | Bakes the root transform into vertices | Static meshes that should start clean |
| Automatic Bone Orientation | Off | Rebuilds bone roll along each chain | Rigged meshes whose bones twist oddly |
FBX has no unit field every tool honours, which is why Unity's import settings carry both Scale Factor and Convert Units. The result is a model at 100 times its intended size or one hundredth of it, and the reflex is to fix it in the import dialog. That works, but it leaves an unapplied scale on the object, which breaks modifiers and armature behaviour later. Import at the right size, or apply the scale immediately after import. For a character that should be 1.8 m tall, read the Dimensions panel: 180 m means the file was authored in centimetres.
Unity is Y-up and left-handed; Blender is Z-up and right-handed. The importer's default pair, -Z forward and Y up, is what stands a Y-up file upright in Blender, so a model on its back means the axis was converted twice or not at all: the exporter wrote a Z-up file that the importer rotated again, or someone edited that pair by hand on one end. Also check the hierarchy for negative scale. A -1 on any parent axis mirrors the mesh and flips its winding order, so the shape looks right until backface culling hides the surface.
| Symptom in Blender | Most common cause | Fix |
|---|---|---|
| 100 times too large or small | Metres and centimetres crossed paths | Set import Scale to 0.01 or 100, then apply |
| Model lies on its back | Axis converted twice, or never | Reimport with -Z forward and Y up |
| Surfaces look inside out | Negative scale in the Unity hierarchy | Recalculate normals outside, remove the mirrored parent |
| Materials are blank or magenta | Referenced textures whose paths died | Embed media on export, or relink by hand |
| Rigged mesh stays put | Skeleton missing from the export | Export armature and mesh together |
Many meshes now arrive generated rather than sculpted. Open3DAI takes text, image or multiview input, applies AI texturing, and exports GLB, glTF, OBJ, STL, PLY or 3MF, which Blender and Unity read without a conversion step; the same prompt can be run through the available engines and compared side by side before exporting, while the 48 format converters, 12 browser tools and REST API handle the file work around it. Two limits matter. Generated meshes are not guaranteed watertight or print-ready, and the service does not rig, animate, retopologise or unwrap UVs, so a generated character needs a hand-built skeleton in Blender before it can leave Unity as a skinned FBX. FBX is not among the export formats.
Package names, engine versions and import defaults move between releases: the FBX Exporter, glTFast and Blender's import panels have all been renamed or reorganised recently, and engine availability, credit pricing and third-party terms change as well. Confirm option labels against your installed versions and check vendor pages before committing a budget.
No. Unity scenes and .unitypackage files are Unity's own serialised formats and Blender has no importer for them. Either export the objects you need from the scene, or unpack the .unitypackage, which is an archive of the original asset files, and take the source FBX out of it.
A unit mismatch between Unity's metres and FBX's centimetre convention. Set the import Scale field to 0.01, or 100 in the opposite direction, and apply the scale straight away so the object does not keep an unapplied transform.
FBX when the asset is rigged or has to go back into Unity, because it carries skeletons, weights and clips most completely. glTF when it is a static or lightly rigged prop and materials matter, since metallic-roughness maps closely onto Blender's Principled BSDF.
Only when the model lives in the scene rather than as a file in Assets. If the original .fbx is still in the project, import that instead. The exporter exists for scene objects, prefabs, LOD levels and meshes that a script builds at runtime.
Embed the textures on export, or copy them next to the exported file, and expect custom shaders to be flattened into a basic surface. Afterwards, check the material slots in Blender and relink anything that arrived as a placeholder.
Yes, along the FBX route: select the armature and the skinned mesh together so the skeleton, weights and clips are written, then verify the armature modifier and bone orientation after import. Constraints, IK targets and Animation Rigging components have no equivalent in the file and must be rebuilt.
FBX and glTF store attributes per vertex, so every UV seam or hard normal edge splits a vertex into several. Merge by distance after import to weld the duplicates back together before you edit the mesh.
FBX is not one of its export formats; the list is GLB, glTF, OBJ, STL, PLY and 3MF. It also does not rig, animate, retopologise or unwrap UVs, so a generated mesh that needs a skeleton gets one in Blender, and the FBX is written there or in Unity.
Dimensions against a length you know, applied rotation and scale, merged seams, recalculated normals, and material slots with no empty entries. Those five checks remove most of the surprises that appear later in the modelling session.
Blender's FBX exporter ships a Unity FBX preset: keep the scale at 1.0, apply transforms, and let the preset handle the axis set. Unity reads one unit as one metre, so the object lands at the size it left with.
Send the same prompt or image to several engines, compare the meshes side by side, then export GLB, glTF, OBJ, STL, PLY or 3MF. Creating an account grants free credits and needs no card.
Blender is free and runs on modest hardware, but the first week goes into a shortcut-driven interface rather than pretty models. Here is the interface in five minutes, a first-model walkthrough, the hotkeys worth memorising and how to pick an export format.
Daz Studio reads OBJ, FBX and Collada, and nothing else you are likely to receive. Here is how to pick a carrier format, land on the right centimetre scale, and repair the three failures people hit: invisible meshes, wrong scale and grey textures.
Surface Material Override in the editor, runtime swaps from GDScript, and the shared-resource behaviour that repaints every copy of a model — plus the PBR values and import settings that make the result hold up.