YouTube playlistItems.insert costs 50 units: adding Shorts in bulk

Adding a video to a playlist through the YouTube Data API costs 50 quota units per call, per the playlistItems.insert page (read 2026-10-02). Against the default 10,000-unit pool for non-upload endpoints, that is at most 200 playlist adds per day, fewer if you also spend units elsewhere.

That matters for a Shorts series, where each episode is a playlist entry. Uploads sit in their own bucket now, so the playlist step, not the upload, can become the daily bottleneck.

What the page says

Facts below are from the playlistItems.insert page and the quota calculator, both read 2026-10-02.

The daily arithmetic

Per 10,000 units: 200 adds if adds are all you do. Add a thumbnail upload at 50 units per video and it falls to 100 videos fully dressed per day, which happens to match the 100-call videos.insert bucket. So a 30-episode season (30 uploads, 30 adds, 30 thumbnails, so 3,000 units outside the upload bucket) fits in one day with room to spare.

Order the work around the error list

• Add each episode once. The page says videos already in series playlists cannot be duplicated, so make your queue idempotent: store which episode went into which playlist.
• Add in episode order and let the playlist keep that order, unless the playlist uses manual sorting, since position can only be set there.
• Treat the playlist item note as a 280-character field and trim it before sending.

Where Sume fits

Sume produces the episodes, not the playlist. Use a bulk Format run to queue up to 100 runs with a concurrency window, then upload and add them yourself. Sume docs describe no YouTube playlist or series feature, so ordering and series membership stay in your own queue.

The takeaway for episode batches

Playlist adds are cheap in isolation but add up in a season-sized run. Count them next to thumbnails and caption uploads before you promise a release date, and spread a long season over two days if needed.

Since the page warns that duplicates in series playlists fail, keep a ledger keyed by episode number. If a run dies halfway, the ledger tells you which adds already happened, so the resume does not waste 50 units per retry on items that will only error.