Rig it when it has to move.

The test

A rig is a skeleton you can pose. You need one when the character has to idle, walk, or run in an engine. You do not need one to orbit a model, print it, or drop it into a still.

If you can describe the performance as “it walks,” rig before you export. If the next person will only rotate it, export the mesh and skip this step.

What it covers

Auto-rig targets humanoid and quadruped characters. Idle, walk, and run are useful first checks, not proof that every pose deforms correctly. Inspect shoulders, hips, elbows, and knees in the receiving tool before approving the rig.

It is not a hand-authored rig for a creature with an unusual limb layout, a cape, or a held prop that has to move on its own. Those still start in a DCC tool, from the mesh.

Why it is on Studio

Pro exports FBX and GLB for a static character. The skeleton, the preview, and the rigged FBX are the Studio step, with API access and a shared workspace.

Enterprise is for volume, SSO, and custom terms. A single character that needs to walk does not require it. Preview the cycle before you download, and fix a bad weight in your DCC rather than regenerating the mesh.

Limits to check before delivery

A humanoid or quadruped label does not guarantee usable bone mapping in every engine. Preview cycles do not cover all joint limits. Custom appendages, accessories, and retargeting can still require manual work; GLB supports animation in the format, regardless of this product's export choices.

• Unity Manual — importing a model
• Khronos — glTF 2.0 specification

Handoff checklist

Import the rigged file in the target project. Confirm the skeleton and clip list, inspect elbow and knee bends, and test shoulders and hips. Verify root motion and a target animation. Keep a record of the receiving engine version and failed poses before production use.