Blender Motion Capture: Import, Retarget, and Use Mocap Animations in Blender

Using Motion Capture in Blender

Blender is a natural home for motion capture animation work. It handles FBX and BVH imports natively, provides full NLA (Nonlinear Animation) editing tools, and exports to every major game engine and DCC format. For indie developers, animators, and VTubers who use Blender as their primary 3D tool, integrating motion capture data into a Blender-based pipeline is both practical and powerful.

This guide covers the complete Blender mocap workflow: importing FBX and BVH animation files, connecting mocap data to a Rigify or custom armature, cleaning up common artifacts, and exporting the final result for Unreal Engine, Unity, or delivery to a game-ready asset pipeline.

What you'll learn: This guide walks through the entire blender motion capture process from file import to game-engine-ready export. You'll learn how to import mocap blender supports natively — both FBX and bvh blender formats — how to handle blender animation retargeting from a mocap skeleton to your character rig, and how to troubleshoot the most common blender mocap problems that trip up artists at every skill level.

Importing Motion Capture Data Into Blender

Blender supports two primary mocap formats out of the box, with FBX import handling the majority of modern animation assets.

Importing FBX Motion Capture

FBX is the standard format for professional mocap animation packs and the output of most inertial and optical capture systems.

1. File > Import > FBX
2. In the import options panel (right side of the file browser), configure:
3. Automatic Bone Orientation: Checked — this corrects the bone roll axis to Blender's Y-up convention, preventing immediate pose distortion
4. Import Normals: Checked
5. Ignore Leaf Bones: Checked if the FBX has leaf/null bones at joint ends (common in some capture systems) — these cause extra unwanted bones in Blender
6. Primary Bone Axis / Secondary Bone Axis: Leave at defaults (Y / X) for most mocap FBX files; adjust if bones appear rotated 90° after import
7. Click Import FBX

After import, select the armature and enter Pose Mode. The animation should be visible in the timeline. Press Play to preview. If the character's pose looks correct at rest and the animation plays back smoothly, the import succeeded.

Common FBX import issue: Bones appear rotated 90° from expected positions. Fix: re-import with Primary Bone Axis set to Z instead of Y, or apply a -90° rotation on the armature in Object Mode and Apply (Ctrl+A) to bake the correction.

Importing BVH Motion Capture

BVH (BioVision Hierarchy) is the older mocap format common in academic datasets like Carnegie Mellon University's CMU Graphics Lab database. Blender imports bvh files natively, which makes it straightforward to work with this large library of free motion capture data.

1. File > Import > BVH
2. In the import options:
3. Scale: Leave at 1.0 unless the character appears very small (CMU data often imports at centimeter scale — try 0.01)
4. Rotate: Enabled by default — aligns the BVH's coordinate system to Blender
5. Forward / Up axis: Y forward / Z up for most BVH files
6. Click Import BVH

The bvh blender import creates a new armature with the animation baked directly onto it. This armature won't match your character rig — you'll need to retarget from this armature to your target, which is covered in the next section.

Importing from MoCap Online Packs

MoCap Online animation packs ship as FBX files using a standard biped skeleton. Import using the FBX workflow above. The skeleton uses bone naming and orientation conventions aligned with Unreal Engine's Mannequin and common Blender humanoid rigs, which simplifies the blender animation retargeting step considerably.

Download the free animation pack to test the Blender import workflow before purchasing a full pack.

Retargeting Mocap to Your Blender Character

After you import mocap blender's tools give you three workable approaches to connect that animated armature to your character. The right choice depends on your toolset and how many animations you're processing.

Option 1: Auto-Rig Pro Retargeting (Recommended)

Auto-Rig Pro ($40 on Blender Market) is the industry-standard Blender addon for character rigging and animation retargeting. Its Remap feature handles mocap-to-Rigify and mocap-to-custom-rig retargeting through a visual mapping interface, making blender animation retargeting dramatically faster than manual constraint setup.

Workflow:
1. Install Auto-Rig Pro and enable it in Preferences
2. Open the N-panel → Auto-Rig Pro → Remap tab
3. Set Source Armature to your imported mocap armature
4. Set Target Armature to your character's armature
5. Use the Bones List to map source bones to target bones (Auto-Rig Pro will attempt auto-mapping by name if your source uses standard naming)
6. Click Build Retarget — this creates a constraint-based live connection
7. Bake the retarget to the target armature using Bake Action (NLA Editor or Action Editor)

Auto-Rig Pro ships with preset mappings for Mixamo, BVH, and several common mocap skeletons — if your source matches one of these, the mapping is one-click.

Option 2: Constraint-Based Manual Retargeting

If Auto-Rig Pro isn't available, Blender's built-in constraint system handles blender animation retargeting manually. This approach works for any bvh blender armature or imported FBX skeleton.

1. Select the target armature and enter Pose Mode
2. For each bone you want to retarget, add a Copy Rotation constraint (Bone Constraints panel)
3. Set the Target to the source mocap armature, and the Bone to the corresponding bone name
4. Repeat for all relevant bones
5. Once the live constraints look correct, select all target bones and use Pose → Animation → Bake Action to bake the constraint-driven poses into keyframes
6. Remove or disable the Copy Rotation constraints after baking

This approach is tedious for full-body retargeting but works well for partial retargeting (upper body only, or a single bone chain).

Option 3: The NLA Strip Approach for the Same Skeleton

If your character already uses the same skeleton as the imported mocap (or you've retargeted a master rest pose), NLA strips handle animation layering cleanly. Push each imported Action to the NLA as a strip, then use strip blending and timing controls to combine animations without rebaking.

Cleaning Up Mocap Data in Blender

Raw motion capture almost always needs cleanup. Blender's Graph Editor and Dope Sheet are the tools for this work.

Fixing Foot Sliding

The most common mocap artifact. Foot sliding occurs when foot bones continue to move during contact phases due to root bone velocity.

Manual fix: In the Graph Editor, identify the frames where the foot is in contact with the ground (look for low Y/Z velocity on the foot bone). Set key values manually to hold the foot position flat during contact.

Procedural fix: Use the Foot Roll bone in a Rigify rig — bake the mocap onto the FK bones first, then add IK constraints to hold foot position during contact frames.

Reducing Joint Noise

Inertial mocap data often has high-frequency noise on fast rotations. In the Graph Editor, select all F-curves for a noisy joint and use Graph Editor > Key > Smooth Keys (Shift+O) or apply a Smooth Modifier to the F-curves from the Modifiers panel. Over-smoothing removes noise but also reduces the sharpness of intentional quick movements — find the balance visually.

Creating Clean Loops

For locomotion cycles, the first and last frame must match for seamless looping.

1. Identify the loop point (usually one full stride cycle)
2. Note the bone positions at frame 0
3. At the last frame, set key values to match frame 0 exactly
4. Use the Interpolation mode (set to Linear between last and first key if needed) for smooth crossfade

The Cycle F-curve modifier in the Graph Editor (Add Modifier > Cycles) handles mathematical looping but doesn't fix the pose mismatch at the seam — you still need matching first/last keyframes.

Fixing T-Pose to A-Pose Conversion

Some FBX animations import in T-pose rest position while your character uses an A-pose rig. The visual result is arm animations that look offset sideways — a common pain point in blender motion capture work.

Fix: Apply a rest pose correction armature object that counteracts the T-to-A offset, or add a bone rotation constraint on the upper arm bones to apply the appropriate base rotation offset before the mocap rotation data is applied.

Troubleshooting Common Blender Mocap Import Problems

Even experienced artists run into the same handful of problems when working with blender mocap data. Here are the five most common issues and their fixes.

Scale Mismatch on Import (Bones Appear Tiny or Huge)

When you import mocap blender may display the armature at the wrong scale — bones that are either enormous or barely visible. This is especially common with bvh blender imports from CMU and other academic datasets that were captured in centimeter units.

Fix: In the BVH import dialog, adjust the Scale value before importing. Start at 0.01 for CMU data. For FBX files, the scale is usually correct with Apply Scalings set to FBX Units Scale, but if bones still appear oversized, select the armature in Object Mode, set the scale numerically (N-panel > Item > Scale), and apply with Ctrl+A > Apply Scale. Never retarget before resolving scale — blender animation retargeting from a wrongly scaled armature will produce broken results that are difficult to diagnose.

Axis Orientation Mismatch (Character Faces Wrong Direction)

After importing FBX or bvh blender data, the character may face the wrong direction — sideways or backward — relative to your scene. This happens because different mocap systems and exporters use different forward/up axis conventions.

Fix for BVH: In the import dialog, change the Forward axis from Y to -Y (or Z to -Z) to flip orientation. Fix for FBX: If the character is rotated 90° sideways, re-import with Primary Bone Axis changed from Y to Z. If you've already imported, select the armature in Object Mode, rotate -90° on the appropriate axis, then apply the rotation (Ctrl+A > Apply Rotation) before continuing.

T-Pose vs A-Pose Arm Offset After Retargeting

This is one of the most frustrating blender animation retargeting issues: after retargeting, the character's arms hover at the wrong angle at rest — typically 45° below or above where they should be. The root cause is a rest pose mismatch between the source mocap skeleton (usually T-pose) and the target character rig (usually A-pose).

Fix: Before retargeting, set the source mocap armature's rest pose to match the target rig's rest pose. In Auto-Rig Pro's Remap, use the Fix Roll option to align bone rolls. In manual retargeting, add a base rotation offset to the upper arm Copy Rotation constraints to account for the T-to-A angular difference (typically 30–45° on the shoulder bones).

BVH Bone Name Conflicts With Existing Rig

When you import mocap blender creates a new armature with bone names from the BVH file — names like "LeftArm," "RightLeg," "Spine." If your scene already contains an armature with the same bone names, Blender's constraint targeting can silently point to the wrong armature, producing baffling retargeting errors.

Fix: Before importing bvh blender data into a scene with an existing rig, rename the existing rig's armature object (not the bones) to something distinctive (e.g., "CharacterArmature"). After import, the BVH armature will be named "Armature" by default — rename it immediately to "MocapSource" or similar. Keeping object names distinct prevents constraint targeting confusion throughout the retargeting process.

Ghost Keyframes After NLA Strip Baking

After baking a retargeted animation or an NLA stack to a new Action, you may find that moving bones in Pose Mode snaps them back to unexpected positions. This is caused by leftover keyframes — "ghost keys" — from the original mocap Action or residual NLA strips still influencing the armature.

Fix: After baking, go to the NLA Editor and mute or delete all strips other than the newly baked Action. Then open the Dope Sheet, switch to Action Editor mode, and check for unexpected keyframes outside your intended frame range. Select and delete any stray keys. Finally, in the NLA Editor, verify the active Action is the baked one and that no other strips are marked as active. Running Pose > Clean Keyframes (with a threshold of 0.001) removes redundant keys created by the bake process and reduces file size.

Blender Mocap Workflow: From Download to Engine

Once you're familiar with all the individual steps, the complete blender motion capture pipeline comes down to seven repeatable stages. Use this as a checklist for every animation you process.

1. Download FBX from MoCap Online — choose the correct skeleton format for your target engine (UE5 Mannequin, standard biped). Verify the pack includes the animation clips you need before importing.
2. Import into Blender — use File > Import > FBX with Automatic Bone Orientation checked. For bvh blender imports, set scale to 0.01 if the source is CMU data.
3. Check scale and axis orientation — press Play in the timeline and verify the character moves at the correct size and faces the correct direction. Fix scale and axis issues now, before retargeting.
4. Retarget to your character rig — use Auto-Rig Pro Remap (recommended) or manual Copy Rotation constraints. Verify rest pose alignment before baking to avoid T-pose vs A-pose arm offset.
5. Clean up the animation — fix foot sliding, reduce joint noise with Graph Editor smoothing, and resolve any ghost keyframes from the NLA bake. This is where blender animation retargeting results become production-quality.
6. Create loops if needed — match first and last keyframes for locomotion cycles. Apply the Cycles F-curve modifier for in-editor preview.
7. Export for the target engine — FBX with Apply Scalings: FBX Units Scale for Unreal Engine; FBX with Apply Transform for Unity. Set sampling rate to 30fps unless your project uses 60fps. Import into the engine with the target skeleton selected.

Following this sequence in order eliminates the majority of import errors and retargeting failures that make blender mocap work feel unpredictable.

Exporting Blender Animations to Game Engines

Once your mocap animations are retargeted and cleaned, export them for Unreal Engine, Unity, or other targets.

Export for Unreal Engine

1. Select the character mesh and armature
2. File > Export > FBX
3. In the export options:
4. Apply Scalings: FBX Units Scale (Unreal expects centimeter scale)
5. Armature: enabled
6. Bake Animation: enabled (bakes constraints to keyframes if not already baked)
7. All Actions: checked if exporting multiple animations in one file, OR export individually for cleaner asset management in UE5
8. Leaf Bones: unchecked
9. In Unreal Engine, import with the target Skeleton selected and Import Animations enabled

Export for Unity

Unity's FBX importer is more forgiving about scale and axis settings than Unreal.

1. File > Export > FBX
2. Export settings:
3. Apply Transform: checked
4. Bake Animation: enabled
5. Sampling Rate: 30fps (or match your project's framerate)
6. Import into Unity and set Animation Type to Humanoid on the imported asset

BVH-to-FBX Conversion

If your source animation is BVH and your target needs FBX, the Blender bridge is:
1. Import BVH (as above)
2. Retarget or use as-is
3. Export as FBX with Bake Animation enabled

This is the standard workflow for converting CMU bvh blender data to FBX for game engine use, and it's one of the most practical reasons to keep Blender in your blender motion capture pipeline even if you do final work in another DCC.

Blender Mocap Tools and Addons

Auto-Rig Pro ($40, Blender Market): The production standard for rigging and retargeting. Handles blender animation retargeting from virtually any source skeleton to Rigify or custom rigs.

Animation Layers (free, built-in): The NLA Editor's strip blending system allows layering multiple mocap clips non-destructively.

Rokoko Studio Plugin (free): Rokoko offers a Blender plugin that enables live streaming from the Smartsuit Pro directly into Blender, eliminating the FBX export step for real-time capture review.

BlenRig (free, bundled): Advanced character rigging system with its own retargeting support for BlenRig-rigged characters.

FAQ: Blender Motion Capture

Can Blender use motion capture data from an iPhone?
Not directly via Live Link. For iPhone ARKit face capture, Blender requires either a third-party addon (some integrate with iPhone depth camera data) or recording via an intermediary (record to CSV via Live Link Face app, convert, import). For body capture, record with an inertial suit, export to BVH/FBX, and import into Blender.

How do I get MoCap Online animations working in Blender?
Import the FBX file via File > Import > FBX with Automatic Bone Orientation checked. The animation appears on the imported armature. To apply it to your character, use Auto-Rig Pro's Remap or add Copy Rotation constraints manually. MoCap Online packs use standard bone naming that aligns with common Blender humanoid rigs, reducing the blender animation retargeting effort significantly.

Is Blender good for motion capture cleanup?
Blender's Graph Editor is capable for mocap cleanup tasks — smoothing, loop fixing, and manual correction are all possible. For production-scale cleanup (hundreds of animations), a dedicated DCC like Maya or MotionBuilder is more efficient. For indie projects with dozens of animations, Blender is a practical choice.

Can I stream live motion capture into Blender?
Yes, with specific inertial systems. Rokoko's Blender plugin streams live data from the Smartsuit Pro. Axis Studio (Xsens) has community integrations. This is useful for real-time preview and iterative capture sessions directly in Blender.

Why does my character's arms point wrong after blender animation retargeting?
This is a T-pose vs A-pose rest pose mismatch. Most blender mocap source skeletons are captured and stored in T-pose (arms straight out horizontally), while many character rigs — especially Rigify humanoid rigs — use A-pose (arms angled 45° downward). When you retarget without correcting for this difference, the arm bones carry an unwanted angular offset throughout the animation. The fix is to align the rest poses before retargeting: in Auto-Rig Pro Remap, enable the rest pose correction option, or manually add a -30° to -45° rotation offset on the shoulder Copy Rotation constraints in the Y axis before baking. Correcting the rest pose mismatch is one of the most important steps in any blender motion capture retargeting workflow.

Can I do blender mocap retargeting without Auto-Rig Pro?
Yes — Blender's built-in constraint system handles blender animation retargeting without any paid addons. The process uses Copy Rotation (and sometimes Copy Location for the root bone) constraints on each target bone, pointed at the corresponding source bone on the mocap armature. Once the live-constraint preview looks correct, bake the result with Pose > Animation > Bake Action, then remove the constraints. The manual approach works for any bvh blender armature or FBX source. The trade-off compared to Auto-Rig Pro is time: mapping 50+ bones manually takes 30–60 minutes per skeleton pair, whereas Auto-Rig Pro's preset mappings for common mocap skeletons reduce that to minutes. For one-off retargeting jobs, the manual route is free and sufficient; for recurring blender mocap work across many animations, Auto-Rig Pro pays for itself quickly.

What is the best frame rate for blender mocap exports to game engines?
30fps is the standard for game engine animation imports and the rate at which most blender motion capture data is captured and processed. Exporting at 30fps produces clean, engine-compatible files for both Unreal Engine and Unity. 60fps is supported by both engines and is worth considering for high-fidelity character animations (facial capture, hand gestures, reactive physics-driven motion) where the extra frames carry perceivable detail. The critical rule is to match your export frame rate to your project's animation frame rate setting in the engine — mismatches cause playback speed errors that look like the animation is playing in slow motion or at double speed. Set your Blender scene frame rate (Output Properties > Frame Rate) to match before baking and exporting any blender mocap animation.

Professional Mocap Animations, Ready for Blender

The most efficient Blender mocap workflow starts with production-ready assets that don't need cleanup. MoCap Online's animation packs are delivered in FBX format, pre-cleaned, and tested across Blender, Unreal Engine, Unity, and iClone workflows.

Browse the motion capture animation library for the category that matches your project — locomotion, combat, sports, creature motion, and more. Start with the free animation pack to verify your Blender import pipeline before purchasing. Workflow guides and tutorials are available on the MoCap Online animation blog.