Seedance 2.5 native 4K: the press claim and what Sume accepts
A June report said Seedance 2.5 makes native 4K. Sume lists 480p, 720p and 1080p for seedance-2.5 and returns 400 for a 4K request. What to send instead.

Seedance 2.5 on Sume tops out at 1080p: the catalog row lists 480p, 720p and 1080p, and a resolution of 4K on seedance-2.5 returns a 400 ("4K is not supported by model seedance-2.5" on the Video Router). The 4K figure comes from press coverage of the June announcement, not from the model's launch post, and Sume does not expose it.
The Next Web, reporting on ByteDance's Beijing conference on June 23, 2026, wrote that Seedance 2.5 produces 30-second clips at native 4K with 10-bit colour (The Next Web, read 2026-10-02). ByteDance Seed's launch post of July 31 describes 30-second generation, references and editing, and states no output resolution (read 2026-10-02). Sume's side is Video Router and the API reference.
What does each source say about resolution?
The two vendor-side sources differ, and Sume follows neither: it exposes what its provider accepts for the model.
| Source | What it says about resolution | Note |
|---|---|---|
| The Next Web, June 23, 2026 | Native 4K, 10-bit colour, 30-second clips | Pre-launch report from the Beijing event |
| ByteDance Seed launch post, July 31, 2026 | No output resolution stated | Covers 30 s, references, editing |
| Sume Video Router docs | seedance-2.5 accepts 4-30s at 480p/720p/1080p | Catalog row on Sume |
| Sume request validation | 4K on seedance-2.5 returns 400 | Message: "4K is not supported by model seedance-2.5." |
What happens if I send 4K anyway?
A 400, before anything is reserved. On POST /v1/videos the catalog check names the value ("seedance-2.5 does not support resolution 4K."). A lowercase 4k is refused on the Video Router with "4k is not supported by Video Router v1." The only 4K generation row in the Video Router docs is gemini-omni-flash-1.1, which lists 360p, 720p, 1080p and 4K; check supported_resolutions for the current list.
How do I get 4K output from a Seedance clip?
Generate at 1080p, then upscale as a second step. Sume has a separate video upscale endpoint for that; How to upscale video to 4K covers scale factors and step order. An upscale of a 1080p render is not the same thing as native 4K generation, and this post does not claim they look alike.
For the first step, the request is the same as any other 1080p job:
curl -X POST https://api.sume.com/v1/videos \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: seedance-1080-001" \
-d '{"model":"seedance-2.5","prompt":"A slow dolly across a lit bakery counter at dawn","duration":10,"resolution":"1080p"}'Will Sume add 4K for Seedance 2.5 later?
This post cannot say. The catalog is the source of truth: GET /v1/video-router/models lists resolutions per row, so read it before you build around a limit that may change.
Sources
Related posts
More in Models
- Seedance 2.5 one-take prompt: one continuous shot, 30 seconds
Seed's Seedance 2.5 one-take prompts ask for a single continuous take with no cuts. Write the camera path in beats and send it to Sume as a 30-second job.
- Seedance 2.5 adds subtitles or music I did not ask for: fixes
Seed says Seedance 2.5 minimises stray subtitles and music. On Sume, generate_audio false drops the audio track; subtitles need prompt wording.
- Seedance 2.5 timestamp-level editing: no timestamp field on Sume
ByteDance describes timestamp-level control in Seedance 2.5. Sume documents no timestamp parameter on /v1/videos. Here is what you can send instead.
- Sume Auto video has no 1:1 or 21:9: which model to pin instead
Auto in Sume's Videos panel offers 720p or 1080p, 16:9 or 9:16 and 3 to 10 seconds. For square, ultrawide or longer clips, pin Wan 3.0, H3 or Kling 3.0.
Written by Sume