Seedance 2.5 vs 2.0 vs Fast vs Mini: price per clip at 720p on Sume

At 720p a 10-second Seedance clip costs $5.78 on 2.5, $3.78 on Seedance 2, $3.03 on Seedance 2 Fast and $1.89 on Seedance 2 Mini on Sume. Seedance 2.5 is the only one that goes past 15 seconds.

Rates

All four use the token formula, width x height x seconds x 24 / 1024. The provider rate per 1,000 tokens is $0.0214 for 2.5, $0.014 for Seedance 2, $0.0112 for Fast and $0.007 for Mini (SEEDANCE_VIDEO_USD_MICROS_PER_1000_TOKENS). Sume multiplies by 1.25 and rounds up. The ratio to 2.5 is 0.65, 0.52 and 0.33.

Using the ladder

For testing a prompt, Mini at 4 seconds is 76 cents, about a third of 2.5. If the winning idea needs more than 15 seconds, only 2.5 takes it. Note the per-tier differences in the Video Router docs: the cheaper rows have lower caps and may differ in inputs, so confirm the one you pick accepts your references.

At 1080p, Seedance 2.5 uses a higher token rate of $0.0234 per 1,000 tokens, so its 1080p clips cost more than the 720p rows here. The full 2.5 ladder, including reference-video effects, is in the reference video post.

• Mini about one third of 2.5; Fast about half.
• Only 2.5 accepts 30 seconds.
• Compare same resolution and duration.

A test-then-ship plan

A cheap workflow is to explore on Mini, then re-render the winner on a higher tier. Ten 4-second explorations on Mini cost $7.60; the final 4-second 2.5 render is $2.32, so the whole path is $9.92. Exploring on 2.5 directly would cost $23.20 for the same ten attempts.

That plan assumes the cheaper models respond to your prompt in a way that predicts the dearer one, which you should test, not assume. Prices alone cannot say whether Mini output is good enough to ship. Treat the table as a budget tool and keep the final judgement on the actual video.

How these numbers were produced

I read the rate tables in the clone of Sume's repository on 2026-10-06 and called estimateSeedanceProviderCost for the four Seedance rows, covering 720p, 9:16 clips of 4, 10 and 15 seconds. The output fields are billableAmountUsdMicros and billableAmountUsdCents; the tables show the cents.

These are estimates of the billed amount for the stated settings. Anything not in the table, such as a different frame shape, a reference input or a changed quality tier, can change the number, so run the estimate for your own request before a large batch. Where this page and the public API pricing list disagree, the pricing page and the live quote win.