Shorts-only YouTube playlists can't be reordered: render in order
YouTube's playlist help says reordering is unavailable for Shorts-only playlists. Fix episode order before upload and render in order with fixed keys.

If you publish a Shorts series into a playlist, fix the order before you upload. YouTube's playlist help says that to reorder videos you drag them up or down in the playlist, and that this is unavailable for Shorts-only playlists (read 2026-10-07). So the render queue, not the playlist screen, is where a series gets its order.
I will not claim more about YouTube's series or show features than I read. The page covers playlists, and this post stays there.
What the playlist page says about Shorts
From YouTube's playlist help. The save path on mobile is More, then Save to playlist, then New playlist.
| Item | Page says |
|---|---|
| Save a Short | More, then Save to playlist, then New playlist (mobile) |
| Shorts chip | shows Shorts saved to the playlist; computers only |
| Reorder | drag up or down; unavailable for Shorts-only playlists |
| Privacy | chosen when the playlist is created |
What that means for your pipeline
A playlist of mixed videos can be shuffled by hand; a Shorts-only one cannot. Two practical consequences follow, and neither is something the page states outright: upload in the order you want viewers to watch, and avoid re-uploading an episode to fix a typo, because the new upload lands wherever the playlist puts it.
Fix the typo before the upload. A caption or voice error is cheap to re-render and costly to re-publish.
Render the series in order
Each Timeline 1.0 render takes an Idempotency-Key. Use a stable key per episode, so a retry replays the same job instead of producing a second file. The script prints a numbered plan with keys, which you can paste into a tracker.
titles = ["Setup", "The twist", "The fix", "Recap"]
plan = [
{"episode": i, "title": t, "idempotency_key": "series-a-ep-%02d-v1" % i}
for i, t in enumerate(titles, start=1)
]
for row in plan:
print(row["episode"], row["idempotency_key"], row["title"])Bump the version, not the number
When an episode needs a fix, change the key suffix to v2 for the new render and keep the episode number. Collect each result per Jobs and results. Sume produces the files and does not publish to YouTube in the docs I read, so the upload order is yours to keep.
Quality gate before the first upload
Because order is hard to change later, hold the whole season back until every episode passes the same checks: probe for width not above height, duration at or under 180 seconds, audio present. The classifier in the neighboring post does the first two.
A fixed gate also keeps episode three from slipping to the end of the playlist after a late fix. You can still publish on a schedule; you just publish from a folder that is already in the right order.
Sources
Related posts
More in Use cases
- Slow-motion water splash prompt for Gemini Omni: what 'slow' does
Prompt a slow-motion splash in Gemini Omni: how to word the speed, why a 5-second clip is enough, and what 360p, 720p and 1080p cost on Sume.
- Sneaker drop teaser in 6 seconds: Gemini Omni timecodes and cost
A 6-second vertical sneaker teaser built from a product photo and two timecoded beats in Gemini Omni on Sume, with 720p and 1080p prices and a Veo comparison.
- Solar roof before and after clip: Wan 3.0 first and last frame, 7 s
Send the bare roof as first_frame and the finished array as last_frame to wan-3.0. A 7-second clip costs $0.88 at 720p on Sume. Rules for matching the photos.
- How do I add a spoken tagline and sound sting to the end of an ad?
Make a 3-second spoken end tag: one 1-cent TTS job, a $0.125 music sting and a $0.01 concat to attach it to any ad read. About 14.5 cents on Sume.
Written by Sume