250 Wan 3.0 clips of 7 seconds at 480p: $109.38 on Sume

Two hundred fifty 7-second Wan 3.0 clips at 480p cost $0.4375 each, $109.38 on Sume; the same set at 720p is $218.75 and at 1080p $437.50.

4 min readSume
All posts

Two hundred fifty 7-second Wan 3.0 clips at 480p cost $0.4375 each and $109.38 in total on Sume. At 720p the set is $218.75, and at 1080p $437.50. Resolution multiplies the bill; the clip count and length scale it linearly.

Cost ladder for 250 clips

Sume bills the provider list rate multiplied by 1.25 on every video model (Video Router). The figures here come from the price estimators in Sume's repository, run on 2026-10-07, and are rounded to the cent. The live numbers for your workspace are in the catalog response and on the API pricing page.

Wan 3.0, 7-second clips on Sume (read 2026-10-07)
ResolutionPer secondOne 7 s clip250 clips1,750 seconds as minutes
480p$0.0625$0.4375$109.3829.2
720p$0.125$0.8750$218.7529.2
1080p$0.25$1.7500$437.5029.2

Time as well as money

At 480p a Pro workspace, 4 jobs at once, needs 63 waves of four to submit 250 clips; Scale, at 20, needs 13. The provider's own generation time per clip decides the wall clock, so test one clip and multiply. A Pro workspace runs 4 jobs at once, Startup 8 and Scale 20 (the plans page lists the ladder), so a big batch drains in waves rather than all at once.

The sum a workspace needs on hand is not $109.38. Only jobs in flight are reserved, so a Pro workspace holds about $1.75 at a time at 480p.

  • Submit in waves sized to your plan's concurrency so you never hit queue_full.
  • Log usage.cost per job to tie the batch to a ledger.
  • Stop on the first 402 insufficient_credits and top up rather than retrying blindly.

When 480p is enough

480p is a draft or a small-screen size. It is right for storyboards, A/B hooks and thumbnails, and wrong for a final that fills a desktop player. A good pattern is 250 drafts at 480p ($109.38) and 25 finals at 1080p ($43.75), a total of $153.13.

Sume reserves the estimated amount when it accepts a job, captures it on success, and refunds the reservation if the job fails or is cancelled before capture (Usage, Generation admission). So the balance you need on hand at submit time is the price of everything in flight, not only the final total.

Set a cap before you start: from MCP, a paid tool takes dry_run=true and max_spend_usd (MCP tools and gates). Send a distinct Idempotency-Key per job so a retry replays the original job instead of charging again.

Sources

Related posts

More in Pricing

All Pricing posts

Written by Sume