Kling motion control credits per second: 3.0 and 2.6
Kling charges 9 or 12 credits per second for 3.0 Motion Control and 5 or 8 for 2.6. Rounding rules, and Sume's per-second dollar rate for the same job.

Kling motion control costs 9 credits per second in Standard mode and 12 in Professional mode for Video 3.0, and 5 and 8 credits per second for Video 2.6. A 10-second driving video is 90 or 120 credits on 3.0.
Credit numbers are from Kling's Motion Control User Guide, read 2026-09-29; the page gives credits, not dollars. Sume's dollar rate comes from Sume's pricing code and the Sume API reference, see also API pricing.
How many credits does Kling motion control use per second?
Kling prices by seconds, and lists a Standard and a Professional mode for each version.
| Model | Professional | Standard |
|---|---|---|
| Kling VIDEO 3.0 Motion Control | 12 credits/s | 9 credits/s |
| Kling VIDEO 2.6 Motion Control | 8 credits/s | 5 credits/s |
How does Kling round the length?
The guide says video duration and actual price are rounded to the nearest whole second. Its examples: a 3.4-second clip is billed as 3 seconds, and a 3.6-second clip as 4 seconds.
One caution from the same page: if the model can extract only part of a fast or complex reference, the shorter result still consumes credits, and Kling says they are non-refundable in that case.
What does Sume charge per second for motion control?
Sume lists one model, Kling 3.0 Motion Control, at $0.1575 per output second, plus a 5.5% agent fee by default. Sume rounds the driving video's length up to a whole second, where Kling rounds to the nearest. Your 10-second clip comes to $1.575 before the fee.
The request schema has no field for choosing a Standard or Professional mode, so the Kling mode split in the table above has no Sume counterpart.
When is the money taken?
duration_seconds on the Sume request, 1 to 30, is the driving video's length; the schema says Sume uses it to reserve credits at admit as the rounded-up length times the per-second rate times the margin. Output length follows the driving video.
Send that number accurately: it sets the amount reserved. Job status, results and the request body are in Motion control API: animate an image with a driving video.
Can I convert Kling credits to dollars?
Not from these pages. The Kling guide states credits per second only and gives no dollar value for a credit, while Sume's docs price in dollars from the start. Compare like for like by pricing the same 10-second motion clip in each account: Sume's submit response carries a usage block that quotes the estimated dollar amount, while Kling's guide gives credits only.
Sources
Related posts
More in Pricing
- Lyria 3.5 pricing: what a song costs on Google and on Sume
Google lists Lyria 3.5 at $0.08 per song on the paid tier. Sume lists its own per-generation music price. Both rate cards, side by side.
- MiniMax H3 pricing per second on Sume, by resolution
What a MiniMax H3 or H3 Max clip costs on Sume: a per-second rate by resolution, reserved on submit. Rates for 480p, 768p, 1080p and 2K, with 10-second totals.
- MiniMax H3 reference images: what you pay past the fifth
MiniMax H3 reference-to-video on Sume includes the first five reference images; each one after that adds a charge. Worked totals for 6 to 9 images.
- Nano Banana 2 pricing per image on Sume, by resolution tier
What one Nano Banana 2 image costs on Sume at 512, 1K, 2K and 4K, how the price scales with n, and where Google publishes its own per-image rates.
Written by Sume