Runway Seedance 2.5: 20 credits plus input at 480p; what input adds
Runway lists Seedance 2.5 at 20, 30 and 68 credits per second plus input at 480p, 720p and 1080p. Sume bills tokens; a reference video adds 15 assumed seconds.

Runway's Seedance2_5 row reads "20/30/68 plus input" for 480p, 720p and 1080p, which is $0.20, $0.30 and $0.68 per second at $0.01 per credit, plus a charge for input that the pricing guide does not quantify. I will not guess that number. On Sume, seedance-2.5 is billed by video tokens, and a request with a reference video adds 15 assumed input seconds and a 0.6 multiplier.
What Runway lists
Runway values are from the Runway API pricing guide.
| Runway row | 480p | 720p | 1080p |
|---|---|---|---|
| Seedance2_5 credits per second | 20 plus input | 30 plus input | 68 plus input |
| Dollar equivalent at $0.01 per credit | $0.20 plus input | $0.30 plus input | $0.68 plus input |
| Seedance2 (for contrast) | 36 | 36 | 40 (4K is 150) |
What input does on Sume
seedance-2.5 takes 4 to 30 seconds at 480p, 720p and 1080p. Its list is $0.0214 per 1,000 video tokens, and $0.0234 at 1080p, from Sume's pricing table. The token count is (width x height x seconds x 24) / 1024 for the output frame size. For a reference video, Sume's pricing code counts the output seconds plus 15 assumed input seconds, then multiplies the cost by 6/10.
These are estimates from the rate card. The live figure is in GET /v1/videos/models.
| Request | Billable seconds | Tokens (720p 16:9) | List cost | At list x 1.25 |
|---|---|---|---|---|
| 10 s output, no reference video | 10 | 216,000 | $4.6224 | $5.778 |
| 10 s output, reference video | 10 + 15 = 25 | 540,000 | 540 x $0.0214 x 0.6 = $6.9336 | $8.667 |
| 4 s output, reference video | 4 + 15 = 19 | 410,400 | 410.4 x $0.0214 x 0.6 = $5.2695 | $6.587 |
What the arithmetic says
With a 10 second output, a reference video raises the estimate from $5.778 to $8.667, which is a factor of 1.5 (25 seconds x 0.6 = 15, against 10). With a 4 second output the factor is 2.85 (19 x 0.6 = 11.4, against 4), because the 15 assumed seconds dominate a short clip.
So the adder hurts most on short clips: a short clip with a reference video pays for the 15 input seconds that the estimator assumes, whatever the real input length.
Practical rule
Plan around two facts: Runway's input charge is not quantified in the guide, and Sume's reference-video adder is a 15 second assumption with a 0.6 multiplier. Use a still frame or an image reference when the video is not essential, and ask for a quote from the catalog before a large run.
Sources
Related posts
More in Pricing
- Runway Tier 1 caps spend at $100 a month; Sume returns 402 at balance
Runway's API tiers cap monthly spend from $100 at Tier 1 to $100,000 at Tier 5. Sume gates paid jobs on balance and returns 402 insufficient_credits.
- Veo 3.1 audio doubles Runway credits; Omni Flash on Sume does not
On Runway, Veo 3.1 is 20 credits a second silent and 40 with audio; Omni Flash is 10. Dollar costs next to Sume's Omni Flash 1.1 rates.
- School-year lecture capture: 150 hours of transcripts, MAI vs Sume
Five 50-minute classes a week for 36 weeks is 9,000 audio minutes: about $81.00 on MAI-Transcribe-2-Streaming and $91.80 on Sume STT with 900 jobs.
- Why Seedance 2.5 at 1080p costs 2.46x its 720p price, not 2.25x
1080p has 2.25x the pixels of 720p, yet Seedance 2.5 on Sume costs 2.46x as much. The 1080p tier has its own list rate. Prices for 4, 5, 10 and 30 s.
Written by Sume