A script may call for ten seconds of action, but generating a usable ten-second clip can consume credits across several attempts. Runway Gen-4.5 gives a concrete per-second meter for building realistic budgets.
Pricing snapshot: Vendor first-party documentation checked on 25 October 2026. Original price effective date unknown unless separately declared. Amounts are published list figures, subject to tier, region, currency and eligibility.
The documented 12-credit rate
Runway’s official Gen-4.5 help page lists 12 credits per generated second and documents selectable clip durations from two to ten seconds. This is an application credit meter—not dollars per second and not an API rate. A five-second generation uses 60 credits, while ten seconds uses 120 credits before any separately charged export option. The specific plan and tool availability must still be confirmed; the page lists Standard and higher.
The source describes generation from text and image inputs, but pricing should not be mixed with older Gen-3 or newer unnamed model rates. Always attach the model version to a credit debit record.
A simple production equation
Start with accepted clips required, generated duration per attempt and expected attempts per accepted clip. Credits equal sum of all generated seconds × 12 for this documented Gen-4.5 route, plus any separate add-on charges. A hypothetical six-shot edit needing two ten-second attempts per accepted shot spends 6 × 2 × 10 × 12 = 1,440 credits on initial Gen-4.5 generations alone. It does not guarantee any clip will actually meet editorial quality criteria.
A production script’s finished runtime is not identical to generated runtime because transitions, excess footage and discarded versions change demand. A budget based solely on final timeline duration usually understates experiments.
Optional exports can add to the burn
The provider’s Gen-4.5 guide describes an additional five credits per second for certain ProRes or PNG sequence exports on eligible plans. It is an optional feature and must not be applied to every generated video. At that additive rate, exporting a ten-second qualifying clip would add 50 credits. Check the requested export path, plan eligibility and whether output is generated or post-processed.
Use separate fields for base generation and optional export charges; do not imply a mandatory 17-credits-per-second rate.
Expected cost versus a hard cap
A planning spreadsheet should allow attempt count and credit balance to vary independently. Scenario A can assume one successful attempt per shot, scenario B two, and scenario C five, while highlighting where available monthly credits run out. This is an illustrative cost model, not a statistical estimate of how often Gen-4.5 succeeds. There are no hands-on quality claims in this article.
Set a maximum number of attempts before an editor revises the reference frame, prompt or sequence design. Spending three more retries on a fundamentally unsuitable shot may be less efficient than a different production method.
Credit purchases, teams and deadlines
Runway’s website-plan credit balances can expire or roll over based on their origin and plan, and Team members use a shared pool. Plan on a per-project consumption ledger so a late-month sprint does not accidentally exhaust a separate project’s allocation. Purchased credits are not identical to monthly credits for expiry. A paid subscription’s headline credit count also cannot be automatically converted into an API wallet.
For programmatic production, seek the separate API product’s price schedule instead of reusing 12 website credits per second as if it were $0.12 or an API credit unit. Region, taxes and monthly subscription fees are separate from this model-specific usage meter.
Pricing evidence boundary
This cost discussion concerns Runway (Gen-4.5). Reproduce a quote only with its exact model or plan identifier, chargeable unit, billing region, processing mode and timestamp; a changing vendor rate card is not a permanent price guarantee. If any one of these dimensions is missing, keep the associated rate and worked scenario under editorial review instead of filling the gap with an estimate.
Sources & Further Reading
- help.runwayml.com — 46974685288467 Creating with Gen 4 5 (official documentation; accessed 2026-10-25)
- help.runwayml.com — 15124877443219 How do credits work (official documentation; accessed 2026-10-25)