FBX
Choose FBX when the next step is animation review, DCC cleanup, or game-engine import.
OUTPUT GUIDE
Video mocap output formats guide
Compare FBX, BVH, preview video, robot JSON, and simulation-oriented motion outputs in video mocap workflows.
For users who know they need motion output, but are unsure which format fits animation, robotics, or review.
Short answer
Video mocap outputs are not interchangeable: FBX suits animation pipelines, preview video supports review, and robot motion data targets robotics workflows.
When to use AIMoCap
Use AIMoCap when you need target-aware output choices from the same uploaded video job model.
When not to use AIMoCap
Do not assume one exported file can serve animation cleanup, robot control, and simulation without downstream adaptation.
Output format is one of the first decisions in a video mocap workflow. A file that is convenient for an animator may not be the right artifact for a robot or simulation pipeline.
AIMoCap separates animation output, robot motion output, previews, and custom avatar targets so the job intent stays clear.
This guide is meant to reduce format confusion before a team spends time processing footage: first identify the next tool or robot workflow, then choose the motion artifact that matches it.
Format notes
- FBX is animation-oriented and usually expects downstream review and cleanup.
- BVH is common in animation pipelines but may require conversion depending on the toolchain.
- Robot motion data should be treated separately from character animation exports.
- Preview video is for review; it should not be confused with the motion artifact.
- A custom avatar target is a retargeting workflow choice, not a new universal motion file format.
- A good output choice starts from the receiving tool: DCC/game engines, browser review, robot simulation, or a reusable character target.
Format decision table
Use these facts to decide whether this workflow matches your output, integration, and cleanup needs.
BVH
Choose BVH only when the downstream toolchain explicitly expects skeleton-motion data in that format or can convert reliably.
Robot data
Choose robot-specific output when the result must feed robotics review, simulation, or robot-target integration rather than character animation.
Preview MP4
Use preview video to review whether the motion is worth keeping, but do not treat it as the editable motion data artifact.
Custom avatar target
Choose a published custom avatar target when the question is retargeting quality on a specific character rather than a generic export format.
Choosing an output format
01
Animation review
Use FBX-oriented output when the next step is DCC, game engine, or animation cleanup.
02
Robot motion review
Use a robot target such as Unitree G1 when the goal is robot-oriented motion data.
03
Quality review
Use preview video and browser result pages before downloading production artifacts.
04
Custom character review
Use a published custom avatar target when the visual question is whether the motion works on a specific character.
Common questions
Is FBX the same as BVH?
No. Both can appear in animation pipelines, but they store and move through tools differently. AIMoCap publicly focuses on downloadable FBX for Default animation output.
What output should robotics teams look for?
Robotics teams should evaluate robot-specific targets such as Unitree G1 output rather than assuming an animation file is robot-ready.
Why keep preview video?
Preview video gives teams a fast way to inspect the result before downloading and cleaning motion artifacts.
Can one output format cover every workflow?
Usually no. Animation cleanup, browser review, custom avatar retargeting, and robot-motion validation have different artifact requirements.
How should I choose the first output to test?
Start from the receiving workflow: FBX for animation cleanup, preview video for quick review, Unitree G1 for robot-oriented output, or a published custom avatar for character-specific review.
Related AIMoCap guides
Continue through this topic cluster to compare output formats, API options, and workflow boundaries.