Buying a Runway plan does not mean buying unlimited universally usable generation. The service’s help center distinguishes monthly balances, purchased credits, shared workspaces and a separate API wallet.
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.
First understand the credit wallet
Runway’s official credit help article lists a one-time 125-credit Free grant and monthly plan deposits of 625 for Standard, 2,250 for Pro and Unlimited, 9,500 for Max and 6,900 per seat on Team, pooled across its workspace. Enterprise arrangements require direct confirmation. These are consumption quotas, not US-dollar price tags. The list does not establish what one subscription costs in each billing region; an individual monetary rate should remain null until its checkout terms are separately verified.
Credits can be used across different tools with differing burn rates. A plan name alone is not enough to predict the quantity of finished videos.
Why leftover credits are not all equal
The provider distinguishes credit expiry by source. Standard, Pro and Unlimited monthly plan credits expire at the billing date, while Max and Team have a limited rollover provision. Purchased credits, according to its help article, do not expire; the free one-time deposit also does not expire. This difference has a real planning effect: a team producing one large video batch every few months should not value expiring monthly credits as cash savings automatically.
Keep fields for credit origin, wallet, deposit date, spend order, rollover eligibility and expiry. Treat the absence of spend as an unused entitlement, not as revenue or a refundable asset.
Team subscriptions have shared consumption
For Team workspaces, credits are shared rather than privately owned by each member. A producer can consume capacity that colleagues were expecting for their own work. Establish workspace budgets, project labels and approvals for large batches. Workspace admins may be responsible for purchasing extra credits and enabling auto-refill, which can turn a finite monthly quota into ongoing spend.
Even when the vendor shows an estimated clip-equivalent credit number, the actual count depends on model choice, duration and retries. A forecast should count accepted outputs, including the credit cost of rejected renders.
A credit budget with arithmetic
Assume a Standard subscription has 625 available monthly credits and a selected generation tool consumes 12 credits per second. The theoretical output at that meter would be floor(625 / 12) = 52 fully billed seconds before editing, failures and other tools. This is a scenario anchored to the separately documented Gen-4.5 rate, not a promise of 52 seconds of accepted, usable footage. Ten-second clips would consume 120 credits each; clip granularity affects what fits in the pool.
If a team needs 20 clips of 10 seconds, the basic generation debit is 2,400 credits at that particular model rate, which exceeds a single Standard monthly allocation. Plan for the quota and its expiry rather than pricing all plans by their headline labels.
Website versus API: two budgets
The help center explicitly states that Runway website plan credits and Runway API credits are separate. Do not construct a universal “Runway credit” exchange rate or assume a web plan pays for programmatic generation. Record channel=consumer_subscription for website quota and channel=api for API consumption. A developer workflow may have different terms, minimum purchases and supported models.
Subscription prices can also vary with taxes, promotional terms or annual billing. No monetary subscription fee is invented here. The dated evidence is the official help-center page and it does not confirm the effective date of each plan’s commercial terms.
Pricing evidence boundary
This cost discussion concerns Runway (Runway website). 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 — 15124877443219 How do credits work (official documentation; accessed 2026-10-25)
- help.runwayml.com — 46974685288467 Creating with Gen 4 5 (official documentation; accessed 2026-10-25)