modelstringFixed model ID. Swap it with kling-v3-motion-control to switch versions.
Default: kling-v2.6-motion-control
Kling 2.6 Motion Control API
Transfer a reference video's motion to one character image at 720p or 1080p. Use EvoLink's unified API to evaluate dance clips, avatar gestures and motion previews, then choose whether 2.6 meets your brief or 3.0 is worth evaluating.
KlingVideo GenerationAvailable
From ~$0.067 / s of 720p output video$0.074 official price-10%
Motion ControlImage + Video to VideoCharacter AnimationOriginal AudioPer-Second Billing
Production routeLive
Model Highlights
Motion transfer from a reference video · 720p / 1080p · keeps the original audio
Use Cases
Dance clips, avatar and mascot animation, character motion previews
Input
1 character image + 1 motion video: 3–10 s (Follow image) or 3–30 s (Follow video)
Output
720p / 1080p video via an async task; complex motion may shorten the output
Try Kling 2.6 Motion Control before you integrate the API.
Upload a character image and a motion video, pick the orientation and resolution, and preview the result before you wire up the async API.
Create a Sample
Add a character image and a motion video, then set the parameters.Kling 2.6 Motion ControlImage + motion video to video · From ~$0.067/s
Character Image
Required. One JPG or PNG up to 10 MB showing the character's upper body or full body.
0/1 files
Motion Video
Required. One MP4 or MOV up to 100 MB. Use 3–10 s with Follow image or 3–30 s with Follow video. Complex or fast motion may produce a shorter video.
0/1 files
Character orientation
The character keeps the facing of your image. The motion video can be up to 10 s.
Resolution
Keep original audio
On: the output uses the motion video's own audio. Off: the output is silent. No new audio is generated.
Estimated: ~$0.66245 cr
720p × 10s assumed until the motion video length is read
Estimates round the reference length up. Final charges use actual output seconds, rounded to the nearest whole second.
Ready
Your motion-controlled video will appear here
Add a character image and a motion video, then click Generate.
History
Results are kept for 24 hours — download anything you want to keep.
Your generation history will appear here
Know your Kling 2.6 Motion Control testing cost before you add credits.
Pay per second of actual output video. 1080p uses 1.6x the 720p rate; complex or fast motion may produce a shorter output than the reference.
First Test Cost
3s motion video - 720p-10%3s 720p
Credits13.5
One 3s 720p clip, the shortest motion video allowed
Approx. Cost$0.199
About 50 tests with $10 in credits.
In the playground, upload a 3-second motion video and keep 720p to reproduce this minimum-cost test. Trim longer clips to the section you want to test.
Testing Budget Guide
Pick an amount based on how many tests you expect.$10
About 50 tests
Good for a first validation.
$50
About 251 tests
Good for trying different characters and motions.
$100
About 503 tests
Good before production integration.
Common Cost Examples
Short dance clip720p · 5s
~$0.331-10%
~22.5 cr·~$0.368 Official priceHD character animation1080p · 10s
~$1.059-10%
~72 cr·~$1.177 Official priceFull-length take (Follow video)720p · 30s
~$1.986-10%
~135 cr·~$2.206 Official priceEstimated total for one run, with the reference length rounded up. Final billing uses the actual output length, rounded to the nearest whole second.
Kling 2.6 Motion Control Pricing
Kling 2.6 Motion Control-10% vs official
kling-v2.6-motion-control| Item | 720p | 1080p | Billing |
|---|---|---|---|
| Motion controlOutput video, per second | $0.067/s-10% 4.5 cr/s$0.074 Official price | $0.106/s-10% 7.2 cr/s$0.118 Official price | Output seconds (follows the motion video) |
Motion control
Output video, per second · Output seconds (follows the motion video)
720p
$0.067/s-10%
4.5 cr/s$0.074 Official price1080p
$0.106/s-10%
7.2 cr/s$0.118 Official priceEstimates round reference seconds up; final billing rounds actual output to the nearest second. 1080p = 720p x 1.6. Submission reserves credits for the reference length (10 s if unreadable); settlement refunds any unused reserve.
Where Kling 2.6 Motion Control fits your video workflow
Kling 2.6 Motion Control transfers a reference video's performance onto one character image. Use the same EvoLink video endpoint as Kling 3.0 Motion Control: change the model ID and remove element_list when switching to 2.6. Its rate is about 55% of 3.0 at 720p and 66% at 1080p. Output generally follows the reference length, but complex or fast motion may shorten it. Original audio can be kept or muted; this route does not generate new audio.
Input
1 image + 1 motion video
Output
Video, original audio optional
Duration
Generally follows the reference; may be shorter
Resolution
720p / 1080p
Reference limits
Video up to 10 s (Follow image) or 30 s (Follow video)
Kling 2.6 Motion Control model ID for API calls
Kling 2.6 Motion Control
kling-v2.6-motion-controlOne model ID for image-plus-video motion transfer. The request shape is identical to kling-v3-motion-control; only subject elements (element_list) are not available.
Key Kling 2.6 Motion Control API parameters
These fields cover the main integration decisions. Open the API tab for the full request and response schema.
image_urlsarrayOne character image: JPG or PNG, up to 10 MB, 300-65536 px per side, aspect ratio 1:2.5 to 2.5:1.
Default: required
video_urlsarrayOne MP4 or MOV up to 100 MB; 3–10 s with image orientation or 3–30 s with video orientation. Output may be shorter.
Default: required
model_params.character_orientationenumimage keeps the image's facing (video up to 10 s); video follows the clip (up to 30 s).
Default: required
qualityenum720p (std) or 1080p (pro, billed at 1.6x). 4k is rejected.
Default: 720p
model_params.keep_soundbooleanKeep the soundtrack of the motion video; false mutes the output.
Default: true
promptstringAdd details such as clothing, scene elements, or camera effects.
Default: optional
callback_urlstringHTTPS webhook that receives the task result instead of polling.
Default: optional
What Kling 2.6 Motion Control adds to a video workflow
Real motion, your character
Record or pick a clip of the movement you want, then apply it to any character image instead of describing complex choreography in a prompt.
Original audio kept by default
The soundtrack of the motion video is carried into the output, so dance and performance clips stay in sync with their music. Turn it off to get a silent video.
Same contract as 3.0, lower price
The request and response match Kling 3.0 Motion Control. Start on 2.6 for volume and move individual jobs to 3.0 when you need subject elements.
Two ways to use Kling 2.6 Motion Control: EvoLink API or Agent
Use the EvoLink API for product integration and batch jobs, or call it from Codex, Claude, or Gemini for fast creative and development workflows. Both paths share the same EvoLink API key, balance, model routes, and task history.
Option 1
Integrate with the EvoLink API
Best for: product backends, batch jobs, automated workflows
Call EvoLink’s unified video API from your server and control the model ID, parameters, task queue, callbacks, and result storage.
- 1Validate output and cost with a real brief in Playground
- 2Create an EvoLink API key in the console
- 3Pick the model ID that matches your task from the route cards above
- 4Submit the task and retrieve the result by polling or HTTPS callback
Option 2
Call it with an Agent
Best for: creative and development tasks in Codex, Claude, and Gemini
Give the Agent your output goal, assets, and acceptance criteria. It can choose the route, assemble the request, track the task, and return the result without requiring you to hand-code every step.
- 1Set EVOLINK_API_KEY in your local environment; never put it in code or a prompt
- 2Describe the output goal, references, and the key parameters
- 3Ask the Agent to call a Kling 2.6 Motion Control route and save the task ID
- 4Let the Agent poll the final state, download the result, and report failure reasons
Kling 2.6 Motion Control: what to check for your use case
Dance clips for social content
Start with a full-body character image and a short, continuous dance reference. Check foot placement, limb crossings and timing before reusing the workflow for other characters. A completed task still needs a visual review.
Avatar gestures and mascot animation
Pair an upper-body gesture with an image showing the same body area. Review face, clothing and silhouette through the whole clip. Test head turns and hands crossing the face separately before choosing a version.
Motion previews before production
Use a short reference to check a character's movement and framing before committing to a longer shot. For actions involving a chair, bicycle or other prop, inspect contact and object shape; treat these as tests, not guaranteed production results.
Check the inputs before changing models
- The framing does not match
- Match full-body motion with a full-body image, or upper-body motion with an upper-body image. Keep the head and moving limbs visible, and leave space for the action. Fix the crop before increasing resolution.
- The face changes during a turn
- Try a shorter motion segment with fewer extreme turns or face occlusions and a clearer character image. Change one input at a time, then review identity and motion separately. A different version is worth testing if the revised inputs still miss your brief.
- The output ends before the reference
- Use one continuous shot without cuts or the performer leaving frame. Complex or fast motion can leave fewer usable motion segments and shorten the output. Test a clean 3–5-second section before submitting a longer performance.
Kling 2.6 Motion Control API code example and error handling
This example shows the shortest runnable flow: create a task, save the returned task ID, then poll or wait for an HTTPS callback. Open the API tab for the complete parameter and response reference.
cURL
curl -X POST https://api.evolink.ai/v1/videos/generations \
-H "Authorization: Bearer $EVOLINK_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "kling-v2.6-motion-control",
"image_urls": ["https://example.com/character.png"],
"video_urls": ["https://example.com/dance.mp4"],
"quality": "720p",
"model_params": {
"character_orientation": "image",
"keep_sound": true
},
"callback_url": "https://your-domain.com/webhooks/video-task-completed"
}'
# Save the returned task ID, then query:
curl https://api.evolink.ai/v1/tasks/{task_id} \
-H "Authorization: Bearer $EVOLINK_API_KEY"Parameter validation failed
Check every value against the parameter cards above: ranges, allowed options, asset counts, and file types must match the selected route.
Authentication or balance issue
Check the Authorization bearer token and confirm the available balance and task billing in the console.
Content or asset rejected
Review likeness rights, brand assets, readable text, sensitive content, and input-asset compliance.
Task failed or timed out
A Kling 2.6 Motion Control task that reaches a final failed state is not charged. Keep the task ID, inspect the final state, and identify whether the cause is validation, review, or execution before retrying.
Callback not received
callback_url must be a public HTTPS URL, not localhost or a private network address. Always keep the task ID as a polling fallback.
When to keep 2.6 and when to evaluate 3.0
Choose against your own acceptance criteria: motion timing, character identity, framing and usable duration. The guidance below is an evaluation plan, not a measured quality ranking.
- Keep 2.6 when it meets the brief
- For a repeatable dance, gesture or motion preview, review a short sample against the intended delivery requirements. If the output is usable, you do not need to switch solely because a newer version exists.
- Evaluate 3.0 for subject elements
- Kling 3.0 Motion Control supports subject elements; 2.6 does not. Consider 3.0 when your workflow needs that reference capability. Extra references change the inputs, so evaluate this separately from a comparison using the same image and video.
- Compare the same inputs
- Keep the image, motion clip, resolution, orientation and prompt the same for a version comparison. Review every attempt, including failures, before judging which workflow needs less rework. A higher resolution alone does not establish better identity consistency.
Choose a Kling Motion Control route for your workload
| Feature | Kling 2.6 Motion Control | Kling 3.0 Motion Control |
|---|---|---|
| Model ID | kling-v2.6-motion-control | kling-v3-motion-control |
| Price per output second | About 55% of 3.0 at 720p, 66% at 1080p | Higher |
| 1080p multiplier | 1.6x the 720p rate | 1.334x the 720p rate |
| Subject elements (element_list) | Not supported | Up to 1 element |
| Inputs, orientation and duration rules | Same as 3.0 | Image + video, 3-30 s, Follow image or video |
| When to choose it | Cost-sensitive volume and general motion transfer | Jobs requiring subject elements |
Model ID
Kling 2.6kling-v2.6-motion-control
Kling 3.0kling-v3-motion-control
Price per output second
Kling 2.6About 55% of 3.0 at 720p, 66% at 1080p
Kling 3.0Higher
1080p multiplier
Kling 2.61.6x the 720p rate
Kling 3.01.334x the 720p rate
Subject elements (element_list)
Kling 2.6Not supported
Kling 3.0Up to 1 element
Inputs, orientation and duration rules
Kling 2.6Same as 3.0
Kling 3.0Image + video, 3-30 s, Follow image or video
When to choose it
Kling 2.6Cost-sensitive volume and general motion transfer
Kling 3.0Jobs requiring subject elements
Need subject elements? See Kling 3.0 Motion Control →
Kling 2.6 Motion Control key details
Kling 2.6 Motion Control routes to Kling's kling-v2-6 model
EvoLink sends your request to Kling's motion control endpoint with the 2.6 model. Parameters are validated before the task is queued, and element_list is rejected with a 400 because 2.6 does not support subject elements.
Kling 2.6 Motion Control runs as an async task
Submit a task, then poll GET /v1/tasks/{task_id} or receive a callback. The finished video URL is kept for 24 hours, so copy it to your own storage.
Kling 2.6 Motion Control bills by output seconds
Credits are reserved for the reference length (10 s if unreadable). Estimates round up; final billing rounds actual output seconds to the nearest whole second, at 1.6x for 1080p. Any unused reserve is refunded.
Why use Kling 2.6 Motion Control through EvoLink
Transparent Pricing
See the per-second rate for 720p and 1080p and estimate each run before you generate.
Unified API
Call Kling and other video models through one API key and one request format.
Unified Balance
Manage credits, spending, and model usage in the same EvoLink account.
Task Status Tracking
Track pending, processing, completed, and failed tasks through a consistent async workflow.
Version Choice
Change the model ID to choose 2.6 or 3.0. Remove element_list when switching to 2.6; use 3.0 for subject elements.
Kling Model Family
Compare Kling routes under one EvoLink account and API key, then choose by capability, quality, and cost.
Kling 3.0 Motion Control
Motion transfer with subject elements for more consistent characters.
View API
Other video models on EvoLink besides Kling 2.6 Motion Control
Seedance 2.0
A video model for text, image, and reference-driven generation with native audio.
View API
Kling 2.6 Motion Control FAQ
What is Kling 2.6 Motion Control?
It is Kling's motion control model at version 2.6. You give it a character image and a motion video, and it returns a video in which the character performs the motion from the clip.
Which model ID should I use on EvoLink?
Use kling-v2.6-motion-control. Kling's official API names the same model kling-v2-6.
How is it different from Kling 3.0 Motion Control?
The endpoint and orientation limits are shared. 2.6 is about 55% of the 3.0 rate at 720p and 66% at 1080p, but rejects element_list. Use 3.0 for subject elements and evaluate both on your own references.
Can I switch between 2.6 and 3.0 without changing my integration?
Yes. Change the model field between kling-v2.6-motion-control and kling-v3-motion-control. Remove element_list when you send a request to 2.6.
Does Kling 2.6 Motion Control support element_list?
No. Requests that include a non-empty element_list are rejected with a 400 error. Use Kling 3.0 Motion Control when you need subject elements.
How long can the motion video be?
At least 3 seconds; image orientation allows up to 10 seconds and video up to 30 seconds. Output generally follows the reference, but complex or fast actions may reduce the usable duration.
What does character_orientation do?
image keeps the facing and framing of your character image, which suits camera-facing performances. video makes the character turn the way the person in the clip does, which suits full-body moves and turns.
What images and videos work best?
Match full-body or upper-body framing between your image and video. Keep the head and limbs visible and use one continuous shot with moderate movement. Avoid cuts, occlusion and fast camera moves; test a short clip before running a batch.
How much does Kling 2.6 Motion Control cost?
It is billed per second of output video, and 1080p costs 1.6x the 720p rate. Use the live pricing section and the playground estimate for the current rate of your account.
How is the billed duration calculated?
Estimates round reference length up. At submission, credits are reserved for the reference length (10 s if unreadable). The final charge rounds actual output length to the nearest whole second; any unused reserve is refunded.
Is a prompt required?
No. The prompt is optional and can add details such as clothing, scene elements, or camera effects.
Is the original audio kept?
Yes, by default. Set model_params.keep_sound to false to mute the output.
How long is the result URL available?
EvoLink result URLs are available for 24 hours. Copy completed videos to your own storage instead of using the temporary URL in production.
Is Motion Control the same as Motion Brush or regular Kling 2.6 video?
This route transfers motion from a reference video to one character image. It is a separate workflow from ordinary text-to-video or image-to-video generation and does not provide a brush editor for drawing motion paths. Choose the route by its inputs, not just the Kling version number.
Can I keep the reference video's background unchanged?
Do not assume the source background will be preserved frame by frame. Motion comes from the video, while the character image provides the appearance and scene reference; a prompt can influence scene details. If the original background must stay unchanged, evaluate a video-editing workflow against that requirement.