YouTube show episode numbers follow publish date: render in that order
YouTube assigns Shorts episode numbers by publish date unless you set a manual playlist order. Plan your render queue so numbers match your story.

Who decides episode 5: you or the clock?
By default the clock. YouTube's help says episode numbers in a show are automatically assigned by publish date, and that if you set the order of videos in the playlist by hand, numbers follow that order instead.
So the video you upload fifth becomes episode 5 unless you intervene. For a serial Shorts series, that makes upload order part of the creative work.
| Situation | Number comes from |
|---|---|
| Default | Publish date |
| Playlist order set manually | That order |
| You edit a number or season | Other episodes renumber automatically |
A render queue that matches the numbers
The risk with AI video is that jobs finish out of order. Episode 6 may be ready before episode 4 because its clips were quicker to generate. If you publish as each finishes, the numbers drift from the script.
A simple ledger fixes it: one row per episode with the script position, the job state and a checked flag. Only the lowest unchecked row is allowed to publish next. That costs nothing and removes the guesswork about which number a finished render will get.
Separate the two stages. Render every episode into a holding list, check each one, then publish in script order. On Sume, give each render its own Idempotency-Key built from season and episode, for example s1-e04, so a repeated submit returns the existing job.
What the Timeline job gives you for the holding list
A Timeline 1.0 submit returns a job, and when it is result-ready the result holds video_url, duration_seconds, segment_count and billable_minutes. Keep those four values next to the episode number. The duration column is how you confirm each episode stays at or under 180 seconds before it goes into a Shorts-only playlist.
Warnings such as a padded or looped short source arrive in the result and are not failures, but read them before publishing.
- Record episode number, job id, video_url, duration_seconds.
- Publish in script order, one at a time.
- If you must reorder later, YouTube's manual playlist order is the lever, not re-uploading.
When a re-render is needed after publishing
YouTube's page does not say how a replacement upload is numbered, so test it on one episode and look at the show page afterward. Editing or deleting a number changes the numbers on the other episodes, per the same page. Keep the render ledger so you can tell which job produced which published episode, and note the replacement job beside the original.
Sources
Related posts
More in Use cases
- Will a YouTube show accept audio-led Shorts with no real visuals?
YouTube says videos with no visuals likely will not be considered a show. How to give narrated, audio-led Shorts a real picture track before you build a series.
- YouTube show vs Shorts series: make long-form episodes with Timeline
A Shorts series must be Shorts only, up to 180 seconds. A regular show has no such cap on that page. Render long episodes, up to 30 minutes, with Sume Timeline.
- AI album cover generator: square art at 3000×3000
Generate square album art, then upscale: Apple recommends at least 3000×3000. On Sume, generate 2400×2400 and upscale it 1.25× to reach 3000×3000.
- AI avatar for online course videos: build and update lessons
Use an AI avatar as your online course instructor: one reusable avatar, a short talking video per section, captions, and one Timeline join per lesson.
Written by Sume