Pika next to Runway on plan limits

Pika and Runway publish their plan limits differently on 6 of the eight: queue lanes, storage, seats, project caps, unused credits and extra credits. From 3 source pages, read 2026-09-25 to 2026-10-25; no maker pays to be listed.

Fig. 1 Solid: published. Hollow: not on the pages read.

Pika and Runway, limit by limit, read 2026-10-25.
Limit	Pika	Runway
Generations at once	A number per plan	A number per plan
Priority and slow lanes	A priority queue on some plans	A slow lane that spends no credits
Storage allowance	Not stated on the pages read	A set amount per plan
How long files stay	Not stated on the pages read	Not stated on the pages read
Seats and collaborators	Not stated on the pages read	Counted per seat
Project caps	Not stated on the pages read	A project cap per plan
Unused plan credits	Reset each cycle	Roll over on top plans
Extra credits	Bought credits expire later	Extra credits on sale

Inclusion rule. The eight limits every tool on the sheet is read for. Order. The order limits take on every tool page.

1How the two compare

Runway publishes storage, seats and project caps, which Pika's pages leave out. Both publish generations at once the same way: a number per plan. Both publish queue lanes, in different forms: a priority queue on some plans for Pika, a slow lane that spends no credits for Runway. Both publish unused credits, in different forms: reset each cycle for Pika, roll over on top plans for Runway. Both publish extra credits, in different forms: bought credits expire later for Pika, extra credits on sale for Runway. Neither publishes file keeping.

2The published wording where they differ

Priority and slow lanes

Included: Priority queue
Pika, pricing page

Generations in Unlimited Mode may take longer to start and run fewer at a time; for faster generations and more simultaneous generations, switch to Credits Mode.
Runway, Unlimited Mode help article

Seats and collaborators

Pika publishes nothing on this limit.

2 to 9 members in one workspace
Runway, pricing page

Unused plan credits

Plan credits refresh each billing period and do not roll over.
Pika, pricing page

On the Max plan, up to one month of unused credits rolls over to the following month.
Runway, pricing page

Top plan
A priority queue on the top planPika, pricing page / recorded 2026-09-25
Unlimited Mode
Unlimited Mode on Pro and Max: no credits, slower to start, fewer at onceRunway, Unlimited Mode help article / since 2026-09-25 / checked 2026-10-25
Team plan
A team plan counted per seat, with 2 to 9 members in one workspaceTeam & Enterprise tabRunway, pricing page / recorded 2026-10-25
Credits FAQ
Plan credits refresh each billing period and do not roll overPika, pricing page / recorded 2026-09-25
Credits FAQ
Up to a month of unused credits rolls over on the Max plan onlyRunway, pricing page / since 2026-09-25 / checked 2026-10-25

3Pika and Runway against a third tool's published limits

SceneMixer's published figure on the limits where Pika and Runway differ, read 2026-09-25.
Limit	SceneMixer	Source
Priority and slow lanes	A priority queue on the top three tiers	SceneMixer, guide to what a paid plan changes
Storage allowance	Upload storage grows with the tier; generated files do not count	SceneMixer, guide to what a paid plan changes
Unused plan credits	Membership credits land in the same balance as bought credits and do not expire at month end	SceneMixer, guide to what a paid plan changes

Inclusion rule. Limits on which the two tools differ and SceneMixer publishes a figure or a rule. Order. The order limits take on every tool page.