Paying for seconds you cut: generate 30 s, keep 12, on Sume video
Sume bills the seconds you generate, not the seconds you keep. Asking Wan 3.0 for 30 s and using 12 costs $3.75 for 12 s of use, $0.3125 per kept second.

Sume bills video by the output seconds you request, so a 30-second Wan 3.0 clip at 720p costs $3.75 even if you keep 12 seconds of it. The kept footage then costs $3.75 / 12 = $0.3125 per second, two and a half times the $0.125 list price. Ask for the length you will use, because duration is the one cost lever you control completely.
The unused-seconds table
Prices are per output second and linear in duration inside each model's valid range. The last column is the effective price of each second you keep.
| Model | Asked | Kept | Cost asked | Cost of kept length | Effective price per kept second | List price per second |
|---|---|---|---|---|---|---|
| wan-3.0 720p | 30 s | 12 s | $3.7500 | $1.5000 | $0.3125 | $0.1250 |
| wan-3.0 480p | 30 s | 12 s | $1.8750 | $0.7500 | $0.1563 | $0.0625 |
| seedance-2.5 720p | 30 s | 12 s | $17.3340 | $6.9336 | $1.4445 | $0.5778 |
| seedance-2.5 480p | 4 s | 3 s | $1.0747 | $0.8060 | $0.3582 | $0.2687 |
| gemini-omni-flash-1.1 720p | 10 s | 6 s | $1.2500 | $0.7500 | $0.2083 | $0.1250 |
Why people over-ask
Three habits cause it. Teams ask for the model's maximum so the edit has room. Teams ask for a long clip because it looks like better value per call. And a model's floor forces an overshoot: Seedance 2.5 bills a minimum of 4 seconds, so a 3-second moment costs 4 x $0.268677 = $1.0747 at 480p, an effective $0.3582 per kept second.
The first habit is the expensive one. A 10-second Omni Flash clip at 720p kept to 6 seconds costs $1.25 for $0.75 of use; the extra $0.50 buys cutting room that a 6-second request would not have had. That is sometimes worth it, but it should be a choice.
Splitting and stitching
Splitting does not save money, because the price is linear: one 12-second clip costs the same as three 4-second clips (12 x $0.125 = $1.50 on Wan 720p). It does cost extra jobs and a stitching step. A timeline compose is $0.02 and a render is $0.10 per output minute, so assembling three clips adds about $0.12 against $0 for a single clip.
So ask for the length you will use. If you do trim, the video trim job is $0.02, which is negligible against the generation line, but the seconds you cut were already billed.
A rule you can automate
Compute the duration from the script rather than choosing it by feel.
- Estimate spoken seconds from the script, add 1 second of lead-in and 1 second of tail, and round up to the model's step.
- Clamp to the model's valid range, such as 4 to 30 s for Seedance 2.5 or 2 to 30 s for Wan 3.0.
- If a shot needs only 3 seconds on Seedance 2.5, plan for the 4-second billing and use the extra second.
A budget line for it
Add a line called 'unused seconds' to your cost log. For a 30-second request that keeps 12 seconds on Wan at 720p, the line is 18 x $0.125 = $2.25 for that clip. Over 40 such clips it is $90.00 of generated footage that no viewer sees. Seeing it as its own number makes the habit visible, and a monthly figure is easier to argue about than a per-clip average.
Sources
Related posts
More in Pricing
- Poster motion: Seedance 2.5 at 3:4 costs 0.6% more than 9:16 at 720p
At 14 seconds, a 3:4 Seedance 2.5 clip is $0.05 dearer than 9:16 at 720p. Full 480p/720p/1080p table from the Sume price tool.
- Reaction clip on Wan 3.0: 3 s is $0.1875 at 480p, 50 for $9.375
A 3-second Wan 3.0 clip costs $0.1875 at 480p, $0.375 at 720p and $0.75 at 1080p on Sume. Priced from the tool, with the 2 s floor and a request body.
- Reconcile a 9-clip batch: poll usage.cost versus /v1/usage debited_usd
If 7 of 9 Seedance 2.5 clips complete at $3.4668 each, the poll sum and the ledger should both read $24.2676. How to compare them and why they differ.
- Video frames and reference ingest: no fixed price, a hold that settles
Sume bills video frames and reference ingest by Modal container seconds x list x 1.25 plus a fee, never above the hold. What to expect on the ledger and STT.
Written by Sume