Does Seedance 2 Fast do 1080p on Sume? No: 480p and 720p only

Seedance 2 Fast and Mini no longer list 1080p on Sume. Only seedance-2 and seedance-2.5 do. The exact refusal text and where to move a 1080p job.

4 min readSume
All posts

No. On Sume, seedance-2-fast and seedance-2-mini render 480p and 720p only; a request with resolution 1080p is refused before any job is created. The 1080p Seedance ids are seedance-2 and seedance-2.5. This follows the Video Router catalog as of origin/main commit fab7d59af (#11356).

What changed and why

Until commit fab7d59af, the catalog rows for the Fast and Mini queues listed the same 480p, 720p and 1080p as the full model. The Fast and Mini rows now list only 480p and 720p, which the catalog capabilities in the code show. Before that, /v1/videos could admit a 1080p request from the catalog for these ids.

The practical effect for a client is that the failure moves earlier. A 1080p request for either id is a 400 at submit time, not a failed job after queueing. Nothing is generated and nothing needs a refund discussion, because the request never becomes a job.

The refusal you will see

Both endpoints read the same catalog row, so both refuse the same request, but the wording differs by endpoint. The code paths are refineVideoRouterResolution in apps/api/src/schemas.ts and assertSupported in apps/api/src/videos/generate.ts.

Refusal of resolution 1080p on seedance-2-fast, from apps/api at origin/main fab7d59af
EndpointWhat you getWhere it comes from
POST /v1/video-router/generateA validation issue on resolution: "1080p is not supported by model seedance-2-fast. It renders 480p, 720p."refineVideoRouterResolution, schemas.ts
POST /v1/videosHTTP 400, code unsupported_capability, message "seedance-2-fast does not support resolution 1080p.", with details.supported listing the admitted valuesassertSupported in videos/generate.ts and the 400 mapping in routes/catalog-usage.ts

Which Seedance ids take which resolution

The docs table at docs.sume.com/models/video-router is pinned to the catalog by a test, so it matches the rows below. The same table is in docs/api/video-router.md in the repo.

Seedance rows of the Video Router catalog, apps/api/src/video-router/catalog.ts at fab7d59af
Model idResolutionsDuration
seedance-2.5480p, 720p, 1080p4 to 30 s
seedance-2480p, 720p, 1080p4 to 15 s
seedance-2-fast480p, 720p4 to 15 s
seedance-2-mini480p, 720p4 to 15 s

Where to move a 1080p job

If you need 1080p, the choice is seedance-2 or seedance-2.5. In packages/provider-pricing/src/pricing-tables.ts the provider list rate per 1,000 video tokens is 14,000 USD micros for seedance-2 and 21,400 for seedance-2.5, with a separate 23,400 for seedance-2.5 at 1080p. The video-router docs say Sume bills provider list times 1.25. Fast and Mini are 11,200 and 7,000 micros, so a 1080p job moved to seedance-2 costs more per token than it was priced at on a Fast or Mini row, which never actually rendered it.

If 720p is enough, keep Fast or Mini and send resolution 720p. You can also leave resolution out; the OpenAPI text for the router says the default is typically 720p.

  • Search your logs for jobs with model seedance-2-fast or seedance-2-mini and resolution 1080p; those are the requests that now return 400.
  • Do not retry the same body. Change the model to seedance-2 or seedance-2.5, or change the resolution to 720p.
  • Read supported_resolutions from GET /v1/videos/models instead of hard-coding a list; it is generated from the same row.

What this does not cover

Price comparisons that assumed a 1080p Fast or Mini clip describe a render the provider does not produce. This page states only the catalog rows and the refusal text; for a current price, read pricing_skus from the models endpoint.

Related posts

More in Models

All Models posts

Written by Sume