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
- Shopify rejects file names ending in thumb, icon or large
Shopify file uploads reject names ending in pico, icon, thumb, testing, small, compact, medium, large or grande. A Python rename step for batch outputs.
- Shopify image limits: 20 MB, 25 megapixels vs Sume image outputs
Shopify accepts product images up to 20 MB and 25 megapixels in JPEG, PNG, WEBP, HEIC or GIF. How that lines up with Sume image model sizes and formats.
- Sign MCP requestState for paid render approvals: user, TTL, digest
MCP says requestState is attacker-controlled. For a paid render approval, bind it to the user, an expiry and an argument digest with an HMAC. Python included.
- Slow OAuth consent and MCP timeouts: Sume's Write toggle step
MCP Python SDK v2.3.0 stops counting interactive OAuth logins against request timeouts. Here is the consent step with Sume's Write toggle that benefits.
Written by Sume