Exporting Models — Export models to OBJ/FBX/GLTF with correct scale and axis orientation

The challenge of moving 3D geometry between applications is as old as computer graphics itself. In the early decades of the field, studios wrote proprietary modeling software and rendered everything in-house, so interoperability was largely unnecessary. As the industry matured through the 1990s and 2000s, however, production pipelines grew to span multiple specialized tools—one for modeling, another for rigging, yet another for rendering or real-time display. The need for reliable interchange formats became acute, and the formats that emerged each reflected the priorities and technical assumptions of their era.

Despite three decades of format development, the fundamental headaches remain surprisingly consistent: axis orientation and unit scale. Blender uses Z-up with meters by default; Unity uses Y-up with meters; Unreal uses Z-up with centimeters. A model that looks perfect in Blender can import into another tool rotated 90°, scaled 100× too large, or buried underground. This lesson equips you to diagnose and prevent those problems by understanding the technical underpinnings of each format and the export settings that govern the transformation.

Before touching any export panel, you need to internalize a small set of foundational concepts. These ideas apply regardless of which format you choose, and mastering them will save you hours of frustrating back-and-forth between applications.

The diagram above distills the single most common source of export errors. When you see a model lying flat on its back in Unity or rotated 90° in Unreal, the root cause is almost always a mismatch between the source application's up-axis and the target's expectation. Blender's export dialogs provide explicit "Forward" and "Up" dropdowns that let you remap axes at write-time, but you must set them correctly—or rely on the format-specific defaults, which vary. For FBX export to Unreal, the recommended settings are Forward = −Y, Up = Z. For glTF, the spec mandates Y-up and the Blender exporter handles the rotation automatically if you leave the defaults untouched.

Under the hood, converting between coordinate systems is a straightforward matrix operation. Every vertex position (x, y, z) in Blender's Z-up, right-handed space must be transformed into the target's convention before being written to the file. Understanding the math—even at a high level—helps you diagnose unusual rotations or scales that automated presets don't cover.

In practice, you rarely need to compute these matrices by hand—Blender's export panels handle them for you. The critical takeaway is that axis conversion and scale are applied as a single composite transform to every vertex, normal, and bone at export time. If your object has unapplied transforms (T_apply ≠ I), those non-identity values compound with the axis rotation and scale, producing misaligned or distorted results. This is precisely why the "apply all transforms" step is non-negotiable.

Choosing an export format is not merely a matter of personal preference—it determines which data survives the transfer and how faithfully your materials, animations, and scene hierarchy are reproduced. The table below provides a detailed comparison, and the diagram that follows visualizes the data pipeline for each format.

A few nuances deserve emphasis. The OBJ format has no formal spec for up-axis; different applications interpret it differently, making the Forward/Up dropdown in Blender's OBJ exporter especially important. The FBX format stores axis information in its header, so the importing application can (in theory) auto-correct—but in practice, Unreal's FBX importer expects specific settings and will misbehave if the header disagrees with its assumptions. glTF eliminates ambiguity by mandating Y-up, right-handed coordinates and meters in its spec, making it the most predictable choice for web and cross-engine projects.

Let's walk through a complete export scenario. You have modeled and rigged a humanoid character in Blender 4.x, standing upright at 1.8 meters tall on the world origin. You need to export it to Unreal Engine 5 as an FBX file with correct scale, orientation, and skeletal hierarchy.

No single export format is universally superior. Each occupies a niche defined by its historical origins, target audience, and technical priorities. The table below synthesizes practical strengths and limitations to guide your format selection in production scenarios.

The OBJ/FBX/glTF triad covers the majority of export needs today, but the interoperability landscape continues to evolve. Pixar's Universal Scene Description (USD) is emerging as the backbone for large-scale collaborative pipelines in film VFX, offering a compositional scene graph that can layer contributions from multiple artists and tools non-destructively. Blender 4.x now ships with a native USD exporter, and understanding its axis and scale conventions—Y-up, meters, right-handed—will become increasingly important as USD adoption grows.

Even as USD matures, the principles you've learned here remain directly applicable. Every interchange format must resolve the same fundamental questions: which direction is up, what does one unit mean, and how do we encode surface appearance? By internalizing these questions now with OBJ, FBX, and glTF, you build a conceptual framework that transfers seamlessly to any future format.