Seedance 2.5 720p on fal, 1080p on Sume: read the catalog
fal lists Seedance 2.5 Image to Video at up to 720p and 30 seconds. Sume docs list seedance-2.5 at 4-30 s and 480p/720p/1080p. Check the catalog before pinning.

Seedance 2.5 can make a 30-second clip on both platforms, but the resolution ceilings listed differ. fal's model list describes "Seedance 2.5 Image to Video" as producing a native 30-second clip at up to 720p, while Sume's docs list seedance-2.5 at 4-30 seconds and 480p, 720p or 1080p.
The two listings side by side
| Source | Length | Resolution |
|---|---|---|
| fal Seedance 2.5 Image to Video | native 30 s | up to 720p |
Sume seedance-2.5 | 4-30 s | 480p, 720p, 1080p |
Why not hard-code it
The Sume video docs say limits are not uniform across models: seedance-2.5 accepts 4-30 seconds, wan-3.0 accepts 2-30 seconds, and every other catalog model tops out at 15 seconds unless noted. Read supported_resolutions and supported_durations from the catalog rather than assuming one envelope.
The listing is one call:
curl "https://api.sume.com/v1/videos/models" \
-H "Authorization: Bearer $SUME_API_KEY"What to check in the response
Each model entry carries fields you can validate against before you submit.
supported_resolutionsfor the resolution you want to pin, such as1080p.supported_durationsfor whole-second lengths.supported_frame_imagesandsupported_input_referencesif you are starting from an image.generate_audioto see whether audio is generated.pricing_skusfor the price lines.
Submitting a pinned request
A pinned Seedance 2.5 job through the Video Router uses the documented shape. Sume bills provider list times 1.25 on every model, so reserve for the resolution and length you choose, not the cheapest listing.
curl -X POST https://api.sume.com/v1/video-router/generate \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: seedance-1080p-001" \
-d '{
"model": "seedance-2.5",
"prompt": "A vertical product clip on a desk, natural light",
"resolution": "1080p",
"duration": 12,
"aspect_ratio": "9:16",
"mode": "async"
}'Takeaway
Listings on a marketplace page and on Sume are separate catalogs, so a limit on one is not a limit on the other. If a workflow was designed around 720p because of one listing, re-read the Sume catalog before you decide whether 1080p is available for your clip.
Sources
Related posts
More in Developers
- Seedance 2.5 camera move test grid: six 4-second probes at 480p
Test dolly, orbit, crane, handheld, whip-pan and static camera prompts with six 4-second Seedance 2.5 probes at 480p for about $6.45 before a 30 s run.
- Seedance 2.5 vendor terms mapped to Sume request fields
How ByteDance and BytePlus terms for Seedance 2.5 map to Sume Video Router fields: references, first and last frame, audio, and the limits that differ.
- Tag Sentry events with the Sume job id and error category in Python
When a Sume job fails, set sume.job_id and sume.error_category with sentry_sdk.set_tag so one search finds the event, the job and the retryable flag.
- Stream Sume job progress to a browser with SSE and Node polling
Sume has no SSE or WebSocket job stream, so relay it: a small Node endpoint polls the status route and pushes text/event-stream messages to EventSource.
Written by Sume