Seedance pixel sizes by ratio on Sume: 864x496 at 480p, 1920x1080
Sume prices Seedance by video tokens counted from fixed pixel sizes per ratio and resolution. The size table, and why 480p 16:9 is 864x496 and not 854x480.
A Seedance clip on Sume is priced from a fixed pixel size for each resolution and aspect ratio. 16:9 at 480p is 864 x 496, not 854 x 480; at 720p it is 1280 x 720 and at 1080p 1920 x 1080. The six ratios are 21:9, 16:9, 4:3, 1:1, 3:4 and 9:16. If a Sora client requested a size such as 1280x720, Sume returns 400 unsupported_parameter on /v1/videos and wants resolution plus aspect_ratio instead; this table says what you get.
OpenAI's Sora Videos API ended on 2026-09-24 (Pondero). Anyone with a downstream layout that assumed one fixed size now needs the real numbers.
The size table
These are the dimensions in Sume's Seedance pricing code, which it uses to count video tokens. If a ratio is missing from a request, the pricing code treats auto as 16:9.
| Aspect ratio | 480p | 720p | 1080p |
|---|---|---|---|
| 21:9 | 992x432 | 1470x630 | 2205x945 |
| 16:9 | 864x496 | 1280x720 | 1920x1080 |
| 4:3 | 752x560 | 1112x834 | 1668x1251 |
| 1:1 | 640x640 | 960x960 | 1440x1440 |
| 3:4 | 560x752 | 834x1112 | 1251x1668 |
| 9:16 | 496x864 | 720x1280 | 1080x1920 |
Things to notice
Every 480p dimension is a multiple of 16 (432, 496, 560, 640, 752, 864, 992). That is why 16:9 at 480p is 864 x 496 and not 854 x 480. At 720p, 21:9 is 1470 x 630, which is wider than the 1280-pixel frame an editor might expect. And 3:4 and 9:16 are the 4:3 and 16:9 sizes turned on their side, so a vertical 720p clip has exactly the pixels of a horizontal one.
What it means for cost and layout
Because price tracks pixels x seconds, 9:16 and 16:9 cost the same at the same resolution and duration. A 4:3 720p clip has 927,408 pixels per frame against 921,600 for 16:9, close to the same. 21:9 at 720p is 926,100. The ratio does not move the price much; the resolution does, since 1080p has 2.25 times the tokens of 720p.
For layout, treat the numbers as the delivered size to design against, and verify a delivered file with video inspect rather than trusting a table. Sora-era crops and safe zones were tuned to different sizes, so re-check any text overlay positions.
Which ratios a given model lists
Not every model supports every ratio. The docs' example catalog entry for seedance-2 lists the six above, while gemini-omni-flash-1.1 takes only 16:9 and 9:16. Read supported_aspect_ratios from GET /v1/videos/models for the model you pin. The platform vocabulary is wider (3:2, 2:3, 9:21 also exist), and each model reports its own subset.
Cost at each size for 8 seconds
Using the same token formula, an 8-second 16:9 clip at 480p has 864 x 496 x 8 x 24 / 1024 = 80,352 tokens, at 720p 172,800 tokens, and at 1080p 388,800 tokens. At the seedance-2 rate of $0.014 per 1,000 tokens that is about $1.12, $2.42 and $5.44 at list, or $1.41, $3.02 and $6.80 at Sume's 1.25 multiple. Resolution is the lever; ratio is nearly free.
Sources
Related posts
More in Models
- Silent clips after Sora: which Sume models take generate_audio false
Gemini Omni Flash 1.1 rejects generate_audio false; Kling 3 prices audio on at $0.21 a second against $0.14 off; recast and motion transfer keep source sound.
- A 60-second Seedance 2.5 piece: two 30 s jobs and one last frame
Together lists multi-round extension for Seedance 2.5; Sume documents none. Build 60 s as two 30 s jobs and a last-frame handoff: $34.68 at 720p, $7.50 on Wan.
- Square 1:1 ad video: which Sume models accept it, and 4:5
Seedance, Kling, Wan and MiniMax accept 1:1 on Sume; Gemini Omni takes only 16:9 and 9:16. No video model lists 4:5, so Feed needs a crop. Table and steps.
- MiniMax H3 Max on Sume: video, lip-sync and recast, which id to call
Three Sume ids carry the MiniMax H3 Max name: minimax-h3-max for video, a lip-sync route and h3-max-recast. What each takes, its window and its rate.
Written by Sume