FBX downloads and imports into the receiving tool
Review FPS, root motion, foot contact, hand readability, and target rig playback before marking the job accepted.
Treating a successful download as proof that the animation is production-ready.
VIDEO TO FBX API
Video to FBX API workflow
Create AIMoCap video-to-FBX API jobs, upload source clips, poll status, and download outputs when processing completes.
For developers searching specifically for a video to FBX API.
Short answer
AIMoCap's video to FBX API lets a client create an async job, upload a source video, poll processing status, and download an FBX motion result when the job completes.
When to use AIMoCap
Use AIMoCap when your product needs automated video-to-FBX processing for animation review, internal tools, or batch workflows without sending users through Studio each time.
When not to use AIMoCap
Do not use this flow when you need real-time live capture, guaranteed cleanup-free character animation, or a robot-specific artifact instead of animation-oriented FBX output.
Related AIMoCap resources
A video-to-FBX API page should answer a narrower question than a general mocap API page: can a developer upload video and programmatically retrieve an animation-friendly FBX result?
AIMoCap handles this as an asynchronous job lifecycle. The client creates the job, uploads the source clip to the returned upload URL, completes the upload, polls status, and downloads the result artifact after processing.
For FBX-focused integrations, request the Default target when you need animation-oriented output. Robot targets such as Unitree G1 are separate target-aware artifacts and should not be treated as generic FBX replacements.
The strongest integration pattern is to treat FBX as a handoff artifact, not the end of the animation pipeline. Store enough context for downstream tools to know source clip, trim range, FPS, target, preview verdict, and cleanup owner.
Video-to-FBX integration facts
- AIMoCap API jobs are asynchronous; clients should poll status instead of waiting on a blocking request.
- Default is the animation-oriented target for FBX-focused workflows.
- Video-to-FBX API jobs can request export FPS values of 24, 30, 60, and 120.
- Trim start and end are optional fields; source validation happens through the upload and processing lifecycle.
- Video-to-FBX API jobs consume API v-credit separately from web Studio credits.
- A job can request multiple supported targets, but FBX and robot outputs should be handled as different artifacts.
- The API is designed for uploaded source video, not live capture or frame-by-frame streaming.
- A video-to-FBX API client should store artifact metadata, not only the downloaded file, so failed imports and cleanup decisions can be traced later.
- If a clip imports successfully but looks wrong on the final character, the likely issue may be rig mapping, rest pose, scale, root motion, or source-video readability rather than API delivery.
- For batch processing, one representative source clip is not enough; test walking, turns, hands, and foot-contact-heavy clips before estimating cleanup cost.
Video-to-FBX API handoff matrix
Use this matrix to decide whether a completed API job is ready for animation cleanup, needs a different target, or should be recaptured.
Scenario
Recommended action
Watch for
Preview looks plausible but final character playback is wrong
Compare source video, preview, FBX import settings, character rig, rest pose, scale, and retarget settings.
Repeating API jobs when the real issue belongs to downstream rig setup or cleanup.
The product needs both animation review and robot output
Request Default and Unitree G1 as separate target artifacts and store acceptance notes for each.
Using the FBX artifact to approve robot motion or using robot output as a generic animation export.
Video-to-FBX API objections
Video-to-FBX API users usually want to automate a file pipeline, so the page should explain how upload, processing, download, and import review connect.
Persist state across the upload boundary
The job exists before the source file is uploaded, so clients should store job ID and upload completion separately to recover from network interruptions.
FBX quality is judged after import
A successful API response should still be validated in the receiving DCC or engine for scale, root motion, foot contact, and retarget compatibility.
Batch jobs need consistent acceptance notes
Teams processing many clips should record which files were accepted, rejected for source quality, or sent to cleanup so API automation does not hide quality decisions.
Why this is not just a generic API page
Use these facts to decide whether this workflow matches your output, integration, and cleanup needs.
FBX-specific target choice
A video-to-FBX integration should request animation-oriented output explicitly instead of assuming that every target returns the same artifact type.
Pipeline-friendly FPS control
Export FPS belongs in the job request so downstream animation tools can receive motion at the cadence expected by the pipeline.
Separated usage accounting
API v-credit keeps automated video-to-FBX usage separate from browser Studio credit usage, which matters for product integrations and batch jobs.
Handoff traceability
A reliable video-to-FBX API integration records job ID, trim range, FPS, target ID, artifact URL, preview verdict, import result, and cleanup decision.
Batch acceptance
Teams should test several motion categories before assuming the API will behave the same across walking, turns, gestures, jumps, and hand-heavy clips.
Video to FBX API workflow
01
Create a Default-target job
Create an API mocap job with the target IDs your workflow needs. For animation-oriented FBX output, request the Default target and set the export FPS if your pipeline requires 24, 30, 60, or 120 FPS.
02
Upload and admit the video
Upload the source video to the returned URL, then call complete-upload. AIMoCap verifies the uploaded source, applies file and plan limits, and queues the job for processing.
03
Poll and download FBX
Poll the job endpoint until a terminal status. When the Default target completes successfully, download the FBX artifact and preview assets for downstream animation review.
04
Validate the animation handoff
After download, record import status, target character, root-motion expectation, FPS, cleanup notes, and whether the source video should be accepted or recaptured.
Common questions
Can AIMoCap API convert video to FBX?
Yes. Create an async API job, request the animation-oriented Default target, upload the source video, poll status, and download the FBX result after completion.
Which target should I request for FBX output?
Use the Default target for animation-oriented FBX workflows. Robot-specific targets such as Unitree G1 produce different downstream artifacts.
Can I choose the FBX export frame rate?
Yes. The API supports documented export FPS values including 24, 30, 60, and 120.
Does video-to-FBX API usage consume Studio credits?
No. Video-to-FBX API jobs use API v-credit, keeping automated FBX export usage separate from browser Studio credit usage.
Is the video-to-FBX API real time?
No. It is an asynchronous upload-and-process workflow designed for queued jobs, polling, and downloadable results.
What should I store after downloading an FBX result?
Store the job ID, target, export FPS, trim range, artifact URL, preview status, import result, cleanup notes, and whether the source clip was accepted or should be recaptured.
Why can an FBX file import but still look wrong?
A valid file can still need rig-specific cleanup. Rest pose, scale, skeleton mapping, root motion, and final-character proportions can change how the same motion looks.
Related AIMoCap guides
Continue through this topic cluster to compare output formats, API options, and workflow boundaries.
Mocap API
Async job creation, upload, polling, and downloads.
API decision checklist
Use output, limits, and accounting to evaluate fit.
Output formats guide
Compare animation, preview, and robot artifacts.
FBX animation API from video
Use AIMoCap API jobs to request Default output and download animation-ready FBX motion after processing.
Robot motion API for video mocap
Use target-aware AIMoCap API jobs when your integration needs robot motion output such as Unitree G1.
Markerless video mocap API
AIMoCap exposes a markerless video mocap API for supported targets, trim fields, export FPS, polling, and result download.
Sources reviewed
These related AIMoCap resources document the workflow boundaries, output formats, and implementation details referenced on this page.