Saving, Packing, and Exporting

Before this:Primitive Modeling

What you’ll be able to do

• Pack external resources into a .blend file so nothing goes missing
• Apply an object’s transforms correctly before export
• Export a clean FBX file that a game engine will read correctly
• Recognize and fix the most common export mistakes before they cause problems

Read

Packing resources

A .blend file can reference outside files, most commonly textures, without actually containing them. That’s normally fine, until you move the project, share it, or open it on a different computer, and suddenly Blender can’t find the file it’s looking for and the texture goes missing or turns pink.

File → External Data → Pack Resources embeds every external file directly into the .blend, so the file becomes fully self-contained. It gets larger, but it becomes portable: you can hand it to anyone, on any computer, and everything it needs travels with it.

Get in the habit of packing before you save a version you intend to share or submit. Unpack Resources reverses it later if you need the raw files back out.

Applying transforms before export

Every object carries three transform values: location, rotation, and scale. If those values aren’t at their default state (scale exactly 1.0, rotation exactly 0), that leftover math travels with the object into whatever format you export to, and the receiving software has to interpret it, which is exactly where things go wrong.

Object → Apply → All Transforms (or Ctrl+A → All Transforms) bakes your current location, rotation, and scale into the mesh itself and resets the values to their defaults. The object looks and sits exactly the same. What changes is that it now behaves correctly once exported, instead of arriving rotated, flipped, or scaled 100 times too big.

Do this right before export, every time, on every object you’re exporting. It’s the single most common fix for an asset that “looks fine in Blender but is broken in the engine.”

Units: the most common surprise

Blender’s default unit is the meter. Unreal’s default unit is the centimeter. That mismatch is the source of nearly every “why is my model tiny” or “why is my model gigantic” problem a beginner runs into.

There are two ways to handle it, and either works as long as you’re consistent:

• Keep Blender at 1.0 scale (meters) and let Apply Scalings: FBX All in the export dialog handle the conversion for you
• Set Blender’s Unit Scale to 0.01 in Scene Properties and model directly at centimeter scale to match Unreal from the start

What breaks things is mixing approaches: modeling at one scale, forgetting which one, and exporting with settings that assume the other.

Exporting an FBX

File → Export → FBX (.fbx). The defaults are closer to correct than people expect:

• Forward / Up axis: leave these at Blender’s defaults. They already match what Unreal expects, and changing them is a common way to introduce a rotation problem rather than fix one.
• Scale: 1.0
• Apply Scalings: FBX All
• Apply Unit: checked

The two settings actually worth double-checking, every time, are Apply Scalings and whether you remembered to apply transforms on the object beforehand. Those two account for nearly every real export problem.

A quick pre-export check

Before exporting anything:

1. Select the object
2. Check the sidebar (N panel): Scale should read 1, 1, 1 and Rotation should read 0, 0, 0. If not, apply transforms (Ctrl+A → All Transforms).
3. Confirm textures are packed if you’re sharing the file (File → External Data → Pack Resources)
4. Export, with Apply Scalings set to FBX All

Quick Check

Terms

• Pack Resources
• Apply Transform
• Unit Scale
• FBX
• Apply Scalings

Next

• Blender First Model: Hero Prop — model and export your first complete hero prop
• Import Your Asset — bring your exported FBX into Unreal Engine