15-second clip: Seedance 2.0 vs 2.5 at 720p and 1080p on Sume

A 15-second Seedance 2.0 clip costs $5.67 at 720p and $12.7575 at 1080p on Sume. Seedance 2.5 costs $8.667 and $21.32325 for the same length and tiers. Fifteen seconds is the longest Seedance 2.0 clip Sume accepts, so this is the biggest single-clip price difference between the two.

Prices for 15 seconds

Sume lists Seedance 2.0 at 4 to 15 seconds and Seedance 2.5 at 4 to 30 seconds, both at 480p, 720p and 1080p. Prices are linear in duration inside the valid range.

What the premium buys

At 720p, 2.5 costs 1.53 times 2.0, and at 1080p 1.67 times. The two other concrete differences in Sume's catalog are length, 30 seconds against 15, and a 480p-to-1080p range that both share. This page does not rank output quality; Sume's docs make no such claim and the vendor's own pages are the place to read it.

If your clips are 15 seconds or shorter and 2.0 meets your bar, the saving is $2.997 per 720p clip. Over 50 clips that is $149.85.

When to pay for 2.5

Choose 2.5 when you need more than 15 seconds in one take, since 2.0 cannot do it on Sume, or when a side-by-side test shows a difference that matters for your content. Otherwise start on 2.0 and promote only the shots that need it.

Pin either one with the model field on POST /v1/videos, see the Video generation page for the wire format and the Video Router page for the explicit catalog.

• 15 seconds or less and budget-led: Seedance 2.0.
• Over 15 seconds in one clip: Seedance 2.5, up to 30.
• Test both on one prompt before committing a batch.

Reproduce the numbers

Every Sume price on this page comes from the public catalog at https://api.sume.com/v1/catalog, which needs no API key. Fetch it, find the row for the job or model named in the table, and multiply by your own seconds, characters or image count. Sume bills the list price shown in that row, so the catalog figure is the one that applies to your balance.

All figures on this page are Sume's own, as of 2026-10-09. Prices and limits can change, so re-read the catalog and the linked docs before a large run, and keep the arithmetic in a spreadsheet so you can update it in a minute.