Seedance output pixel sizes: 480p, 720p and 1080p for every ratio
The frame size Seedance renders at 480p, 720p and 1080p for 21:9, 16:9, 4:3, 1:1, 3:4 and 9:16 on Sume, as used for pricing.
A Seedance clip at 720p and 16:9 is 1280x720, and 9:16 is 720x1280. The table below lists every size Sume's pricing estimator uses for the six ratios Seedance accepts, so you can match the clip to a placement before you pay for it.
The sizes come from Sume's pricing code (the same table that sizes the reservation); the docs ask you to pass resolution and aspect_ratio because size is rejected with 400 unsupported_parameter (Video generation).
Sizes
| 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 |
Price of those frames
Pixels drive the price. A 10 s Seedance 2.5 clip costs $2.6868 at 480p, $5.778 at 720p and $14.2155 at 1080p at 9:16.
Three things to know
- 480p dimensions are not exactly 854x480 or 480x854; they are the model-aligned sizes above.
- Do not send
size; useresolutionplusaspect_ratio. - Read
supported_aspect_ratiosfor the model id you call, since each model reports its own subset.
Tokens per second from the sizes
Sume prices Seedance on video tokens: width times height times seconds times 24 fps, divided by 1024. For a 16:9 frame that gives the per-second token counts below, which is why 1080p costs more than twice 720p.
| Resolution | Frame | Tokens per second |
|---|---|---|
| 480p | 864x496 | 10,044 |
| 720p | 1280x720 | 21,600 |
| 1080p | 1920x1080 | 48,600 |
Sources
Related posts
More in Developers
- Seedance reference inputs on Sume: images, video, audio per docs
Which reference types the Seedance ids accept on /v1/videos (images, video, audio, first and last frame), how references are priced, and a working request.
- 60 video jobs in Node with a promise pool: which plans need waves
A Node promise pool for Sume video jobs, plus the fit table: 60 jobs against accepted capacity on Free, Pro, Startup and Scale, and how many waves each needs.
- Sora content rules vs Sume generation_rejected: read the job events
A prompt Sora refused may behave differently on Sume. How a rejection shows up as generation_rejected, which events to read, and why you must not assume parity.
- Sora download_content vs Sume /content: the 302 and two 409 errors
OpenAI's content endpoint took variant=video, thumbnail or spritesheet. Sume's /content redirects with a 302 and returns two different 409s. How to branch.
Written by Sume