Does Runway roll over unused credits? Only Max, for one month

Only Runway's Max plan rolls credits over, and only for one month. On Runway's pricing page, read on 2026-10-13, Max (9,500 credits a month, $76 a month billed annually, listed against a $95 crossed-out price) carries a credit rollover line; Free, Standard and Pro do not. On Sume, plan credits never roll over: they expire at the end of the billing period.

That makes the question a planning one. If your video work comes in bursts, a Runway Max month that you under-use is partly saved, while a Standard or Pro month is simply lost. This post lines the two systems up so you can decide whether rollover is worth a plan jump.

What Runway's page says, read 2026-10-13

The page lists four individual plans. Prices shown are the annual-billing rates, each next to a higher struck-through figure. Only the Max row mentions rollover, described on the page as a one-month rollover. The page does not spell out whether the rolled credits are capped, so do not assume a multiple of the monthly pool; confirm in the plan terms before relying on it.

What a month of rollover is worth

Take Max at 9,500 credits. If you use 6,000 in one month, the 3,500 left over can be spent in the next month, so the following month can reach up to 13,000 credits of headroom, based on the page's one-month wording. Without rollover, the same 3,500 would be gone.

The catch is the entry price. Max costs $76 a month against $28 for Pro, so you pay $48 more each month, $576 more across a year, to buy that safety net on top of the larger pool. Rollover only pays back if you regularly leave credits unspent. A team that burns its Pro pool every month gains nothing from it.

• Steady monthly use: rollover adds nothing, pick by pool size.
• Bursty use with quiet months: Max's one-month rollover catches part of the slack.
• One big project then nothing: a single month of rollover will not carry unused credits across a long gap.

How Sume treats unused credits

Sume's Billing and credits page says a paid plan adds its credits at the start of each billing period, and those credits expire at the end of that period and do not roll over. The Free plan is a one-time grant. A team workspace can buy more credits on its billing page; these last longer than plan credits, but they also expire, and Sume spends plan credits first, then purchased credits, soonest expiry first.

Two other rules from the same docs matter when you compare. A request reserves its credits when Sume accepts it and captures them when it completes, so a generation that fails, or that you cancel before it starts, returns its credits. And over MCP, dry_run=true returns the estimate as usage.credits without submitting anything, so you can size a month before you commit. The Errors and credits page covers the 402 insufficient_credits response when the balance falls short.

Which to pick

If you want leftovers carried forward, Runway Max is the only Runway plan that says so, and it is one month deep. If you would rather control spend per job, Sume's model is a balance you top up as a team, with failed jobs refunded, and no promise of rollover on the plan portion. Neither is better in general; they suit different cash-flow habits.

Check the Runway page again before you subscribe: plan names, pool sizes and rollover terms can change, and this table is a snapshot from 2026-10-13.