Model comparisons
Kling 3.0 Turbo renders up to 15 seconds per request; Kling 2.5 Turbo stops at 10. Tier prices, request fields and limits side by side.
Kling 2.5 Turbo image-to-video animates an opening frame into a 1080p clip of 5 or 10 seconds, with a generated audio track on every clip. Add an optional closing frame to pin how the shot ends.
View model details →View sample outputs →Kling 3.0 Turbo image-to-video animates your opening frame into a 3 to 15 second clip at 720p or 1080p. The person, outfit and setting hold from the image, and a matching soundtrack is generated with every clip.
View model details →View sample outputs →Compare
Start with the input you have, the result you want and your budget. These are the differences that affect that choice.
Compare the published examples, then try the same input on both models with matching settings.
The Spicy Index and Freedom Score for both models, from the same daily calculation as the leaderboards.
| Measure | Kling 2.5 Turbo | Kling 3.0 Turbo |
|---|---|---|
| Spicy Index | 35.7 | 41.1 |
| Freedom Score | 9.0 | 9.0 |
| Evidence | Tested 4 of 6 probe types · 6 runs | Tested 3 of 6 probe types · 5 runs |
| Range if the rest pass | 9.0–60.0 | 9.0–70.0 |
| Price | $0.28 per 5-second clip | $0.56 per 5-second clip |
| Reviews | Read the Kling 2.5 Turbo review | Read the Kling 3.0 Turbo review |
Preliminary · limited independent quality evidence
See both on the leaderboard →Current price
A start price answers a different question than the one you have. These are the tiers both models publish, matched setting for setting, in US dollars per billed unit with no conversion step in between.
These two bill on different tiers, so there is no row to line up. Each one's own published tiers are listed here instead.
Kling 2.5 Turbo: $0.056 / output seconds
Kling 3.0 Turbo: 720p $0.112 / output seconds · 1080p $0.14 / output seconds
Arithmetic on the published rates at each model's own default setting, not a quote. The console prices your actual settings before a request is accepted.
About this comparison
Every row here is read from the JSON Schema the endpoint validates against, so it matches what the API will really accept rather than a feature list written by hand.
Swipe horizontally to compare all fields.
| Controls and limits | Kling 2.5 Turbo | Kling 3.0 Turbo |
|---|---|---|
| Supported tasks | image-to-video | image-to-video |
| Clip length | 5–10 seconds | 3–15 seconds |
| Resolution tiers | Not offered | 720p · 1080p |
| High-resolution tier | No | Yes |
| Negative prompt | Yes | No |
| Execution | Submit, then poll or take the callback | Submit, then poll or take the callback |
| Request timeout | 60 minutes | 60 minutes |
| Availability | Live | Live |
Do low-filter models allow every request?
Two separate facts sit behind these labels. The first is what we do, which is nothing: no platform content filter, and no maturity flag to set on a request. The second is what each model does on its own, and that is the only part that varies between these two.
Kling 2.5 Turbo
This model refuses requests beyond its own limits outright. Measured, not assumed — models we have not measured carry no label at all.
Kling 3.0 Turbo
This model refuses requests beyond its own limits outright. Measured, not assumed — models we have not measured carry no label at all.
Use these content labels to shortlist models, then open each model page for available examples and content-test details.
The label never changes your obligations. Age, consent, real-person likeness and the law where you operate stay with you, and SpicyAPI does not inspect each request.
Can I swap the model ID without changing the request body?
The task lifecycle is shared; the body is not. Each endpoint publishes its own JSON Schema and the API validates against that, so this is the list to reconcile before a switch.
How to choose
Kling 3.0 Turbo supports a high-resolution option.
Compare
The model identifiers are kling/2.5-turbo/image-to-video and kling/3.0-turbo/image-to-video, and both go in the same field of the same request.
Both run the same way: submit the task, then poll it or take the callback. Queueing and retry logic carry over unchanged.
Both use the same submit-and-track flow, but their required inputs may differ. Check each model page before switching.
One key, one balance, one set of spend caps. Both bill to the same account in US dollars, and the per-key daily, monthly and lifetime limits apply to whichever one you call.
Questions developers ask
The two bill on different tiers, so there is no like-for-like row: Kling 2.5 Turbo starts at $0.056 / output seconds and Kling 3.0 Turbo at $0.112 / output seconds. Prices may change; check the estimate shown for your actual settings before submitting.
Kling 2.5 Turbo allows 60 minutes per task and Kling 3.0 Turbo allows 60. Those are ceilings rather than typical times — most requests finish far sooner — but they are what your own client timeout has to survive.
Prices and capabilities shown here come from the current public model catalogue. Check each model page for its latest inputs and examples.