A 3-second beat on Seedance 2.5 is a 4-second job: $2.31 at 720p

A 3-second beat on Seedance 2.5 is a 4-second job: $1.074708 at 480p, $2.3112 at 720p, $5.6862 at 1080p. If the edit needs exactly 3 seconds, add the $0.02 video trim job, which makes the 720p beat $2.3312.

Prices on this page are Sume list prices as of 2026-10-08: the provider list price times 1.25, computed from Sume's pricing package and billed per output second, linear in duration inside each model's valid range. The model ids, ranges and input types come from the Video generation docs and the Video Router docs; the per-second numbers can be cross-checked in the public catalog.

The cost of the extra second

The floor is one of the first things to check when you budget short clips, because it makes the shortest job cost four seconds of the model's rate whatever length you wanted. The extra second is billed at the same rate; nothing is discounted for the part you cut away.

Cheaper ways to get a 3-second beat

Gemini Omni Flash 1.1 accepts 3 s directly: 3 s × $0.125 = $0.375 at 720p with native audio always on. Wan 3.0 accepts 2 s and up: 3 s × $0.125 = $0.375 at 720p.

If the look must come from Seedance 2.5, generate once at 4 s and keep the spare second as handles for the cut. Handles are useful for transitions, so the extra second is not always waste.

• Omni at 720p, 3 s: $0.375
• Wan 3.0 at 720p, 3 s: $0.375
• Seedance 2.5 at 720p, 4 s: $2.3112

Scaling this plan up or down

As a yardstick, the plan above is built on Seedance 2.5 at 720p, $0.5778 per second. Each extra 5 seconds adds $2.889, a further $10 of budget buys 17 more whole seconds, and the largest single job the model accepts (30 s) holds $17.334 at submit. The shortest one (4 s) holds $2.3112.

Those three numbers are enough to rescale the plan without a new table. If the plan doubles, double the totals; if a clip is shortened, subtract the seconds multiplied by the rate; and if the tier changes, swap the rate for the one in the tables above.

• Per second: $0.5778
• Per 5 s: $2.889
• Per 10 s: $5.778
• Per 30 s or the model maximum (30 s): $17.334

Check the model's fields first

Put the price table in your own config and compute the total before you call the API. The price is linear in seconds inside a model's range, so a function of rate and duration is enough, and it lets you refuse a batch that goes over a ceiling. Re-read the catalog when you plan a large run, because list prices are what Sume bills from, and they can change.

Submitting

Submit through POST /v1/videos with model, prompt, duration in whole seconds and resolution; read GET /v1/videos/models first, because supported_durations and supported_resolutions differ per model. Sume reserves the price at submit and usage.cost on the poll response is the billable amount, so the figures here are what leaves the balance.