Transfer motion from video
Use AI Motion Control to drive a character image with a reference video. Review the input requirements before adding motion transfer to your video pipeline.
Build character animation, talking photos, lip sync, and video style changes into your app. Choose an API based on the images, audio, or video your workflow accepts.
Find your API ↓
Use AI Motion Control to drive a character image with a reference video. Review the input requirements before adding motion transfer to your video pipeline.
Choose AI Talking Photo for a portrait, audio, and script, or an AI Lip Sync mode for image or video input. Match each mode's required media to your workflow.
Use AI Video to Video for a style described in a prompt, or AI Video to Anime for anime conversion. Add the relevant step to your video processing pipeline.
4 API products
Add video transformation to your app with prompt-based editing or a dedicated anime conversion endpoint. Submit the inputs for your chosen workflow, set output options, and retrieve the processed clip.
Build photo dance features into your app using a subject image and a dance reference video. Submit both asset URLs and retrieve the generated video for playback in your interface.
Add motion transfer to your animation workflow with a character image and a driving video. Use the clip as the motion reference and retrieve the resulting character animation.
Add lip sync to image and video workflows, or build talking-photo features with image, audio, and text inputs. Use the corresponding endpoint to retrieve a generated video for your app.
Add specific creative controls to your app: drive a character with a motion clip, sync a visual with speech, or transform a video with a style brief. Each effect has its own documented inputs.
Motion Control and Photo Dance require imageUrl and videoUrl: an image for the character and a video for the motion reference. A text prompt alone is not enough. These requests do not expose duration, ratio, or resolution controls. Let users choose the clip that directs the movement.
Learn more ↗Lip Sync requires visualUrl in every inputType. Image (the default) and video modes also need audioUrl; video-to-video needs targetVideoUrl. Talking Photo instead requires imageUrl, audioUrl, and textContent, limited to 300 characters. Lip Sync has no textContent field. Update form validation when the selected mode changes.
Learn more ↗Video to Video accepts a prompt plus optional video, audio, and up to three image references, with duration, ratio, and resolution controls. Video to Anime instead requires videoUrl and animeStyle and offers duration and resolution choices. Build each form around the selected API's supported inputs and settings.
Learn more ↗Save taskId and query the same capability for the completed videoUrl. If the submission response is lost, recover recent tasks before resubmitting. Follow Retry-After when rate limited and retain the original idempotency key while resolving an uncertain outcome. Your effects can share one job record and video preview.
Learn more ↗Answers for developers building with AI Effects APIs.
You can orchestrate separate tasks in your app: generate speech, wait for its audioUrl, then prepare a Talking Photo request with that audio, a portrait, and the required text. Validate the downstream media requirements first. Each generation remains a separate task with its own credit use.
Use the read-only MCP capability estimator with the chosen effect, input mode, and media. Estimates consume no credits. Duration and other settings can affect the estimate. API tasks share your website credit balance and require an active subscription. Keep the final task usage record too.
VidMage's Developer APIs are currently in beta and are not yet recommended for production. Test the complete workflow with your own images, audio, and clips, including output review and interrupted-task recovery. Recheck the current contract and availability notice before depending on an effect for production.
Confirmed failures are refunded automatically only when the refund outcome is certain. Unknown provider, billing, or refund outcomes remain pending reconciliation. Follow the recovery action and avoid requesting another refund while the outcome is unresolved.