Skip to main content

Root motion vs in-place by engine: when to choose each

Not sure whether to use root motion or in-place animations? A plain-language guide to choosing the right option for Unreal, Unity, and DCC tools.

Written by Kyle Blietz

Direct Answer

Choose root motion when you want the animation clip itself to carry the character through space. Choose in-place when your engine, controller, or game logic should drive movement instead.

Start Here

Ask one question first: what is supposed to move the character in your project?

  • If the clip should drive the travel, turns, lunges, or authored distance, start with root motion.

  • If your controller, nav system, blend tree, or gameplay code should decide travel speed and distance, start with in-place.

When Root Motion Usually Makes More Sense

Use root motion when:

  • the exact distance and timing of the move matters

  • the action is a one-off move such as an attack, leap, vault, hit reaction, or cinematic beat

  • you want the clip's authored travel to stay intact during playback

When In-Place Usually Makes More Sense

Use in-place when:

  • your locomotion system decides speed and direction

  • you need to reuse the same clip at different travel speeds

  • you expect gameplay code to control navigation, acceleration, stopping, or blending

Unreal Guidance

In Unreal Engine 5, root motion is the better choice when the animation should move the character exactly as authored. In-place is usually cleaner when a locomotion system or character-movement setup is expected to control travel.

If you are unsure which one you have, test the source clip first before retargeting. If the source clip stays effectively in place, troubleshoot it as an in-place animation instead of assuming the retargeter broke it.

Unity Guidance

In Unity 6, the current root-motion docs separate the clip's stored body movement from the runtime root transform that moves the GameObject. That makes Unity a good fit for either approach, but the decision still depends on whether the clip should move the character or whether your Animator/controller/script should do it.

If your clip is in-place, Unity can still drive movement through controller logic or scripted motion. If the clip already contains travel, review the clip's root-transform settings before changing anything else.

Current Unity clip-inspector labels to review include Root Transform Rotation, Root Transform Position (Y), Root Transform Position (XZ), Bake into Pose, Based Upon, Original, Mass Center (Body), Feet, and Offset.

DCC, iClone, and Character Creator Guidance

In DCC and character-authoring workflows, root motion is usually better when you need to preserve the traveled path for editing, preview, or export. In-place is usually easier when you are cleaning, looping, blending, or retargeting the motion before a downstream engine decides final travel.

A Simple Buyer Rule

  • Buying for a gameplay locomotion system: default to in-place unless you know the system expects authored travel.

  • Buying for authored actions or cinematic-style beats: root motion may save time.

  • If you are still not sure, decide based on the destination engine or controller first, not the pack name.

Related Guides

Version-review notes

  • Verified against Unreal Engine 5.7 and Unity 6.4 (6000.4) documentation, May 2026.

  • Title wording uses major version lines only: Unreal Engine 5 and Unity 6.

  • Approved Unity clip-inspector labels are included above verbatim.

Did this answer your question?