Runway parallel generations: 5, 15 and 20 by plan vs Sume

Runway's pricing page (read 2026-10-02) lists 5 parallel video and image generations on Standard, 15 on Pro and 20 on Max. A batch bigger than that waits its turn. Sume also limits parallel work by plan, with a concurrency ladder shown on its pricing page, and queues paid requests rather than failing them.

What Runway lists

The numbers below come from the Runway pricing page. The same page lists storage per plan; it is included because teams sizing a batch often hit both limits.

What a parallel limit means for a batch

With a limit of 5, queueing 40 clips means roughly eight waves, each as long as the slowest clip in it. Time to finish is set by the limit and the per-clip generation time, not by how many credits you hold.

The limit counts both videos and images, so image work started in the same account can use up slots you wanted for video.

How Sume handles it

Sume documents that paid generation uses queue-first admission and that workspace concurrency limits apply, with the number of jobs running at once governed by your plan's concurrency limit (see the authentication docs). The pricing FAQ says Startup adds more parallel jobs and Scale adds the highest self-serve concurrency.

Submit jobs and poll each by id; you do not need a client-side queue to stay under the limit. Sume does not publish a single Runway-style 5, 15, 20 table in the docs read for this page, so check the live plan cards for your number.

Planning a batch

If a batch deadline matters, run a small sample first to measure real per-clip time on the plan you hold.

• Divide batch size by your concurrency, multiply by the typical clip time, and add margin.
• Spread long and short clips so one slow clip does not hold a wave.
• Do not assume a higher plan is faster per clip; it only runs more clips at once.
• Keep an eye on how image jobs compete with video for the same slots.