YouTube Shorts max out at 1080p: what resolution to request on Sume
YouTube's Shorts page lists a 1080p maximum. Ask Sume for 1080p, not 4K: only Gemini Omni Flash 1.1 offers 4K, and the extra pixels have no Shorts use.

YouTube's Shorts help page says you can upload Shorts with a maximum resolution of 1080p. So the resolution to send in a Sume video request for a Short is 1080p. Asking for 4K buys nothing the page says Shorts can use, and it can change the price.
Which Sume rows reach 1080p
Most rows stop at or below 1080p anyway. Only one row lists 4K. The table is from the Video Router doc.
| Model | Resolutions listed | Reaches 1080p |
|---|---|---|
| seedance-2.5 | 480p, 720p, 1080p | Yes |
| wan-3.0 | 480p, 720p, 1080p | Yes |
| kling-3 | 720p, 1080p | Yes |
| minimax-h3-max | 480p, 768p, 1080p | Yes (latent refinement from 768p) |
| minimax-h3 | 480p, 768p | No |
| gemini-omni-flash-1.1 | 360p, 720p, 1080p, 4K | Yes, and 4K |
| seedance-2-fast | 480p, 720p | No |
Why not just ask for 4K
Two reasons. First, the Shorts page names 1080p as the ceiling, so any pixels above it are not part of what the page says you can upload. Second, resolution is a pricing input. The Video Router doc lists Wan 3.0 at $0.05, $0.10 and $0.20 per second across its three tiers, as a list price before Sume's markup. A fixed tier per step means a higher tier costs more per second for the same story. For a vertical clip that people watch on a phone, 1080p is the sensible stop.
If your Short mixes clips, note that the 4K vertical vs square comparison covers which rows take which ratio at 4K.
A request that fits
Pin the ratio and the tier together so the catalog can validate both. A request with a value the model does not list returns a 400 and no job is created.
curl -X POST https://api.sume.com/v1/videos \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: short-1080p-001" \
-d '{"model":"seedance-2.5","prompt":"A hand-held shot of a ceramic mug on a desk, morning light","aspect_ratio":"9:16","resolution":"1080p","duration":8}'Drafts at a lower tier
A practical pattern is to draft cheap and finish at 1080p. Seedance 2.5, Wan 3.0 and MiniMax H3 Max all list 480p, so a draft at 480p shows you the motion and framing before you commit to the 1080p render. The prompt and the other fields stay the same; only resolution changes.
There is one catch. A different tier is a different generation, not an upscale of the draft. The 480p clip you liked will not be pixel-identical at 1080p, and this doc set says nothing about seeds: no v1 model accepts seed, so you cannot pin the result. Use drafts to judge the idea, not to approve a final frame.
That also means a 1080p ceiling on the platform side is a cap on what you need, not a target you must always reach. A 720p vertical clip is a valid choice for a quick test post. Whether the app shows it as sharply as a 1080p one is something to check on your own upload, since the help page only states the maximum.
What the page does not say
The help page gives the resolution ceiling and says nothing about bitrate, file size or codec. Treat those as unknown until you test an upload.
Sources
Related posts
More in Use cases
- YouTube Shorts series covers: one template, one edit per episode
YouTube is rolling out Shorts series with covers. Make one template with Ideogram 4.5, then change only the episode number with one edit call per episode.
- Shorts series: a season of 30-second episodes with Seedance 2.5
Shorts series are rolling out. A season of eight 30-second episodes costs $138.72 on Seedance 2.5 at 720p and $30.00 on Wan 3.0. The math and a batch loop.
- YouTube Shorts up to 3 min: how many Sume clips each model needs
YouTube's Shorts page says up to 3 minutes. One Sume request tops out at 30 s, so a full-length Short is 6 to 18 clips plus a Timeline render.
- YouTube Shorts: upload 15 at a time, so render in batches of 15
YouTube Studio lets you pick up to 15 Shorts per upload. Render a batch of 15 vertical files with Sume Timeline, and see what 15 shorts cost by length.
Written by Sume