Convert FBX to BVH

A motion-capture player, legacy animation package, or avatar system may accept BVH motion while the supplied animation is an FBX scene. The conversion exports an animated skeleton, not the FBX character model or scene content.

What the FBX format contains

FBX is Autodesk’s 3D interchange format, originally developed by Kaydara. It can store meshes, skeletal rigs, skin weights, materials, cameras, lights, blend shapes, animation curves, constraints, and multiple animation takes. Autodesk Maya, 3ds Max, MotionBuilder, Blender, Unity, Unreal Engine, and many motion-capture systems import FBX files.

An FBX file may contain several armatures, animation layers, inverse-kinematics controls, nonuniform scale, or facial animation. Those elements must be reduced to one evaluated, baked joint animation before export to BVH.

What the BVH format contains

BVH means Biovision Hierarchy. It is a plain-text motion-capture format containing one joint hierarchy, fixed bone offsets, channel definitions, and frame-by-frame position and Euler-rotation values.

BVH contains no mesh, texture, material, skinning, camera, light, blend shape, or constraint data. Its text structure is easy for older mocap applications, research tools, and virtual-character software to parse, and it is often much smaller than a complete FBX scene because geometry and textures are absent.

BVH is not a complete FBX archive format. It preserves only the exported hierarchy and sampled skeletal motion.

Converting in Blender

Blender is the most practical free desktop converter because it imports FBX, permits retargeting and baking, and includes a BVH exporter.

1. Import the file with File → Import → FBX (.fbx).
2. Select the intended armature and play the timeline. If the file has multiple actions or NLA strips, make sure the required action is the one evaluated during the export frame range.
3. Set the scene start and end frames to the exact motion segment. Remove unwanted T-pose frames, calibration frames, and trailing still frames when the receiving application expects only the motion.
4. Retarget the animation to the destination skeleton if its bone layout or naming differs. Do this before BVH export; BVH export does not automatically convert an arbitrary rig to a target humanoid template.
5. Bake constraints, IK, animation layers, and procedural controls to bone keys. In Pose Mode, select the animated bones and use Pose → Animation → Bake Action. Enable visual keying so Blender records the visible evaluated pose rather than only the source curves.
6. Select the armature and use File → Export → Motion Capture (.bvh). Enable the exporter’s selection-only option if the scene has more than one rig.
7. Set the export frame range and scale. Use the root-translation-only option when the target requires translation channels only on the root joint, which is the common BVH convention.
8. Import walk_cycle.bvh into the receiving program and compare its first frame, facing direction, floor height, root movement, and duration with the source.

Blender’s available BVH export settings vary slightly by version. If the exporter does not provide the axis transform required by the destination application, correct the root orientation before export or use the destination program’s BVH import-axis settings.

MotionBuilder and online options

Autodesk MotionBuilder is preferable for production mocap work that needs characterization, retargeting, or cleanup of complex FBX animation. Import the FBX, characterize or retarget the actor as required, plot the final motion onto the destination skeleton, then save or export the baked skeleton motion as BVH.

For a non-confidential test file, CloudConvert or Aspose 3D’s browser converter can be considered only if its current format selector explicitly lists FBX input and BVH output. Upload a short sample first and validate the result in the target application. Online converters cannot reliably resolve custom joint mappings, constraints, multiple takes, or rig-specific root-motion requirements.

Compatibility and quality limits

Export one armature at a time. Standard BVH describes a single root hierarchy, so an FBX scene containing multiple characters or unrelated skeletons must be split into separate exports.

Axis orientation, scale, frame rate, root motion, and joint order cause most failures. BVH has no universal unit declaration, and different programs may interpret its offsets as centimeters, meters, or application units. Check the target’s required up axis, forward axis, unit scale, frame rate, root-joint name, and accepted hierarchy before conversion.

BVH records rotations as Euler channels in a declared order, such as Zrotation Xrotation Yrotation. FBX animation often uses quaternion interpolation or rotation orders that do not map cleanly to the target’s BVH channels. Fast spins can show angle wrapping, discontinuities, or gimbal artifacts after conversion; bake at the required sampling rate and inspect turns, wrists, shoulders, and hips after import.

Many BVH consumers require a humanoid hierarchy with exact names such as Hips, Spine, and LeftArm. Rename or retarget the source rig before export when the destination requires a template. Do not manually add, remove, or reorder joints in the exported text unless the channel layout is updated consistently, because each motion column depends on that hierarchy and channel order.

A static FBX can export a BVH hierarchy, but it cannot create meaningful motion without keyed or baked skeletal animation. Facial blend shapes, mesh deformation, materials, and non-skeletal animation need a separate export or must remain in the original FBX workflow.