Kling 3.0 Turbo gets the shot back while you are still thinking about it. A prompt or a still goes in, 720p or 1080p comes out, and it is the fastest turnaround in the Kling 3.0 generation — which is what lets you try the idea now instead of scheduling it.
Four steps, and the third is the one that keeps the cost down.
A still gives you the look before anything moves, which removes half the variables.
Say what the camera does and what moves in frame as two instructions, not one sentence.
Resolution does not change whether the motion works, and 720p is about a quarter cheaper than 1080p — so test there.
Once the shot is right, generate it again at delivery resolution.
Kling 3.0 Turbo is the fast variant of the Kling 3.0 generation. It takes a prompt, or a still image plus a prompt describing the motion, and returns a clip at either 720p or 1080p. The interesting thing is what it does not have: there is no sound field on this model at all. Kling 2.6 and Kling 3.0 both generate audio with the shot as an option; Turbo simply does not offer it, which makes the choice between them less about quality than about what the clip needs.
If the video will sit under a voiceover or a music bed — which most published short video does — the sound the other models generate is something you would mute anyway, and Turbo is the one to use. If the audio is the point, it has to be 2.6 or 3.0. Resolution is a required field rather than a default, and it is the price: 1080p runs about a quarter more per second than 720p, so 720p is the cheaper place to test.
Creative engine
Per second, by resolution. Nothing else moves the rate.
Same generation as Kling 3.0, tuned for turnaround rather than for the ceiling.
The API has no audio field. For a clip that needs generated sound, use Kling 2.6 or 3.0.
720p or 1080p has to be stated, and it is roughly a 25% price difference.
Pick Turbo when the clip is going to be silent anyway and you want it back quickly. That describes most social video, most background footage, and every clip that will end up under a voiceover — which together is most of what anyone actually publishes. It is also the only Kling here that gives you 1080p as a plain request field, so it is the one to use when delivery resolution is fixed by where the video is going rather than by taste. Kling 2.6 generates the sound with the shot, and Kling 3.0 carries multi-shot sequences — the shelf covers all three, and Turbo is the one that gets you the take fastest.
Turbo has no audio field at all — that is the trade for the turnaround. Kling 3.0 and Kling 2.6 both generate sound with the shot.
Delivery resolution stated directly rather than implied by a tier.
The fast tier of its generation, which matters when you are iterating on motion.
What this variant offers, and where the rest of the Kling line differs.
Generate a clip from a written description with no source material.
Start from a still and describe the motion you want added to it.
Required on every request, and the only thing that changes the per-second rate.
Aspect ratio is chosen when generating from text; from an image it follows the source.
Taken from the model's published API schema.
Clips where the audio was always going to come from somewhere else.
B-roll and cutaways where the soundtrack is recorded separately.
Vertical video where the platform's delivery resolution is the whole spec.
Several attempts at one shot, where turnaround is the constraint.
A photo you already have, given a camera move at delivery resolution.
One credit pool covers Nano Banana images and Seedance and Veo video. The cost shows before every run, the safety check runs before the model does, and a failed run is refunded automatically. Use a subscription for ongoing work, or a one-time pack when you just need to top up.
What's included
Secure checkout by Stripe. Card details never touch our servers.
What's included
Secure checkout by Stripe. Card details never touch our servers.
What's included
Secure checkout by Stripe. Card details never touch our servers.
What's included
Secure checkout by Stripe. Card details never touch our servers.
One-time top-ups — buy extra credits any time you run low.
What's included
Secure checkout by Stripe. Card details never touch our servers.
What's included
Secure checkout by Stripe. Card details never touch our servers.
What's included
Secure checkout by Stripe. Card details never touch our servers.
Charges appear as “SAYMAKER AI” on your card statement. You can cancel any time from Settings → Billing; cancellation takes effect at the end of the period you already paid for. Operator details, the full model list, and the refund window are on the about page.
Powered by
Use one balance across every image and video model on the shelf — the main ones are listed below — and check the credit cost before each request.
Video models
Image models
Model credit guide
A failed run is refunded automatically. The exact estimate in the generator varies by model, length, resolution, audio, and number of images.
| Type | Model | Credit cost |
|---|---|---|
| Video | Seedance 2.5 | The long-take tier, priced per second: 5s 480p ≈ 525 credits, 5s 720p ≈ 1,185. A full 30s take runs ≈ 3,150 at 480p and ≈ 7,090 at 720p. |
| Video | Seedance 2.0 | Supplying a starting frame or clip costs less than starting from words alone: 6s 720p ≈ 565 credits from an image, ≈ 925 from text. Scales with resolution and length. |
| Video | Seedance 2 Fast | Faster and lower cost. 6s 720p text-to-video ≈ 745 credits. |
| Video | Seedance 2 Mini | The cheapest tier of the Seedance 2 family. 6s 720p ≈ 465 credits, 6s 480p ≈ 215 credits. |
| Video | Seedance 1.5 Pro | Audio doubles the rate. 6s 720p ≈ 85 credits silent, ≈ 160 with audio; 1080p ≈ 175 and ≈ 340. |
| Video | Veo 3.1 | Billed per video, not per second, and the tier you pick is the whole price: Lite ≈ 115 credits at 720p and ≈ 135 at 1080p, Fast ≈ 225 at 720p, Quality ≈ 940 at 720p. |
| Video | Kling 3.0 | Audio raises the rate by about half. 6s 720p ≈ 320 credits silent, ≈ 455 with audio; 1080p ≈ 405 and ≈ 610. |
| Video | MiniMax H3 | Fixed 2K, no resolution ladder. Priced per second — a 5s clip ≈ 395 credits. |
| Image | Nano Banana 2 | Generate or edit from text and images. 20 credits per 1K image, 30 at 2K, 45 at 4K. |
| Image | Nano Banana Pro | Consistent run times across generations. 30 credits per 1K or 2K image, 55 at 4K. |
| Image | Nano Banana 2 Lite | Faster, simpler variant, and the everyday editing price: a flat 15 credits per image at every resolution. |
| Image | GPT Image 2 | The lowest-cost premium image model here. 10 credits per 1K image, 15 at 2K, 30 at 4K. |
| Image | GPT Image 2.5 Flare | OpenAI's newest image model, on the fast tier. 25 credits per 1K image, 40 at 2K, 60 at 4K — same price whether you generate or edit. |
| Image | GPT Image 2.5 Sunburst | The 2.5 tier for edits that touch only what you named. Same price as Flare: 25 credits per 1K image, 40 at 2K, 60 at 4K. |
| Image | Seedream 5.0 Lite | Flat pricing — 20 credits per image whether you generate or edit. |
Common questions about the fast variant of Kling 3.0.
No. This model has no audio field at all. Kling 2.6 and Kling 3.0 both generate sound with the shot as an option; Turbo does not.
About 405 credits for 6 seconds at 720p and about 510 at 1080p. Billing is per second, so a 10-second clip is roughly two thirds more.
Same generation, tuned for turnaround. Kling 3.0 adds multi-shot sequences, a 4K tier and the sound option; Turbo trades those for speed and a simpler request.
For the clip you publish, usually. For the attempts before it, no — resolution has no bearing on whether the motion you described actually happens.
Video generation is not deterministic; the same prompt produces a different take on each run. Testing at 720p is the cheap way to absorb that.
Credits are returned automatically, unless the request broke the content policy.
Turbo trades the audio option away for speed at a similar per-second rate. If the clip will be scored in an editor anyway, Turbo gets you there sooner; if you want sound out of the box, stay on Kling 3.0.
Describe the camera move and the subject move, test at 720p, and run the keeper at 1080p.