Seedance 2 Mini at 1080p costs less than Seedance 2.5 at 720p: 10 s

Yes. For a 10-second 9:16 clip, Seedance 2 Mini at 1080p costs $4.26 on Sume, which is less than Seedance 2.5 at 720p at $5.78. Whether the cheaper clip is the better clip is your call, because the catalog does not rank visual quality. What it does tell you is that tier and resolution are two separate price levers, and the tier lever is the bigger one.

The ladder at 10 seconds, 9:16

All four Seedance rows are priced by video tokens. The list rates are $0.0214 (2.5), $0.014 (2.0), $0.0112 (Fast), and $0.007 (Mini) per 1,000 video tokens, and Sume bills list x 1.25, rounded up to a cent. The grid values below apply that rule to a 10-second 9:16 clip.

What the ladder says

• Mini at 1080p ($4.26) is below 2.5 at 720p ($5.78), below 2.0 at 1080p ($8.51) and below Fast at 1080p ($6.81).
• Mini at 720p ($1.89) is about one third of 2.5 at 720p. The ratio is 3.1 to 1.
• Raising 2.5 from 720p to 1080p adds $8.44 to the same clip, which is more than the whole Mini clip at 1080p.

What does not change between tiers

The four rows share the same request shape on Sume: text-to-video, image-to-video, first and last frame, reference images, videos and audio, native audio, and 21:9 through 9:16 aspect ratios, plus the same 480p, 720p, and 1080p set. What differs is the duration ceiling: Mini, Fast, and 2.0 stop at 15 seconds, while 2.5 accepts 4 to 30 seconds. If you need a 20-second clip in one job, only 2.5 on this family can do it.

A test that settles it

The price ladder is only half the decision, so spend a few dollars on a controlled test before you commit a campaign. Run the same prompt and first frame through Mini at 1080p and 2.5 at 720p. At 10 s, the two jobs together cost $10.04. Compare them on the thing your viewers see, such as text legibility or hand motion, and keep the cheaper one if you cannot tell them apart. Use Video generation with a pinned model for each so the comparison is not blurred by routing.

Check it before you run it

Every figure above is a catalog list price times 1.25, rounded up to the cent, as of 2026-10-08. Catalogs change, so before a large batch, read the current model entry in the docs and recompute the one line that matters for your case. Write the arithmetic next to the job in your own notes: list rate, seconds or characters, multiplier, rounding. If the result differs from the wallet charge by more than a cent, the catalog entry has changed, and the docs page is the place to find out why.

Run one small job first. Submit a single request with the pinned model id and the settings in the tables, poll the returned polling_url until it finishes, and compare the charge with your estimate. Then scale up. Using a pinned id for the test matters, because sume/auto never names the family, so you cannot tie its charge to the row you priced.