This Codex-generated editorial illustration explains the route decision. It is not Kling output and is not evidence of model quality.
Use kling-3.0-turbo when you want to create a new short shot from text or one starting image. Use kling-v3-motion-control when you already have a dance, sports move, gesture, or performance video that the character should follow. The first route invents motion from instructions. The second transfers motion from a driving clip.
These routes solve different production tasks and expose different controls. As verified on September 5, 2026, Turbo does not expose native audio, first and last frames, multiple references, or a dedicated camera-control switch. Motion Control requires a character image and a driving video up to 30 seconds.
Start with the Kling route selector if your shot requirement is still unclear.
Key takeaways
- Choose
kling-3.0-turboto generate a new 3 to 15 second Studio shot from text or one starting image. The current API builder offers 5 or 10 seconds. - Choose
kling-v3-motion-controlto transfer an existing performance from a driving video to one character image. It is not a text-to-video route. - Upstream Kling VIDEO 3.0 family features do not automatically appear in either connected route. Check the live controls before planning audio, 4K, multi-shot, or reference-heavy work.
- Motion Control pricing currently differs across public pages. Treat every displayed rate as a dated snapshot and use the accepted task quote as final.
- No controlled generation test was run for this guide. The article documents public route fields, official guidance, and production checks, not a visual-quality winner.
Kling 3.0 Turbo vs Motion Control: the short decision
The fastest route decision starts with the material you already have. A written idea or a single product frame points to Turbo. A video containing the exact performance you need points to Motion Control.
| Production question | Choose | Why |
|---|---|---|
| I have a prompt and need a new social hook | kling-3.0-turbo |
It accepts text and creates a new short shot. |
| I have one product image and need camera or object motion | kling-3.0-turbo |
The source image acts as the starting visual for image-to-video. |
| I have a dance, workout, sports move, or gesture to reproduce | kling-v3-motion-control |
The driving video supplies the movement sequence. |
| I need to preserve the driving clip's existing sound | kling-v3-motion-control API |
keep_original_sound can retain that audio. It does not generate a new soundtrack. |
| I need connected native audio, 4K, multiple references, or first and last frames | Neither current route can promise this | Those capabilities may exist upstream, but the current connected controls do not expose them. |
A detailed prompt cannot replace a driving video when exact choreography matters. Motion Control adds unnecessary preparation when the goal is a short product reveal.
Current Studio and API route comparison
The routes share a family name but not an input contract. This table separates Studio and API facts. Values reflect public pages checked on September 5, 2026, and can change.
| Surface | Exact model ID | Required input | Duration | Resolution | Aspect ratio | Sound | Price snapshot |
|---|---|---|---|---|---|---|---|
| Turbo Studio | kling-3.0-turbo |
Text, or text plus one starting image | Page states 3 to 15 seconds; presets show 5, 10, and 15 | 720p or 1080p | 16:9, 9:16, 1:1 | Not exposed | 168 credits per generated second |
| Turbo API | kling-3.0-turbo |
prompt; optional imageUrl |
5 or 10 seconds in the public builder | 720p or 1080p | 16:9, 9:16, 1:1, 4:3, 3:4 | No public audio field | Starts at $0.13 per generated second |
| Motion Control Studio | kling-v3-motion-control |
One character image plus one driving video | Driving video up to 30 seconds | Check live generator | Check live generator | Not a native sound-generation workflow | Check live generator |
| Motion Control API | kling-v3-motion-control |
character_image_url plus motion_video_url; optional prompt |
No separate duration field; billing follows delivered seconds | 720p or 1080p | Controlled through source composition and orientation | Optional original-sound retention | Public price snapshots conflict; accepted quote is final |
Compare the live Turbo Studio controls with the separate Turbo API contract, because their duration and aspect-ratio choices differ.
For transfer work, check Motion Control Studio and its API model page independently.
Editorial route map verified against public controls on September 5, 2026. It is not Kling output evidence.
Why upstream Kling 3.0 features do not define the connected routes
Kling VIDEO 3.0 is a wider upstream model family. Kuaishou announced that family on February 5, 2026, with up to 15-second output, native audiovisual generation, multi-shot narratives, multilingual dialogue, and image or video element references. Its official guide also covers text-to-video, image-to-video, first and last frames, and reference-driven workflows.
Those family capabilities are useful context, not an operational promise for every integration. The current Turbo controls expose a narrower set: text, one optional starting image, resolution, duration, and aspect ratio. They do not expose an audio field, multiple image references, reference video, first and last frames, negative prompts, or a dedicated camera-control switch. Current connected output tops out at 1080p, so an upstream family announcement about 4K must not be rewritten as a route-level 4K claim.
The same boundary applies to Motion Control. Kuaishou described it in its fiscal 2025 results, and the official Kling VIDEO 3.0 guide presents Motion Control as an upgrade to the 2.6 workflow. Its request contract remains a character image plus driving video.
Plan against controls you can submit. If a required field is absent, treat the capability as unavailable until the route contract changes.
Turbo workflow: create a new short shot
Turbo works best when one visible action and one primary camera move define the shot. The official Kling VIDEO 3.0 guide recommends describing the subject, setting, action, camera movement, and visual style clearly. A compact structure helps keep those instructions from competing.
Reusable text-to-video prompt
[Shot size] of [subject] in [environment], performing [one visible action].
The camera [one primary camera move] at [speed].
[Lighting, material, and mood].
End on [final composition].
Keep [identity, shape, color, logo placement, or label] stable.
Example:
Medium close-up of a silver running shoe on a wet stone platform at dawn.
The shoe rotates once as water beads slide across its surface.
The camera makes a slow clockwise orbit.
Soft blue backlight, realistic rubber and woven fabric texture.
End on a clean side profile. Keep the sole shape and red heel tab stable.
Reusable single-image animation prompt
Preserve the subject, composition, colors, and key geometry from the source image.
Animate [one subject motion] over [short timing description].
The camera [one restrained camera move].
The background [subtle environmental response].
Finish with [stable end pose or product angle].
Start with the shortest duration that can express the action. Review it before increasing duration or adding a second movement. This controls variables, but does not guarantee better output.
For a social hook, use one readable opening beat. For a product shot, prioritize shape, label placement, and one restrained camera move. Build longer narratives as planned clips instead of assuming upstream multi-shot controls are connected.
For a production that combines several clips, use the AI Video Agent workflow guide to plan shot handoffs and review stages.
Motion Control workflow: transfer an existing performance
Motion Control uses the driving video as the motion specification and the character image as the identity reference. The optional prompt can reinforce constraints, but cannot replace either file.
Motion input checklist
Check every item before submitting. These constraints are cross-checked against the official Motion Control user guide:
- One main person: Keep one dominant subject in both files. Official guidance says the current workflow supports one primary subject and may select the largest person when several appear.
- Matching framing: Pair a half-body image with a half-body performance, or a full-body image with a full-body performance.
- Visible anatomy: Keep the face, head, hands, and feet visible when the action depends on them. Leave enough space for wide gestures.
- Continuous driving clip: Prefer one uninterrupted shot. Avoid hard cuts, abrupt angle changes, heavy occlusion, and motion blur.
- Moderate action speed: Extremely fast movement makes contact, limbs, and identity harder to inspect.
- Compatible appearance: A major mismatch between the character's body shape, clothing structure, and the reference action raises transfer risk.
- Rights-cleared media: Confirm permission for the person, performance, location, music, voice, and any branded material before upload.
Editorial input checklist based on the official Motion Control guide. It is not Kling output evidence.
Choose the orientation deliberately
The API exposes character_orientation with image or video. Choose video when the character should follow the driving performance's orientation and camera relationship more closely. Choose image when preserving the character image's facing direction matters more and the prompt will guide the camera.
The API also exposes keep_original_sound, which defaults to false. Setting it to true retains the driving video's original audio. It does not create new dialogue, music, sound effects, or synchronized speech.
Reusable Motion Control prompt
Keep the character's facial identity, hair silhouette, outfit colors, and body proportions consistent.
Follow the driving video's [named action] and timing.
Preserve [image orientation / driving-video orientation].
Keep the background [static / subtly responsive] and avoid adding people or props.
Maintain clear hands, feet, and contact with [object or ground].
The official guide says Element Binding uses facial information and does not automatically lock clothing, hairstyle, makeup, or props. State and review those details instead of treating them as guaranteed.
Four production scenarios and the right route
Social hook from a written concept
Choose Turbo. Write one subject action, one camera move, and one end frame. API users can select 9:16 for vertical placement. Test the shortest useful duration first.
Product motion from a packshot
Choose Turbo with one starting image. Preserve geometry, color, label placement, and background layout in the prompt. Avoid combining a complex object transformation with a fast orbit and a large lighting change in the same first attempt.
Dance, sports, or gesture transfer
Choose Motion Control. The exact performance already exists, so the driving clip carries more useful information than a long prose description. Match framing and minimize occlusion before changing prompt wording.
Audio-led shot
Neither route should be assumed to generate native sound in its current connected form. Motion Control can retain the driving clip's original track through the API, but that is preservation, not synthesis. If newly generated synchronized speech or music is mandatory, select a route that visibly exposes those controls. The Wan 3.0 guide documents a different input and audio contract.
Cost planning across Studio and API
Calculate cost from the surface, resolution, and delivered duration. Do not combine Studio credits with API dollars.
For Turbo Studio, the September 5 snapshot shows 168 credits per second: 840 for 5 seconds, 1,680 for 10, and 2,520 for 15. The page shows no resolution-based credit split.
For Turbo API, the public starting rate is $0.13 per second: $0.65 for 5 seconds and $1.30 for 10 before adjustments. The accepted task quote is final.
Motion Control requires extra care. The Motion Control Studio page, Motion Control API model page, and API reference recently showed different public snapshots, including $0.16 and $0.17 per second; the API reference listed $0.160 for 720p and $0.240 for 1080p when checked. This guide therefore does not present one fixed dollar rate. Inspect the live request quote and store the accepted quote with the job record if cost reconciliation matters.
The pricing page explains membership charges. Keep a separate API estimate per route and recheck it before batch submission.
Quality review and single-variable troubleshooting
Review the full clip frame by frame. Check identity, hands, feet, joints, contact, clothing, background, text, and sound. A good thumbnail can hide a broken moment later.
| Symptom | Likely cause | Change first | Keep fixed |
|---|---|---|---|
| Character identity drifts | Fast motion, occlusion, weak reference, or incompatible framing | Use a clearer reference or slower, cleaner driving segment | Resolution, prompt structure, and duration |
| Hands or feet deform | Limbs leave frame, cross the body, or move too quickly | Choose a clip with visible extremities and less occlusion | Character image and orientation |
| Motion is cut off | Duration or source clip does not contain a clean action boundary | Trim to one complete movement or use an available longer setting | Prompt and source identity |
| Product shape changes | Too many simultaneous motion and style demands | Reduce to one object action and one camera move | Source image and aspect ratio |
| Camera fights the action | Prompted camera direction conflicts with the source performance | Remove the extra camera instruction or change orientation | Character and driving clip |
| Unexpected people or props appear | Busy frame or ambiguous prompt | Crop to one subject and explicitly exclude added people or props in plain language | Core action and duration |
| No newly generated sound | Current route has no native sound-generation field | Add sound in post, or choose a route that exposes native audio | Visual prompt and timing |
| Original audio is missing | keep_original_sound is false or unavailable on the chosen surface |
Enable it in the Motion Control API and verify rights | Visual inputs and resolution |
Change one variable per retry. Changing every input and setting at once hides the cause. Log input hashes, route ID, settings, accepted quote, and review notes.
Commercial use and input rights
Commercial use is conditional, not automatic. Eligible outputs created while a paid membership is active may be used commercially, subject to the Terms of Service, the selected model or provider terms, the user's input rights, third-party rights, and applicable law.
Generation does not clear trademarks, likenesses, music, choreography, locations, characters, or other protected material. You remain responsible for rights to prompts, images, people, brands, voices, performances, and third-party inputs.
Motion Control adds two specific checks. The driving performance may carry its own performer or choreography rights, and its original audio may contain separate music, voice, or recording rights. Enabling original-sound retention does not grant a commercial license to that track.
Sources, verification date, and limitations
This guide was verified on September 5, 2026, against public Studio and API pages, official Kling guides, and Kuaishou announcements. Controls and prices can change. Live fields and the accepted quote take priority.
Upstream facts come from Kuaishou's Kling 3.0 launch announcement, fiscal 2025 results, second-quarter 2026 results, and the official Kling VIDEO 3.0 user guide.
No generation task was submitted, no connected API was called, and no controlled output benchmark was run for this rewrite. Official samples and marketing images were not treated as evidence of route quality. The guidance therefore supports route selection and input preparation, but it does not rank visual quality against other models.
Frequently asked questions
Does Kling 3.0 Turbo generate audio on the current connected route?
No public audio field was exposed on the checked Turbo Studio or API surfaces on September 5, 2026. Upstream Kling 3.0 family materials discuss native audiovisual generation, but that family capability does not automatically apply to this route.
Does either route support 4K output?
The current connected routes list up to 1080p. Kuaishou has announced native 4K at the Kling 3.0 family level, but the checked route controls do not expose 4K.
What is the maximum duration?
Turbo Studio states 3 to 15 seconds and shows 5, 10, and 15 second presets. The current Turbo API builder lists only 5 and 10 seconds. The Motion Control landing page accepts a driving video up to 30 seconds, while the API has no separate duration field.
Are Turbo and Motion Control two modes of the same API model?
No. They use separate model IDs and input contracts. Turbo uses kling-3.0-turbo with a prompt and optional starting image. Motion Control uses kling-v3-motion-control with a required character image and driving video.
Can Motion Control transfer several people at once?
The official guidance supports one primary subject. When a driving clip contains several people, the system may select the largest subject. Use one clearly visible person for predictable setup and review.
Does keep_original_sound=true create new dialogue or music?
No. It retains the driving video's existing audio. It does not synthesize a new soundtrack, and it does not provide rights to the retained recording.
Final route check
Choose Turbo when the creative task starts with an idea or one still image. Choose Motion Control when the task starts with a performance that must be transferred. Then verify the live surface, because Studio and API settings differ and upstream family features may not be connected.
Before submitting, record the model ID, inputs, duration, resolution, aspect ratio or orientation, sound choice, and accepted quote. This makes retries easier to diagnose.
Return to the Kling family hub or the exact route page you selected above to begin with the matching source material.
