Runway vs Pika Pricing 2026: The Commercial Floor Is $12 and $28, Not $12 and $8

Last updated: August 17, 2026

Runway and Pika both meter AI video generation in monthly credits, and their lowest paid plans are $12 and $8 a month on annual billing. Those numbers do not identify the cheapest plan a buyer can use for paid work. This briefing compares five things each company publishes: commercial-use terms, watermark rules, editor and account rules, credit rollover, and per-model credit costs. It does not compare video quality.

Verdict in one sentence: For a solo buyer whose requirement is watermark-free export plus a documented commercial-use permission, Runway Standard at $12 a month is the lower published entry point and Pika Pro at $28 is Pika’s, which reverses the direction of the headline prices.

The floor that matters is the requirement floor

Both companies advertise a cheap way in. Runway’s is $12 a month on annual billing. Pika’s is $8. Comparing those two numbers answers a question almost nobody is asking, because the first plan a buyer can actually use is set by entitlements, not by allowance size.

Take one common requirement: the output must download without a vendor watermark, and the vendor’s own documents must describe commercial use as permitted.

At Runway, the pricing page lists watermark-free output starting on the Standard plan. The Free plan card does not list it. Runway’s Terms of Use contain a commercial-use provision in section 4.4 that names no plan at all, so the watermark row is what moves the floor. Runway’s requirement floor for that pair is $12 a month on annual billing, $15 monthly.

At Pika, the FAQ states that a Basic or Standard subscriber cannot use their content for commercial purposes, and that Pro and Fancy downloads can be watermark-free. Both rows move together at the same step. Pika’s requirement floor for that pair is $28 a month on annual billing, $35 monthly.

If the requirement is different, the floor moves. A buyer who only needs watermark-free personal output, with no commercial intent, has a different answer. So does a buyer who accepts a watermark. The point is that the floor is a function of the requirement, and neither pricing page computes it for you.

Sources: Runway AI, Inc., pricing page, accessed 17 August 2026 · Runway Terms of Use, last updated 11 May 2026, section 4.4 · Mellis, Inc., Pika pricing page, opened in a browser and recorded 17 August 2026 · Pika FAQ, accessed 17 August 2026

Commercial use and watermark removal are separate rows

A watermark is a property of the exported file. A commercial-use permission is a condition in a contract. One does not establish the other, and treating them as a single entitlement is how buyers approve the wrong plan.

The two companies keep them separate in different ways. Pika lists both as distinct rows on every plan card and answers both in its FAQ, where they happen to change at the same step. Runway lists watermark-free output on the pricing page and handles commercial use in the Terms of Use, where the provision applies without naming a plan.

That difference has a practical consequence. Runway’s provision is subject to compliance with the agreement and to any supplemental terms, and it does not distinguish Free from Standard, Pro, or Max. It cannot be read as a plan-level grant, because it does not mention plans. Five Runway surfaces were searched for a plan-level commercial-use statement and none was located: the pricing page, the Terms of Use, the plan-selection help article, the usage policy, and the Plans, Billing and Credits help category.

Neither company’s wording resolves the questions that sit underneath commercial use. Whether a specific file is safe to publish depends on rights in the material the buyer uploaded, on trademarks and likenesses in the output, and on the buyer’s own client contract. A vendor permission tells you the plan boundary the vendor publishes. It is not an opinion about any particular deliverable, and this briefing does not offer one.

Sources: Runway Terms of Use, 11 May 2026, section 4.4 · Runway pricing page, accessed 17 August 2026 · Runway help center, which plan is right for me, accessed 17 August 2026 · Runway usage policy, accessed 17 August 2026 · Mellis, Inc., Pika FAQ, accessed 17 August 2026

What a second person costs at each company

Runway publishes a self-serve route for adding people. Its workspaces article states that Standard users can add up to five additional editors and that Pro and Max users can expand that to ten, that subscription fees are charged per user, and that all members in a workspace share one pool of credits.

Those three sentences price a team. Two editors on Standard is $24 a month on annual billing, and the workspace still has 625 monthly credits. Two editors on Pro is $56 a month, and the workspace still has 2,250. Headcount multiplies the fee. It does not multiply generation capacity.

Pika’s public consumer documents describe a different shape. Its Terms of Service state that each account may only be used by a single individual. No self-serve multi-user entitlement was located across the pricing page, the FAQ, the terms, and the support landing page. On the public route, a second person on a plan that clears the commercial requirement is a second Pro subscription, which is $56 a month on annual billing and carries its own 2,300-credit allowance.

The seam is on Runway’s side and it is easy to miss at approval time. A manager who adds a third editor to a Standard workspace has increased the bill by 50 percent and increased generation capacity by nothing. Editor licenses and generation capacity should be budgeted as two separate lines.

Sources: Runway help center, introduction to workspaces, accessed 17 August 2026 · Runway pricing page, accessed 17 August 2026 · Mellis, Inc., Pika Terms of Service, accessed 17 August 2026 · Pika pricing page, accessed 17 August 2026 · Pika support, accessed 17 August 2026

Runway’s plan-specific and generic pages disagree on rollover

Runway publishes what happens to unused monthly credits in at least six places. Three state that the Max plan carries unused credits forward for one month. Three state that monthly credits do not roll over and do not mention Max.

Recorded 17 August 2026. Every row cites a Runway-published page. No row is a claim about what Runway’s billing system does, which was not tested.

The three pages in the lower half are generic subscription pages. Read as general guidance they are not false, and read by a Max subscriber they are incomplete, because they omit an exception Runway states elsewhere on its own site. A Max buyer can therefore receive two different answers from Runway depending on which page they open, and the public record does not say which governs.

That is a documentation conflict, not evidence of a billing error. Settling it requires a Max account ledger across two consecutive cycles, or a written answer from Runway.

A seventh Runway page addresses unused annual contract credits and states that they do not roll over annually. That is a separate arrangement and is not counted above.

Sources: Runway pricing page, accessed 17 August 2026 · Runway help center, how do credits work, accessed 17 August 2026 · Runway help center, Max plan details, accessed 17 August 2026 · Runway help center, which plan is right for me, accessed 17 August 2026 · Runway help center, managing your subscription, accessed 17 August 2026 · Runway help center, will unused credits carry over, accessed 17 August 2026 · Runway help center, enterprise credits, accessed 17 August 2026

Two Runway plan cards imply a different Turbo rate

Runway prints on each plan card how many seconds of each model that allowance buys. Dividing the allowance by the printed seconds recovers the rate the card was built from.

The Gen-4.5 figures on the same three cards are internally consistent at 12 credits per second, so this is confined to one model and two cards. On the Pro card, the printed 375 seconds is what a six-credit rate produces. Runway’s own model documentation lists five, which would produce 450. A buyer sizing a month of Turbo work from the card plans for 75 seconds less than the documented rate supports.

Sources: Runway pricing page, plan cards, accessed 17 August 2026 · Runway help center, enterprise credits, accessed 17 August 2026 · Runway Dev, pricing and costs, accessed 17 August 2026

What survived when FSR read Pika’s pricing page as text

Pika’s plan cards carry the entitlement rows as text labels with a check or a cross beside each one. FSR opened the page in a browser on 17 August 2026 from a signed-out session in Japan, on the monthly billing view, and recorded the icon states directly. Basic carries crosses on watermark-free download, on purchasing additional rollover credits, and on commercial use. Standard carries a check on fast generations and on purchasing additional credits, and a cross on watermark-free download. Pro and Fancy carry checks on watermark-free download.

The same URL was then read as text on the same date by three extraction paths. In all three records the row labels came through and the check and cross states did not. One of the three, a source-bound extraction tool, reported that the meaning depended on icons it could not read and stopped rather than answer.

The scope of that observation is three extraction records on one date. It does not establish how any search engine, comparison site, or answer engine handles the page, and this briefing makes no claim about that. What it does establish is that a text reading of Pika’s pricing table, taken alone, does not carry the entitlement states, and that the readable version of the same boundary is one page away in the FAQ.

This is a different kind of finding from the Runway rollover conflict above. Runway’s is a disagreement between published statements. Pika’s is a rendering and extraction property of one page whose text version exists elsewhere on the site. They are not two halves of one pattern.

Sources: Mellis, Inc., Pika pricing page, monthly billing view, opened in a browser and recorded 17 August 2026 · Pika FAQ, accessed 17 August 2026

Why the credits do not convert between the two

Runway publishes Gen-4.5 at 12 credits per generated second, and 60 credits for a five-second generation. Pika publishes a five-second Pika 2.5 generation at 20 credits for 720p and 40 for 1080p. Those are each company’s internal meter. They are not a shared unit, and dividing a subscription price by an allowance produces a number that looks precise and compares nothing.

A defensible cross-vendor cost figure needs a matched workload: the same model class, duration, resolution, and generation mode, run the same number of times, with the number of accepted outputs recorded. That work requires two paid accounts and is outside a document-first briefing.

One comparison does hold, and it is internal to each company. Allocating a whole annual subscription across a whole allowance, Runway’s figure falls as the tier rises, from about $0.0192 per credit on Standard to about $0.0080 on Max. Pika’s rises, from about $0.0114 on Standard to about $0.0127 on Fancy. The monthly-billed prices produce the same ordering at both companies.

That changes the reason to move up a tier, separately at each company. At Runway, a higher tier lowers the allocated cost of a credit as well as raising capacity. At Pika, a higher tier raises it, so the argument for Pro or Fancy rests on the entitlement rows, capacity, and queue position rather than on a volume discount.

Sources: Runway pricing page, accessed 17 August 2026 · Mellis, Inc., Pika pricing page, accessed 17 August 2026. Per-credit figures are FSR calculations from published annual prices and allowances, and hold only if the whole allowance is consumed.

What this comparison could not settle

Two things the documents settled cleanly are worth recording so the ledger is not read as one-directional. Runway’s Gen-4.5 second-figures are consistent at 12 credits per second across all three plan cards, the annual credit totals, and the model comparison table. And Pika’s FAQ states its commercial-use boundary in plain, plan-specific language, which is more than Runway publishes anywhere on its pricing page.

Sources: Runway pricing page, accessed 17 August 2026 · Mellis, Inc., Pika FAQ, accessed 17 August 2026 · Pika pricing page, accessed 17 August 2026

FAQ

Sources: Runway pricing page, accessed 17 August 2026 · Runway Terms of Use, 11 May 2026 · Runway help center, introduction to workspaces, accessed 17 August 2026 · Mellis, Inc., Pika FAQ, accessed 17 August 2026 · Pika pricing page, accessed 17 August 2026

Methodology and source register

Tier. Tier C in the Future Stack Reviews system means document-first: primary sources read, no hands-on testing. No account was created at either company, no plan purchased, no generation run, no invoice inspected. Tier C is a scope, not a quality grade.

Freshness. Article last checked 17 August 2026. Pricing pages last checked 17 August 2026. Runway Terms of Use as dated by Runway, 11 May 2026. Help center articles carry no visible revision date on the pages read.

Source register. Runway: the pricing page in its yearly and monthly views, the Terms of Use, the developer pricing documentation, and help center articles covering how credits work, plan selection, subscription management, Max plan details, unused credit carry-over, enterprise credits, workspaces, and the usage policy. Pika: the pricing page in its yearly and monthly views, the FAQ, the Terms of Service, and the support landing page.

How Pika’s icon rows were established. The pricing page was opened in a browser from a signed-out session in Japan and the rendered icon state recorded as a screen capture showing the URL, the billing toggle, and the plan cards. Separately, the same URL was read as text by three extraction paths on the same date. Those two observations are reported separately and are not merged. The screen capture and the three raw extraction records are retained in FSR’s evidence archive.

What was extracted and what was not. Pika’s FAQ answers load client-side and did not survive FSR’s own text extraction of that page. The commercial-use and watermark sentences quoted here were obtained through separate retrieval paths and agree with each other. The subscriptions and billing section of the same FAQ was not extracted, which is why Pika’s monthly-credit rollover rule is recorded as unsettled here rather than as absent from the record.

Calculated, not read. Every per-credit figure, every implied credits-per-second figure, and every multi-seat total in this briefing was calculated by FSR from prices, allowances, and second-counts as published. None appears on a Runway or Pika surface. Per-credit figures allocate a whole subscription across a whole allowance and hold only if the whole allowance is used.

Excluded by choice. Output quality, generation speed, prompt adherence, model benchmarks, and any overall ranking of the two products. Both companies sell separately funded API products, which are named once and not analyzed. Pika’s weekly billing interval is excluded from every figure. Mobile store pricing at either company is listed as an open question rather than reported.

Legal scope. Nothing here is legal, tax, or procurement advice. No statement characterizes any document, plan, or practice at either company as lawful, unlawful, compliant, or non-compliant, and no statement assesses whether any particular output may be published or sold. Where a company’s own pages disagree, the disagreement is recorded and left open.

Disclosure. Runway’s published subprocessor list names Anthropic, PBC as a processor. Future Stack Reviews uses Claude in its production workflow. Runway operates an affiliate program; Future Stack Reviews is not enrolled. Future Stack Reviews has no commercial relationship with Mellis, Inc. This briefing contains no affiliate links.

Volatility. Prices, credit values, model names, plan structures, and document dates change without notice. Verify every figure against the linked primary sources before spending money.

Sources: Runway customer subprocessors list, accessed 17 August 2026 · Runway affiliate program, accessed 17 August 2026

Verdict by buyer type

Sources: Runway AI, Inc., pricing page, accessed 17 August 2026 · Runway Terms of Use, 11 May 2026, section 4.4 · Runway help center, introduction to workspaces, accessed 17 August 2026 · Runway Dev, pricing and costs, accessed 17 August 2026 · Mellis, Inc., Pika FAQ, accessed 17 August 2026 · Pika pricing page, accessed 17 August 2026 · Pika Terms of Service, accessed 17 August 2026