Runway Pricing 2026: Credits, Seats, and Where Runway’s Documents Contradict Each Other

Last updated: August 11, 2026

Runway sells generative media through three commercial paths: Creative subscriptions in the browser, Runway Dev for API work, and Enterprise Orders. The three do not share a credit balance, and they do not carry the same contractual terms on training, indemnity, or feature continuity. This briefing reads what Runway publishes about all three and reports where those documents contradict one another.

Verdict in one sentence: Do not approve Runway from a single pricing page. Pick the commercial path first, then preserve the rate card, seat terms, checkout state, and governing agreement you relied on.

Runway is three purchases, not one price page

The Creative web app is a bundled subscription. Standard, Pro, and Max combine interface access, storage, exports, workspace features, and a monthly credit allowance. Dividing the fee by the credits produces a useful budget number, and it is not Runway’s quoted price for a standalone credit, because the calculation assigns no value to the rest of the bundle.

Runway Dev is a separately funded path. API credits carry a published price of one cent each, purchased for an organization in the developer portal. Runway states that web app credits never appear in an API balance, and that the reverse also holds. A studio doing manual work in the browser and automation through the API funds two pools and cannot move a surplus from one to the other.

An Enterprise Order is a different contract, not a larger plan. The Enterprise Services Terms incorporate a data processing addendum, prohibit training on Customer Content, provide a limited indemnity against third-party claims that the Services infringe intellectual property, and commit that Runway will not materially degrade or remove material functionality named in an Order during its term. The consumer Terms of Use take the opposite position on each of those points: Runway may add, modify, or remove features at its discretion, and inputs and outputs may be used to train and improve its models.

The first decision is therefore the path, not the plan. A team that picks a Creative tier and later discovers it needed API automation, a DPA, or a feature-continuity commitment has bought the wrong contract rather than the wrong tier.

Sources: Runway pricing page, accessed 11 August 2026 · Runway Dev pricing docs, accessed 11 August 2026 · Runway help center, credits, accessed 11 August 2026 · Runway Enterprise Services Terms, 1 June 2026 · Runway Terms of Use, 11 May 2026

Three contradictions, and four differences that are not

The sharpest instance is the Pro plan’s Gen-4 Turbo conversion. Two Runway pages take the same plan and the same 2,250 credits and produce different amounts of video. The pricing page card gives 375 seconds. The plan-selection help article gives 7.5 minutes, which is 450 seconds. Runway’s own web and developer rate cards both list Gen-4 Turbo at five credits per second, and 450 seconds is what that rate produces. The pricing card’s figure requires six.

The other two contradictions are cleaner still. On rollover, the pricing page and the credits help article both say Max carries up to one month of unused credits forward, while the plan-selection article states that credits refresh monthly, do not roll over, and expire at the end of the billing cycle. On workspace size, the plan-selection article says Standard supports up to five editors in total; the workspaces article says a Standard workspace can add up to five additional editors. One produces a five-person ceiling and the other a six-person ceiling.

One difference was examined and is not reported as a conflict. Runway’s data security page states AES-256 encryption at rest, while the DPA security annex requires a minimum of AES-128. A service using AES-256 satisfies a floor of AES-128, so the two statements are compatible. It appears here because the classification only means something if some candidates fail it.

A now-expired promotion illustrates why a fixed campaign window has to be read with its terms rather than its banner.

Sources: Runway pricing page, accessed 11 August 2026 · Runway help center, plan selection, accessed 11 August 2026 · Runway help center, workspaces, accessed 11 August 2026 · Runway web rate card, accessed 11 August 2026 · Runway Dev rate card, accessed 11 August 2026 · Runway help center, Gen-4.5, accessed 11 August 2026 · Runway data security page, May 2025 · Runway DPA, accessed 11 August 2026 · Runway promotion terms, accessed 11 August 2026

What the subscription fee allocates per credit

Runway does not quote a standalone price for an included web credit. It quotes a plan price and an allowance. Allocating the whole fee to the allowance gives a budget quotient, and the label matters more than the arithmetic: these are allocation figures, not prices Runway published.

The spread across Creative tiers is a factor of three on the same model at the same published rate, and the only variables are the plan and the billing period. Under this allocation method, annually billed Max is the one Creative tier that sits below the Runway Dev list price, and a buyer on Standard cannot close that gap by moving credits, because the balances do not transfer.

Three further terms belong in the same budget line. Additional credits can be bought on Standard and above with a minimum purchase of 1,000. Purchased credits do not expire, while monthly plan credits do. And the Gen-4.5 documentation lists a plan requirement of Standard and higher, so the Free plan’s 125 one-time credits cannot be spent on Gen-4.5 at all.

Sources: Runway pricing page, accessed 11 August 2026 · Runway Dev pricing docs, accessed 11 August 2026 · Runway help center, credits, accessed 11 August 2026 · Runway help center, Gen-4.5, accessed 11 August 2026

Editors add a fee without adding plan credits

Runway’s plan-selection article states that its pricing is per editor. Each additional editor is charged at the workspace owner’s plan and billing cycle: $15 monthly or $144 annually on Standard, $35 or $336 on Pro, $95 or $912 on Max.

The monthly plan credits do not scale with the headcount. One set of plan credits is shared per workspace, and Runway supplies its own worked example: two people each paying $15 a month for Standard share a single allowance of 625 credits.

That example prices cleanly. Thirty dollars a month for 625 credits allocates to 4.8 cents per credit, against a Runway Dev list price of one cent. The same article tells buyers that if they want multiple sets of credits they should open separate subscriptions rather than one shared workspace.

This does not mean a second editor buys nothing. It buys account access, generating permissions, private and shared assets, and project collaboration, and Runway states that one member’s generations do not slow another’s. What it does not buy is another monthly plan-credit allowance. Procurement should budget editor licenses and generation capacity as two separate lines, and should not size the credit allowance from the headcount.

Sources: Runway help center, plan selection, accessed 11 August 2026 · Runway help center, workspaces, accessed 11 August 2026 · Runway Dev pricing docs, accessed 11 August 2026

Runway Dev is the unresolved middle contract

A consumer-versus-Enterprise comparison is the obvious way to read Runway’s contracts, and it is incomplete.

The Runway Dev portal markets a set of commitments that the consumer Terms of Use do not contain: no training on your data, ownership of outputs, IP indemnification, SOC 2 Type II, support for zero-data retention, and a 99.9 percent uptime figure. Those appear on the Dev portal under an enterprise heading.

What the public pages do not establish is which of those a self-serve Dev customer actually receives, or which accepted agreement grants them. Runway’s Enterprise Services Terms are a signed or ordered contract with named protections. The Dev portal is a marketing page. A marketing claim is not a contractual right until the accepted terms say so, and the clickwrap that a new Dev organization accepts was not obtained for this briefing.

This is the most consequential open question in the document set, and it cuts both ways. A buyer who assumes Enterprise-only protections may be overbuying. A buyer who assumes the Dev marketing page grants them may be shipping client material under terms that do not.

Sources: Runway Dev portal, accessed 11 August 2026 · Runway Enterprise Services Terms, 1 June 2026 · Runway Terms of Use, 11 May 2026

What the published subprocessor list shows

Runway publishes a subprocessor list naming 22 companies. Its opening line scopes it to personal data as defined in the customer data processing addendum, disclosed depending on which features are used. Eighteen are listed as processing in the United States, one in the United Kingdom, one in Spain, and two in Singapore.

That list is a contractual mechanism, not a courtesy. Under the DPA, customers are notified of new subprocessors through it, may object within 15 days, and may terminate the affected part of the service if no agreement follows. The DPA also disapplies the standard contractual clauses’ own subprocessor annex and relies on the page instead.

Three limits on what a reader can take from it.

First, scope. The DPA is incorporated into the Enterprise Services Terms. The reviewed documents did not establish a self-serve route to a DPA on a Creative plan, so a Standard or Pro subscriber cannot assume the list, or the objection right attached to it, applies to them. The privacy policy that does govern consumer use names Amazon Web Services as a vendor example, Stripe as its payment processor, and Google Analytics in an opt-out instruction, and carries no vendor list.

Second, mapping. The list gives company names and processing roles. It does not map model names to processors. Three providers named on Runway’s own rate card, MiniMax, Topaz AI, and Ideogram, are not listed by name; the list does include companies whose stated role is model inference, so those models may reach a customer through an intermediary. Which one is not published.

Third, the pointer. Runway’s data security page and its DPA name different addresses for the same list. Either address is a legitimate starting point, and a buyer citing the list in an approval should record which one they used and when.

Sources: Runway subprocessor list, accessed 11 August 2026 · Runway DPA, accessed 11 August 2026 · Runway privacy policy, 11 May 2026 · Runway data security page, May 2025 · Runway web rate card, accessed 11 August 2026

What this briefing could not settle

Nine questions need an account, a checkout, or an invoice, and none of them was opened for this briefing.

Two things the documents did settle, in Runway’s favor, are worth recording so the ledger is not read as one-directional. The plan lineup difference between the pricing page and the help center is explained: Runway published a migration notice stating that Max replaces Unlimited for new subscribers from 29 May 2026, with existing Unlimited accounts switching on 1 September 2026. And the encryption figures on the security page and in the DPA are compatible, as set out above.

Sources: Runway help center, plan selection, accessed 11 August 2026 · Runway help center, credit refunds, accessed 11 August 2026 · Runway data security page, May 2025 · Runway DPA, accessed 11 August 2026

What to preserve before you pay

When published documents disagree, the answer is not to pick the friendliest page. It is to record which pages you relied on, on what date, and to keep that record with the invoice. Preserve the commercial record before payment, not after a dispute.

The last item carries the most weight. Runway’s consumer terms state that it has no obligation to store customer content, and its account deletion article states that assets cannot be accessed or recovered after deletion. Do not use Runway storage as the only archive for client deliverables.

Two policy terms belong in the same file. Runway’s usage policy prohibits attempts to create content in the style of a known, living artist, and reserves the right to suspend an account for any violation. The refund article states that a denied suspension appeal ends the plan without a refund and without further access to the account or its assets.

Sources: Runway Terms of Use, 11 May 2026 · Runway help center, account deletion, accessed 11 August 2026 · Runway usage policy, 6 March 2026 · Runway help center, refunds, accessed 11 August 2026

FAQ

Sources: Runway pricing page, accessed 11 August 2026 · Runway help center, credits, accessed 11 August 2026 · Runway help center, plan selection, accessed 11 August 2026 · Runway help center, Gen-4.5, accessed 11 August 2026 · Runway Terms of Use, 11 May 2026 · Runway Enterprise Services Terms, 1 June 2026 · Runway help center, Gen-2 deprecation, accessed 11 August 2026 · Runway help center, credit refunds, accessed 11 August 2026

Methodology

This is a Tier C briefing. Tier C means document-first: claims are limited to what published documents establish, and no hands-on testing was performed. No account was opened, no generation was run, no invoice was inspected. Tier C is a scope, not a quality grade.

Twenty-three Runway-published documents were read and their page state recorded on 11 August 2026: the pricing page, the changelog, the Terms of Use, the Enterprise Services Terms, the privacy policy, the customer data processing addendum, the data security page, the subprocessor list, the usage policy, the affiliate program page, the Gen-4.5 launch page, the promotion terms, the Dev portal, the web model rate card, the developer rate card, and help center articles covering credits, plan selection, workspaces, Gen-4.5, the Gen-2 deprecation, refunds, credit refunds, and account deletion.

Differences between documents were classified before they were reported. Direct conflict means two statements about the same subject that cannot both be true. Scope drift means a general or legacy statement sitting beside a current model-specific one. Channel difference means different pricing for separately sold products. Documentation defect means broken published copy. One candidate, the encryption figures, was examined and reported as compatible rather than counted.

Dollar figures per credit and per second are FSR calculations, shown with their formula and their exclusions. They allocate the entire subscription fee to the credit allowance. The Runway Dev credit price is the one published price used.

Four things this briefing does not establish: what the product actually debits, whether Runway’s output is good, whether any arrangement complies with any law, and what a self-serve Runway Dev contract grants. Runway’s funding, valuation, and partnership claims were not examined.

Disclosure: Runway’s subprocessor list names Anthropic, PBC for content moderation and processing, and Runway’s rate card sells Anthropic’s Claude models. Future Stack Reviews uses Claude in its production workflow. Runway operates an affiliate program that pays a referral fee and provides active partners with a complimentary Max plan. Future Stack Reviews is not enrolled in it, and this briefing contains no affiliate links.

Sources: Runway subprocessor list, accessed 11 August 2026 · Runway affiliate program page, accessed 11 August 2026 · Runway web rate card, accessed 11 August 2026

Verdict

Runway’s public commercial record was fragmented on 11 August 2026, and it was not uniformly broken. Three statements contradicted each other: the Pro plan’s Gen-4 Turbo conversion, Max credit rollover, and the Standard workspace editor ceiling. Four further differences are better described as scope drift, channel pricing, a copy defect, and two pointers to one list. One apparent conflict, the encryption figures, holds up as compatible.

The evidence does not establish overbilling, deception, weak security, unlawful data processing, or poor product quality. It establishes that a buyer cannot reconcile Runway’s own documents before signing, and that the reconciliation currently falls to them.

Three instructions follow from that, and only three. Choose the commercial path before the tier, because Creative, Dev, and Enterprise carry different balances and different protections. Budget editor licenses and generation credits as separate lines, because one does not buy the other. And preserve the rate card, plan card, checkout screen, and governing agreement you relied on, because when two published pages disagree, the record of what you were shown is the only thing that resolves it.