AI Video Cost Per Second (2026): Kling vs Runway vs Veo vs Sora
Per-clip prices are hard to compare when providers use credits, subscriptions and different durations. This resource converts a verified advertised rate into a cost per generated second, then applies a clearly labelled user assumption for retries.
Last checked: September 2026 Runway and Gemini API reference rates are linked below. Kling and Sora are shown without invented defaults until a current, comparable public rate is verified.
What cost per second can and cannot tell you
A rate per generated second is a useful common denominator, not a quality score. Resolution, audio, duration minimums, queue time, plan fees and commercial terms can change the decision. A cheaper second is not automatically a cheaper finished shot.
Use the calculator to compare a fixed clip duration and an explicit attempt factor. If a provider only publishes a subscription or account-specific credit table, leave the rate blank until you can verify a comparable number.
Provider facts versus planning assumptions
Runway Dev documents credits purchased at $0.01 each and Gen-4 Turbo at 5 credits per second, giving a $0.05 reference rate. Google's Gemini API lists Veo 3.1 Standard with audio at $0.40 per second for 720p or 1080p; Fast and Lite have lower rates. Veo supports 4-, 6-, or 8-second clips, and 1080p requires 8 seconds. These are provider references, not a promise that every consumer plan uses the same route.
Kling and Sora are included as comparison slots, but the calculator does not silently fill them with old, regional or non-comparable figures. Retry factor is always a NotCheapAI assumption; it is not a provider failure-rate statistic.
Normalize a comparable clip
Pick the same output duration and record model, resolution, audio mode, credit rate and whether the price is API or subscription capacity. Then calculate generated cost = rate per second × duration. If a provider has a minimum charge, use the minimum rather than pretending a fractional clip is possible.
For context, compare the resulting clip with our short-form video budget guide, which models a complete workflow rather than only generation seconds.
Cost per usable second
Multiply generated cost by the number of attempts you expect for one accepted clip. This is intentionally adjustable because prompt complexity, reference images, motion and editorial standards vary. Keep the provider rate and the attempt factor visible in any client estimate.
For the official references, see Runway billing and Google Gemini API pricing. Re-check rates before committing to a project.
Common questions
Is cost per second the real cost of a video?
No. It excludes retries, editing, storage, subscriptions, minimum purchases, taxes and the value of your time unless you add them.
Why are Kling and Sora rates blank?
The page avoids substituting unverified or non-comparable numbers. Enter a current rate from the provider's official pricing surface if you have one.
Is the retry factor a provider benchmark?
No. It is an editable NotCheapAI planning assumption and should be replaced with your own measured project data.
Pricing dates and model availability move quickly. Report a correction with the official source and the affected model.
For the hardware-versus-cloud decision behind a video workflow, see our local AI video vs cloud cost comparison. For a provider-specific view of product-ad generation, see our Creatify Boreal cost analysis.