FBX animation import looks simple because Unreal Engine can create an Animation Sequence from a file in a few clicks. Most production problems appear after that first success: the wrong skeleton was selected, extra frames were imported, scale or axes were inconsistent, root motion was misunderstood, or a reimport changed data that gameplay already used.
This guide gives a repeatable import process for animation-only FBX files. Interface labels can change between Unreal Engine releases, but the checks remain useful because they focus on the data relationship between the file, Skeleton asset, and Animation Sequence.
Before opening the import dialog
Inspect the delivery information first. You should know:
- Which skeleton or bone hierarchy the animation was authored for.
- Whether the file contains a mesh or animation only.
- The expected frame rate and frame range.
- Whether the clip is Root Motion or In-Place.
- Whether the take should loop and where the loop boundaries are.
- Which unit scale and axis convention the source application used.
If these facts are unknown, importing with random options creates a fragile result. A clip can appear correct in the preview while still being assigned to an incompatible skeleton or containing unwanted root and scale data.
Step 1: choose the destination deliberately
Create or choose a clear content folder before import. Keep animation libraries organized by product or system rather than dropping every take into one directory. A predictable structure makes reimport, retargeting, migration, and marketplace packaging easier.
For a large library, separate source-specific animations from retargeted output. For example, keep original animations in one folder and generated target-skeleton sequences in another. This avoids editing the source asset by accident.
Step 2: import as animation data
Use the Content Browser import command and select the FBX file. For animation-only delivery, enable animation import and disable mesh, material, and texture import unless those assets are intentionally included.
The critical field is the Skeleton. When importing animation without a new skeletal mesh, Unreal Engine needs an existing Skeleton asset. Selecting the wrong asset may cause import failure, missing tracks, distorted motion, or a sequence that is technically linked but visually unsuitable.
Do not choose a skeleton only because its character looks similar. Bone names, hierarchy, reference pose, proportions, and retargeting strategy all matter.
Step 3: verify the animation range
FBX files can contain a longer exported timeline than the intended motion. Review the animation length option and confirm whether Unreal Engine should use the exported range, animated keys, or a specified frame interval.
Common symptoms of a wrong range include:
- Several frozen frames before or after the action.
- A loop hitch caused by a duplicated boundary frame.
- Multiple takes appearing as one long sequence.
- A transition starting late because unused timeline frames were included.
After import, compare the sequence length and frame count with the product documentation or source take.
Step 4: keep sample rate decisions intentional
Unreal Engine can determine a sample rate or use a custom value, depending on the import pipeline and version. A 30 FPS animation does not need to be resampled to a higher rate unless the source data or project has a specific reason. More samples do not automatically create better motion; they can increase asset size and make cleanup less transparent.
If the source contains keys at irregular times, a consistent sample rate can be useful. The safe rule is to preserve the intended motion and verify fast contacts, impacts, foot plants, and short transitions after import.
Step 5: check axes, units, and root behavior
Unreal Engine uses centimeters. Conversion settings can handle common FBX coordinate and unit differences, but they should not compensate for an inconsistent export pipeline. Watch for a character that is extremely small, extremely large, rotated, or moving along an unexpected axis.
Open the imported Animation Sequence and inspect the root:
- Does the root begin from a clean, expected transform?
- Does a Root Motion clip show the intended trajectory?
- Does an In-Place clip remain near the origin without artificial drift?
- Does vertical root motion exist intentionally?
- Do the feet and pelvis behave correctly when root motion preview is enabled or disabled?
If the difference between Root Motion and In-Place is unclear, read Root Motion vs In-Place Animations for UE5 before modifying the root track.
Step 6: inspect the Animation Sequence
Do not stop at the successful import notification. Open the sequence and review it at normal speed, slow speed, and frame by frame.
- Check the first and last pose.
- Confirm that looping clips do not pop.
- Inspect planted feet and prop contacts.
- Look for scale spikes or bone distortion.
- Verify that the expected curves and notifies are present or absent.
- Confirm compression does not damage short, high-speed details.
Test the asset on the actual Skeletal Mesh, not only on a default preview. Proportions and retarget settings can expose problems that the source preview does not show.
Step 7: retarget only when necessary
If the animation hierarchy differs from the target character, importing directly onto the target Skeleton is usually the wrong shortcut. Import the animation against its correct source skeleton, then use an IK Rig and IK Retargeter to create target-skeleton output.
This preserves a clean source asset and makes pose, chain, root, and contact corrections repeatable. The full workflow is described in How to Retarget Mocap Animations in UE5.
Reimport without breaking the library
Reimport is useful when the source FBX is corrected, but it can replace transforms, curves, or other import-dependent data. Before reimporting a production asset:
- Confirm the source file path and take.
- Review the saved import settings.
- Check whether gameplay-added curves, notifies, or edits must be preserved.
- Reimport one representative asset before processing a large batch.
- Test the state machine, montage, and retargeted output after the update.
Common import failures
Unreal Engine asks for a skeleton
An animation-only file must be associated with an existing compatible Skeleton asset. Select the intended source skeleton or import the corresponding skeletal mesh first.
The animation is distorted
Check hierarchy compatibility, reference pose, scale tracks, and whether the file was imported onto the wrong skeleton. Do not attempt to repair a hierarchy mismatch with random import rotations.
The clip contains extra idle frames
Review the exported time range and animation length option. Confirm the source timeline and intended start and end frames.
The character slides
Determine whether the clip is Root Motion or In-Place. For In-Place locomotion, compare the implied animation speed with movement-component speed. Import settings alone may not be the cause.
The loop pops
Compare the start and end poses and check whether the boundary frame is duplicated. The correct loop may use the first pose at the end for interpolation but exclude that duplicate from runtime playback.
A repeatable final checklist
- Correct destination folder.
- Correct Skeleton asset.
- Animation import enabled; unwanted mesh, materials, and textures disabled.
- Correct frame range and sample rate.
- Expected scale and axis orientation.
- Root Motion or In-Place behavior confirmed.
- Loop, contacts, curves, and compression visually checked.
- Gameplay preview tested on the target character.
For assets with documented skeleton, animation type, looping, and engine-version information, browse the nikoff mocap animation packs.