Different from FBX
Unitree G1 output should be evaluated as robot-oriented motion data, not as a replacement name for animation FBX.
UNITREE G1
Unitree G1 robot motion data from video
AIMoCap supports Unitree G1 robot motion output for teams that need video-driven robot motion data alongside animation outputs.
For robotics teams searching for Unitree G1 motion data workflows from video.
Short answer
AIMoCap supports a Unitree G1 target for video-driven robot motion output that is separate from animation FBX output.
When to use AIMoCap
Use it when you want to evaluate human-source video motion for a G1-oriented downstream robotics or simulation workflow.
When not to use AIMoCap
Do not treat G1 output as a direct substitute for validating motion in your own robot, controller, or simulation environment.
AIMoCap includes a G1 target for robot-oriented output. This gives robotics teams a path from source video to motion data that can be reviewed before downstream use.
The same source clip can also be used for animation targets, helping teams compare human-readable preview output and robot delivery.
The page intentionally separates discovery, review, and validation: AIMoCap can generate a G1-oriented artifact, but robotics teams still need to test it inside their own simulation or robot-control stack.
Robot motion scope
- G1 is the current robot target described in public documentation.
- Robot motion data is separate from animation FBX output.
- For custom robot support, teams should contact AIMoCap for integration planning.
- Preview output is useful for human review, but it is not a substitute for robot-side validation.
- API workflows can request target-aware outputs, which helps robotics teams automate repeated tests without mixing them with animation-only jobs.
Robot-output boundaries
Use these facts to decide whether this workflow matches your output, integration, and cleanup needs.
Target-aware processing
AIMoCap treats Default animation output and Unitree G1 robot output as separate targets, so teams can select the intended result per job.
Integration caution
Robot downstream use still requires validation in the team's own robot or simulation stack before production use.
Search-intent boundary
Users searching for Unitree G1 motion data usually need robot-specific output boundaries, not a generic video-to-animation explanation.
Unitree G1 output workflow
01
Select the robot target
Choose the documented G1 target in Studio or request it through the API target list.
02
Review the processed result
Use the result page to inspect the processed preview before downloading robot motion data.
03
Download robot motion output
Completed Unitree G1 jobs can provide robot motion data for downstream robotics workflows.
04
Validate outside AIMoCap
Use downstream simulation, controller checks, and team-specific safety review before treating any generated robot motion as production-ready.
Common questions
Does AIMoCap currently support Unitree G1?
Yes. It is the currently documented robot motion output target.
Is Unitree G1 output the same as FBX?
No. FBX is animation-oriented output, while the robot target produces robot motion data.
Can other robots be supported?
Additional robot support is a custom integration topic. Teams can contact AIMoCap to discuss requirements.
Can I request Unitree G1 output through the API?
Yes. Unitree G1 is represented as a supported target in AIMoCap's target-aware API workflow when the account and job limits allow it.
Does AIMoCap validate robot safety?
No. AIMoCap can provide robot-oriented motion output, but robotics teams must validate the result in their own simulation, controller, and safety workflow.
Related AIMoCap guides
Continue through this topic cluster to compare output formats, API options, and workflow boundaries.