Does a YouTube upload cost 1,600 units or 1? The pages differ
YouTube's quota calculator still shows videos.insert at 1,600 points while the method page says 1 unit in a 100-call bucket. Which to trust, and how to plan.

Neither number is a unit cost you can multiply by your whole day. Since the June 1, 2026 granular quota change, YouTube says videos.insert has its own Video Uploads bucket of 100 calls per day, at 1 unit per call, on the method page. The older 1,600-point figure still appears on the calculator page, which in the same breath says the method is limited to 100 per day.
So plan on 100 uploads per day, not 10,000 divided by 1,600. Sources: the quota calculator, the videos.insert page and the revision history, all read 2026-10-02.
Three YouTube pages, three numbers
| Page | Statement |
|---|---|
| Quota calculator | Lists 1,600 points for videos.insert, noting it is limited to 100 per day |
| videos.insert reference | 100 calls per day, 1 unit per call, in the Video Uploads bucket |
| Revision history, Dec 4, 2025 | Upload quota cost dropped from about 1,600 units to about 100 |
| Revision history, June 1, 2026 | Granular quotas begin; videos.insert and search.list charge separate buckets |
| Audits guide | Default allocation: 100 videos.insert calls per day |
How to read them together
The sequence looks like this: uploads were once priced in the shared pool at about 1,600 units; on December 4, 2025 that dropped to about 100; on June 1, 2026 uploads moved into their own bucket counted in calls. The calculator table seems to retain the old figure. That is my reading, not a statement from YouTube, so verify it where it matters.
The check that settles it is in your own project: open the Quotas page in Google Cloud console, which the audits guide names, and read the videos.insert limit and usage.
Planning rules that hold either way
- Treat 100 uploads per day as the ceiling, and keep other endpoints inside the 10,000-unit pool.
- Do not budget 1,600 units per upload against the shared pool unless your Cloud console shows that is how your project is billed.
- Re-check after any YouTube announcement; this API's quota rules have changed twice in a year.
Where Sume fits
Sume does not touch your YouTube quota. It can prepare up to 100 videos in one bulk Format run, which lines up with one day's upload bucket. The upload itself, and any quota increase through an audit, are on the YouTube side.
The takeaway
When two official pages conflict, the method reference and your own Cloud console win over a table that may lag. Build your queue around the 100-call bucket, log your actual usage from the Quotas page for a week, and adjust. If a plan needs more than 100 uploads in a day, the route is the audit form, not a cleverer unit calculation.
Sources
Related posts
More in Developers
- YouTube videos.insert: 256 GB limit and containsSyntheticMedia
The YouTube Data API videos.insert method takes files up to 256 GB and a status.containsSyntheticMedia flag. A request body for an AI-made upload, with checks.
- Zed prevent_idle_sleep for agent threads and Sume jobs_wait
Zed 1.21 keeps your machine awake while agent threads run. A sleeping laptop is not a cancelled Sume job: jobs keep billing, so resume with jobs_wait.
- Which MCP server lets Claude Code or Cursor generate video and images?
MCP servers that let Claude Code and Cursor make video and images: Sume, fal, Replicate, Runway, Higgsfield. Endpoints, sign-in, billing, setup.
- Idempotency keys for AI video APIs: retry without paying twice
An idempotency key makes a retried create return the original run or job instead of a second paid one. How Sume's Idempotency-Key works on each API.
Written by Sume