--- title: Exporting Blender Animations for Real‑Time Engines siteUrl: https://logzly.com/blenderstudio author: blenderstudio (Blender Studio) date: 2026-06-13T15:01:17.845740 tags: [blender, animation, gamedev] url: https://logzly.com/blenderstudio/exporting-blender-animations-for-realtime-engines --- Need a jitter‑free walk cycle or facial rig from Blender straight into Unity or Unreal? This guide shows **exact, step‑by‑step methods for exporting Blender animations** that retain timing, scale, and bone integrity, so your character moves perfectly the first time you import it, and you can further enhance your workflow with **[essential Blender add-ons](/blenderstudio/essential-blender-add-ons-to-streamline-your-workflow)**. ## Why the Timing Matters Game engines are closing the gap with offline renderers, and real‑time ray tracing makes high‑quality animation a must. If you keep guessing on export settings, you waste development time and miss rapid iteration cycles. A solid export workflow lets you focus on storytelling, not on fixing broken rigs after the fact. ## Preparing Your Animation in Blender ### Clean Up the Action Before you export, scrub through the action and delete any stray keyframes. A hidden rotation on an unused bone will cause a sudden snap in the engine. Use the Dope Sheet’s **“Only Selected”** view to isolate the armature and press **Alt‑I** to delete empty keyframes. ### Apply Scale and Rotation Real‑time engines expect a scale of **1.0** and a rotation of **0°** at the start of an animation. Select the armature, press **Ctrl‑A**, and choose **“Apply Scale & Rotation.”** This prevents the dreaded “scale drift” where a character slowly grows or shrinks during playback. ### Use a Consistent Frame Rate Most engines run at **30 FPS** or **60 FPS**. Set your Blender timeline to match the target engine (Properties → Scene → Frame Rate). Exporting at 24 FPS and playing back at 60 FPS will stretch the motion and make timing feel off. For practical timing tips, see our guide on **[animating a walking cycle in Blender](/blenderstudio/animating-a-walking-cycle-in-blender-tips-for-smooth-motion)**. ## Choosing the Right Export Format Two formats dominate the real‑time world: **FBX** and **glTF**. Both have strengths; the choice depends on your engine. ### FBX – The Old Reliable FBX (Filmbox) has been the workhorse for Unity and Unreal for a decade. It supports baked animation, blend shapes, and most rig features. For creating game‑ready assets, refer to our guide on **[building low‑poly game assets in Blender for Unity and Unreal](/blenderstudio/building-lowpoly-game-assets-in-blender-for-unity-and-unreal)**. The downside is its proprietary nature—different FBX versions can behave inconsistently. ### glTF – The Modern Open Standard glTF (GL Transmission Format) is open, lightweight, and built for real‑time. It handles skinning and morph targets well, and the binary **.glb** packs everything into a single file, ideal for asset bundles. Unity added native glTF support in 2022, and Unreal’s Datasmith pipeline can import it with a plugin. **My take:** For Unity‑centric pipelines, start with **FBX** because its import settings are more mature. For cross‑platform toolchains or tighter file sizes, give **glTF** a try. ## Export Settings That Matter ### Bake Action Enable **“Bake Action”** in the export dialog. This forces Blender to write out every frame’s transform, eliminating reliance on constraints or drivers the engine can’t interpret. Set the **Step** to **1 frame** for maximum accuracy. ### Only Selected Objects Select the armature (and any mesh objects you need) before exporting and tick **“Only Selected.”** This prevents stray objects from sneaking into the file and cluttering the engine’s hierarchy. ### Apply Unit Scale Blender’s default unit is meters, while some engines default to centimeters. In the export dialog, set **“Apply Unit”** to **“Scale All Directions.”** This normalizes size so a 1.8‑meter tall character stays 1.8 m in the engine. ## Importing into Unity 1. Drag the **FBX** or **glTF** file into the **Assets** folder; Unity auto‑generates a prefab. 2. In the Inspector → **Rig** tab, set **Animation Type** to **“Humanoid”** for retargeting or **“Generic”** for custom rigs. 3. Click **Apply**; Unity bakes the animation into an **.anim** asset. 4. Test the clip by dragging it onto the **Animator** window. If the foot slides, check the **Root Motion** setting—enable **Root Motion** on the Animator component and ensure the root bone is correctly marked in Blender. ## Importing into Unreal Engine 1. Place the **FBX** file in the **Content Browser**; Unreal opens the **FBX Import Options** dialog. 2. Under **Skeleton**, create a new one or select an existing compatible skeleton. 3. Enable **“Import Animations”** and check **“Convert Scene”** to bring the scale into Unreal’s centimeters. 4. Click **Import**; the animation appears as an **.uasset**. Open it to preview. 5. If the pelvis bounces oddly, open the skeleton asset and verify the **Root Bone** is set to the correct bone (usually **root** or **pelvis**). ## Common Pitfalls and How to Fix Them ### Missing Blend Shapes Blend shapes (morph targets) disappear if you forget to enable them. In the FBX dialog, tick **“Include > Mesh > Blend Shapes.”** In glTF, enable **“Export > Include > Morph Targets.”** ### Quaternion vs. Euler Rotations Blender stores rotations as quaternions, while some engines prefer Euler angles. Sudden flips can be solved by setting **Primary Axis** to **“Y Forward, Z Up”** and turning **Apply Transform** on. This converts rotations into a format the engine expects. ### Double‑Sided Materials If hair or cloth vanishes from certain angles, enable **Two‑Sided** in the engine’s material settings, or add a small **Backface Culling** toggle in Blender’s material node tree before export. ## A Quick Personal Tale The first time I shipped a complex facial rig from Blender to Unreal, I spent a weekend chasing a phantom “eye blink” that never triggered. The culprit was a driver on the blink shape key referencing a custom property—Unreal simply ignored it. **The fix? Bake the shape‑key animation directly into the FBX.** After that, I celebrated with a coffee that tasted suspiciously like victory. Moral: always bake what you can, and keep drivers for offline work only. ## Wrapping It Up Exporting Blender animations for real‑time engines is less about magic and more about discipline. **Clean your timeline, lock down scale, pick the right format, and respect each engine’s import quirks.** Master these basics, and you’ll iterate on motion faster than ever, turning precious development time into polished storytelling.