Seedance 2.5 costs 1.53x Seedance 2.0 at 720p for 10 seconds

A 10-second 9:16 clip at 720p costs $5.78 on Seedance 2.5 and $3.78 on Seedance 2.0 on Sume, so 2.5 costs 1.53 times as much. The extra $2.00 per clip buys a longer maximum length and nothing else that the Sume catalog lists as different.

The ratio at each resolution

Both models take 480p, 720p and 1080p. The ratio is not the same at every resolution, so check the one you will ship. Figures are Sume billable prices for a 10-second 9:16 clip, read 2026-10-08.

What the extra money buys

Comparing the catalog entries for the two models, these are the differences Sume lists.

• Maximum length: Seedance 2.5 accepts 4 to 30 seconds. Seedance 2.0 accepts 4 to 15 seconds.
• Same inputs: both list text-to-video, image-to-video, first and last frame, reference images, reference videos and reference audio, with audio output.
• Same aspect ratios: auto, adaptive, 21:9, 16:9, 4:3, 1:1, 3:4 and 9:16.
• Seedance 2.5 lists $0.0214 per 1,000 video tokens before Sume's 1.25 multiplier; Seedance 2.0 lists $0.014.

When 2.0 is the better buy

If the shot is 15 seconds or shorter, nothing in the catalog forces Seedance 2.5, so the cheaper model is the default for volume work. At 100 clips of 10 seconds and 720p, Seedance 2.0 is 100 x $3.78 = $378.00 and Seedance 2.5 is 100 x $5.78 = $578.00, a $200.00 difference.

If you need a single continuous shot longer than 15 seconds, Seedance 2.5 is the only Seedance model that can do it in one job. The alternative is two jobs joined in a Timeline render, at $0.10 per output minute, with a cut between them.

Neither model accepts a seed on Sume, so you cannot re-run a Seedance 2.0 take on 2.5 and expect the same shot. Pick the model first, then iterate on the prompt.

Check before you commit a budget

Prices come from provider list prices that can change. The submit call reserves the price up front and the poll response reports usage.cost, so a first clip on each model tells you the real figure for your settings before you queue a batch.

Prices change when the catalog changes. The figures here were read on 2026-10-08 from the Sume model docs and the pricing data behind them, and the arithmetic is shown so you can redo it if a list price moves. Before a large batch, run one clip with the exact model, resolution, aspect ratio and length you plan to use, read the cost on the result, and multiply from there. A single test clip is cheaper than finding a wrong assumption after fifty.

If a clip is one step in a longer piece, count the other steps too. Joining clips in Timeline 1.0 costs $0.10 for each started output minute, and a music bed from Music 1.0 is a fixed $0.125 per generation. Both are small next to a high-resolution clip, but they are not zero, and they belong in the total for the finished piece. Planning a Timeline job with POST /v1/timeline-1.0/plan is not billed, so you can check the structure first.