YouTube Shorts top out at 1080p: don't render 2160 in Timeline 1.0
YouTube's help page says Shorts can be uploaded at a maximum of 1080p. Timeline 1.0 allows up to 2160 per side, so set 1080x1920 and save render time.
YouTube's upload help page says: "You can upload Short videos with a maximum resolution of 1080p." The page also describes Shorts of up to 3 minutes. It does not list recommended bitrates or frame rates, so do not invent a spec beyond it.
Where Sume allows more
Timeline 1.0 accepts output.width and output.height as even integers from 256 to 2160. A render at 2160 on the long side exceeds what the Shorts page lists. The default, 1080 by 1920, already matches.
| Setting | Value for a Short |
|---|---|
| output.width | 1080 |
| output.height | 1920 |
| output.fps | omit, or 24, 25, 30, 60 |
| Max Shorts resolution (YouTube) | 1080p |
Rate of the render
Timeline's price is $0.10 per rounded-up output minute, so the size of the canvas does not change the bill. What it changes is file size and upload time. Confirm the live rate in GET /v1/catalog.
Frame rate
If you omit output.fps, the render takes the rate of the longest video sources. If you set a rate that differs from a source, the job resamples and reports output_fps_resamples_sources. Match the rate, or accept the judder warning.
Action
Pin 1080 by 1920 in the render template, and check one finished file before you batch.
Sources
More in Developers
- YouTube Studio takes 15 Shorts per upload: batch-render vertical clips
YouTube lets you pick up to 15 Short files at once, each up to 3 minutes, square or vertical. Submit the jobs in a Python loop with idempotency keys on Sume.
- A zsh function: submit a video prompt, keep your terminal free
A 19-line .zshrc function sends a prompt to Sume Wan 3.0 (2 s, 480p, $0.125), returns at once and saves the MP4 later. Do not name a variable status.
- 503 provider_capacity_exceeded on a transcription submit: retry?
provider_capacity_exceeded means Sume's dispatch queue is full. Retry later with the same idempotency key. It differs from 429 queue_full and 402.
- A/B test two AI video models by API with a stable hash bucket
Split production video jobs between two Sume model ids by hashing a job key, so retries keep the same arm. Python code, a duration table and a 1,000-key check.
Written by Sume