Seedance 2.5 price calculator: the token formula in Python

Seedance 2.5 bills video tokens, not seconds. Width x height x seconds x 24 / 1024, then the per-1,000 rate. A 20-line Python calculator, checked against fal.

4 min readSume
All posts

Seedance 2.5 is priced in video tokens: (width x height x seconds x 24) / 1024, charged per 1,000 tokens. On fal's page the rate is $0.0214 per 1,000 tokens at 480p and 720p, and a 5-second 720p 16:9 clip is 108,000 tokens, about $2.31 (read 2026-10-09). Sume bills provider list x 1.25, so the same clip is $2.889 on Sume.

What is the formula, and does it match the vendor's examples?

fal's page publishes three worked examples. The formula reproduces the token counts: 1280 x 720 x 5 x 24 / 1024 = 108,000, and 864 x 496 x 10 x 24 / 1024 = 100,440.

The 30-second 720p example on the same page is about $13.87, which is 648,000 tokens at $0.0214 per 1,000.

fal Seedance 2.5 worked examples (read 2026-10-09) and the same clip on Sume (list x 1.25)
ClipTokensfal listSume
5 s, 720p, 16:9108,000about $2.31$2.889
10 s, 480p, 16:9 (864x496)100,440about $2.15$2.687
30 s, 720p, 16:9648,000about $13.87$17.334

Can I run it myself?

This script uses Sume's 16:9 pixel sizes per tier. The 1080p list rate of $0.0234 per 1,000 tokens is the value in Sume's pricing code; I did not read it on a vendor page today, so treat that row as Sume's own number.

DIMS = {"480p": (864, 496), "720p": (1280, 720), "1080p": (1920, 1080)}
LIST = {"480p": 0.0214, "720p": 0.0214, "1080p": 0.0234}  # USD per 1,000 tokens
MARGIN = 1.25  # Sume bills provider list x 1.25

def tokens(res, seconds):
    w, h = DIMS[res]
    return w * h * seconds * 24 / 1024

def sume_usd(res, seconds):
    return tokens(res, seconds) / 1000 * LIST[res] * MARGIN

for res in DIMS:
    print(res, round(tokens(res, 10)), round(sume_usd(res, 10), 2))

What does the output look like?

For a 10-second clip the script prints 100,440 tokens and $2.69 at 480p, 216,000 and $5.78 at 720p, and 486,000 and $14.22 at 1080p. That is $0.269, $0.578 and $1.42 per second. Resolution moves the price through pixel count, so 1080p has 2.25 times the pixels of 720p and costs about 2.5 times as much (the 1080p token rate is also higher).

What changes the answer?

  • Aspect ratio: the token count follows the pixel size, so each ratio needs its own DIMS entry, for example a 1:1 clip at 480p is 640 x 640, or 96,000 tokens for 10 seconds.
  • A reference video in the request adds input seconds to the token count; see the separate post on that.
  • Duration: Seedance 2.5 accepts 4 to 30 seconds on Sume, per the Video Router docs.

How do I price a whole batch?

Multiply the per-clip number by the count, then add a retake allowance. Forty 8-second clips at 720p are $184.90 ($4.622 each). The same forty at 480p are $85.98.

Sume reserves the price at submit, per the Video generation docs, so a wallet that cannot cover the reserve of the job in flight will refuse new work. Keep a buffer of one wave above the batch total rather than topping up mid-run.

  • Change DIMS if you use another aspect ratio; the 1:1 480p size is 640 x 640.
  • Treat the printed figure as an estimate and compare it with usage.cost on a finished job.
  • Re-read fal's page before a large run, since its numbers are subject to change.

Sources

Related posts

More in Pricing

All Pricing posts

Written by Sume