To use Mixamo animation in Maya, download the clip from Mixamo as FBX Binary and bring it in with File > Import. If you downloaded it with Mixamo's character attached, it plays straight away. To put the motion on your own rig, define both characters in Maya's HumanIK, set the Mixamo skeleton as the source, and bake the result onto your rig's controls. Everything you need ships with Maya.
The rest of this page is that last route in detail, because that is where people get stuck: the download settings, the T-pose, the character definitions, the control mapping, the bake, and the failures you will hit along the way.
Which case are you in?
| You want | What to do |
|---|---|
| A Mixamo character, animated, in Maya | Download With Skin, then File > Import. Done. |
| A Mixamo clip on another plain skinned skeleton | Steps 1 to 3 for both skeletons, then bake to the target skeleton |
| A Mixamo clip on your own rig with controls | Every step below, baking to your Custom rig |
Mixamo itself is free for anyone with an Adobe ID, and Adobe's Mixamo FAQ says you can use its characters and animations royalty free in personal, commercial and non-profit projects. Its auto-rigger and animations are for bipedal humanoids only.
What you are moving
A Mixamo FBX contains a joint chain named mixamorig:Hips, mixamorig:Spine, mixamorig:LeftArm and so on, with a key on every frame. Your rig has different joint names, a different hierarchy, and controls on top of the joints. Copying curves across fails, because a Mixamo joint and your FK control share neither a rest pose nor an axis orientation.
Retargeting describes both characters to a solver in the same terms (this is the hips, this is the left forearm), lets the solver drive one from the other, and bakes the result onto your controls.
Step 1: download the right file from Mixamo
In Mixamo's download dialog:
- Format: FBX Binary (.fbx).
- Skin: Without Skin is enough when the motion goes onto your own rig. You only need the skeleton.
- Frames per Second: match your Maya scene. The dialog defaults to 30; a new Maya scene defaults to 24.
- Keyframe Reduction: none. You will bake anyway, and reduced keys make the source harder to check.
Walks and runs often show an In Place checkbox in Mixamo's animation settings before you download. Tick it if you want the cycle to stay on the spot, for a game engine or a cycle you will move yourself. Leave it off if the character should travel. Not every clip offers it.
Step 2: import it and get both characters into a T-pose
- Open the scene with your rig and use File > Import to bring in the FBX.
- Go to the first frame. Select every Mixamo joint and set Rotate X, Y and Z to 0. A Mixamo skeleton with all rotations at zero stands in its T-pose. Don't key it; you only need the pose while you define the character.
- Put your own rig in its T-pose too. If the character was built in an A-pose, rotate the arm controls up until the arms are level.
HumanIK needs this. Autodesk's skeleton preparation page asks for a T-stance facing positive Z, head up along Y, arms along X with palms down, and feet pointing along Z. Without it, the solver "will likely produce skewed, awkward or unexpected poses".
Step 3: define the Mixamo skeleton in HumanIK

- Open Windows > Animation Editors > HumanIK.
- In the Start pane, click Create Character Definition. Rename the character to something like
Mixamo. - In the Definition tab, select a Mixamo joint in the viewport, right-click the matching cell in the character diagram and choose Assign Selected Bone. A valid assignment turns the cell green.
- Leave Mirror Matching on. When the joints follow a left/right naming convention, mapping one side fills in the other.
- Map at least the fifteen bones HumanIK requires: hips, spine, head, and for each side the upper leg, lower leg, foot, upper arm, forearm and hand. Add the shoulders, neck and extra spine joints for better results.
- When the validation indicator turns green, click the lock icon to lock the definition.
Autodesk documents the procedure under Define an existing skeleton for HumanIK, and the required bones under HumanIK character structure.
Every Mixamo clip uses the same joint names, so do this once and keep it. The Definition tab's Save Skeleton Definition button writes a naming template; enter mixamorig: in its Prefix field so the template strips the prefix. For the next clip, select the first Mixamo joint, click Load Skeleton Definition and pick your template.
Step 4: define your own character and map its controls
Repeat step 3 for your character's skeleton, the joints your mesh is skinned to, and name it Target.
Here a rigged character differs from a bare skeleton. The rig already drives your joints, so you cannot bake onto them. HumanIK handles this with a Custom rig mapping: with Target as the current character, open the Custom Rig tab, select one of your rig's controls, right-click the matching cell and choose Assign Selected Effector. Mapped cells turn green. Do this for the hips, spine, head, and the arm and leg controls you animate with. Autodesk's page is Create a Custom rig mapping; it also covers knee and elbow pole vectors, which map translation only.
The mapping is the slow part, and you do it once per rig. The Custom Rig tab's Save Custom Rig Mapping button stores it as an XML file, so the next clip on the same rig skips this step.
Step 5: set the source and bake

- In the HumanIK window, set Character to
Targetand Source toMixamo. Your character snaps to the Mixamo pose. - Play the clip. Check the feet, the hands and anything that crosses the body.
- Click the HumanIK menu button and choose Bake > Bake To Custom Rig. Maya sets a key on every mapped control for every frame, using the options in Bake Simulation Options.
- Set Source back to None, delete the Mixamo skeleton, and check that the animation still plays.
Autodesk covers the three bake targets (skeleton, Control rig, Custom rig) in Bake retargeted animation to the target character.
The failures you will hit
The validation indicator stays yellow or red. The character is not in a clean T-stance, or a required bone is missing. Zero the Mixamo rotations again, level your rig's arms, and look for the cell that is not green.
The arms end up raised or drooping on every frame. You defined the two characters in different poses, usually an A-pose rig against Mixamo's T-pose. The solver treats the pose at definition time as "the same pose", so it bakes the difference into the whole clip. Unlock the definition, fix the pose, lock it again.
The feet slide or float. The proportions differ, and the hips travel the source's distance on your character's legs. Watch the contact frames after the bake and correct the hip height and the foot controls there.
The character walks off and snaps back at the loop. You downloaded a travelling walk and wanted a cycle. Download it again with In Place ticked, or keep the travel and offset each loop.
Controls refuse to bake. A locked or already-constrained channel cannot take keys. Unlock it or leave that control out of the mapping.
The timing looks off after import. The FBX came at a different frame rate from the scene, so its keys no longer sit on whole frames. Download the clip again at the scene's rate; that beats repairing the timing.
The baked curves are unusable. A key on every frame on every control is normal after any bake. See how to clean up animation curves in Maya, and retiming animation in Maya if the clip needs to be faster or slower.
Where HumanIK stops
HumanIK is free, built in and good at what it does. Its costs are in setup, not quality:
- Two character definitions and a control mapping before the first clip moves.
- It maps your controls only where you tell it to. A rig with unusual control names or extra helper curves is entirely manual.
- IK controls and pole vectors need care. A foot IK control mapped loosely will slide.
- It needs a character it can describe with its required bones: a spine, a head, two arms, two legs. Anything else is a different job; for rig-to-rig transfers without HumanIK, see copying animation between rigs.
If you retarget a few clips a year onto one character, do it this way. The saved templates make the second clip quick.
One option: AnimKit's Retarget tab
Disclosure: AnimKit is my own paid Maya toolkit. The same retargeter is also sold on its own; both are on the AnimKit page.
It replaces steps 2 to 5. You import the Mixamo FBX, pick a preset (Custom Rig (Smart Auto-Detect) or Unreal Engine 5 Mannequin), click Scan Scene to see which control it matched to each Mixamo joint, and click Auto Retarget & Bake. The detection reads the rig itself: the skinned joints, their symmetry and which control drives each joint, with names used only as hints. The release notes for the current version record it as tested on 27 rigs.
The options are the ones that matter in the manual route: Force Mixamo T-Pose Before Bind, Match Rest Pose, Smart IK Proxy for feet and hands, and Bake to New Animation Layer so your existing animation stays untouched. It skips locked controls and lists them instead of stopping the run. Reset Rig & Clear Keys undoes a bake.
The limits: it reads Mixamo's humanoid skeleton and nothing else as a source. It runs on Maya 2022 to 2026 on Windows only. AnimKit costs $9 a month, $39 a year or $79 once, with no free trial (the AnimKit page offers a 7-day money-back guarantee). And a scan can miss a control on an unusual rig, which is why the scan shows you the mapping before it bakes anything.
Frequently asked questions
Is Mixamo free to use with Maya?
Yes. Adobe's Mixamo FAQ says Mixamo is free for anyone with an Adobe ID, needs no Creative Cloud subscription, and allows royalty-free use of its characters and animations in personal, commercial and non-profit projects. Enterprise and Federated IDs cannot access it.
Which Mixamo format should I download for Maya?
FBX Binary (.fbx), at your Maya scene's frame rate, with Keyframe Reduction set to none. Pick Without Skin if the motion goes onto your own rig, With Skin if you want Mixamo's character too.
Why does my Mixamo character not match my rig after import?
Because the clip is keyed on Mixamo's joints, not your rig's controls. The two need a retarget: define both in HumanIK, set the Mixamo skeleton as the source, and bake to your Custom rig.
Maya or Mixamo: which do I need?
Both, for different jobs. Mixamo is a free web service with an auto-rigger and a library of motion clips for humanoid characters. Maya is the full animation package where you edit, combine and polish that motion, and where you animate everything Mixamo has no clip for.
Can I put Mixamo animation on a non-human character?
Not through Mixamo itself; its FAQ limits the auto-rigger and animations to bipedal humanoids. HumanIK can characterize a quadruped if you set its skeleton up in the biped T-stance, but a two-legged clip on a four-legged character needs heavy rework.
Pick your route
One clip on one character, now and then: use HumanIK and save both templates after the first run. Many clips on several custom rigs every week: a dedicated retargeter will pay for itself in mapping time. Either way, plan to clean the curves after the bake.
