YouTube API Quota: How It Works and How to Request an Extension
How the YouTube Data API quota works in 2026: separate upload and search buckets, the midnight Pacific reset, and how the audit and quota extension works.
If you build anything on the YouTube Data API, a script that uploads your own videos, an internal tool for a team, or a product with users, the quota decides how much it can do in a day. It's also the reason most YouTube upload tools have daily caps. This post explains how the quota is counted today, what changed in 2026, and how the audit and quota extension process works, using Google's own documentation.
How the quota is counted in 2026
Google's revision history notes that from June 1, 2026 the API moved to more granular quota buckets, starting with videos.insert and search.list. Per Google's quota calculator, a project's default allocation is now:
- 100 videos.insert calls a day, in their own bucket. Each upload is one call.
- 100 search.list calls a day, also in their own bucket.
- 10,000 units a day shared by every other method.
Inside the 10,000 units, reading is cheap and writing costs more. Reading a video's or channel's details (videos.list, channels.list) costs 1 unit; updating a video (videos.update) or setting a thumbnail (thumbnails.set) costs 50. The calculator lists every method's cost, and Google notes the defaults can change, so check it before you plan.
Quotas reset at midnight Pacific time, not at midnight where you or your users are. A tool used in Europe sees its day roll over in the morning; in Asia, in the afternoon. You can watch usage on the Quotas page for your project in the Google Cloud console.
The quota belongs to the project, not the user
This is the part that surprises people. The quota is per Google Cloud project, so an app with a thousand users shares the same 100 uploads a day between all of them. It has nothing to do with each user's own channel, which has a separate daily upload limit set by YouTube (upload limits explained). Both limits apply at once: an upload through an app needs room in the app's project quota and in the channel's own limit.
Using less quota
- Cache what you read. Channel and video details don't change every minute; store them briefly instead of calling list methods on every page load.
- Request only the parts you need. Ask for the resource parts you'll use rather than everything.
- Batch IDs. list methods accept several IDs in one call.
- Avoid search.list where you can. With only 100 calls a day, reading a channel's uploads playlist is often a better way to list its videos.
- Fix metadata with updates, not re-uploads. A re-upload spends an upload call; videos.update spends 50 of the shared units.
- Budget uploads when they start. The request that opens a resumable upload session is the videos.insert call, so count it then, whether or not the file finishes.
Requesting more: the audit and quota extension
Google's Quota and Compliance Audits guide says that to get more than the default allocation, a project must first pass an audit showing it complies with the YouTube API Services Terms of Service and Developer Policies. The steps:
- Read the Developer Policies and make sure your app follows them: how you store data, how you display YouTube content, your privacy policy, and how users revoke access.
- Fill in the Audit and Quota Extension Form. It asks about your organization, contacts, API clients and use cases, and wants per-project quota figures with a justification for each.
- Wait for YouTube's API Services team, which Google says will contact you. Google doesn't publish a processing time.
- Answer follow-up questions. Incomplete forms cause delays, Google warns, so send screenshots or a demo video of the flow that uses the API if asked.
- Keep within the approved use. Extra quota applies only to the approved use case; a changed use case needs a new audit submission.
Google also runs periodic re-audits, and the same form handles a project that passed an audit in the last 12 months and needs more quota, or one asked to re-audit that doesn't need more.
What not to do
Don't split one app across several Cloud projects to multiply the default quota. The Developer Policies prohibit creating multiple projects or apps to artificially acquire more quota, and Google says violations can lead to reduced quota or revoked API keys.
Why upload tools cap your uploads
Any tool that uploads for you is a Cloud project with this quota. Until Google approves more, 100 uploads a day is shared by every user of that tool, so tools set daily caps per account and reserve capacity so one heavy user can't use up everyone's day.
Zeotra is in exactly that position, and says so: its project has the default 100 uploads a day, shared by every Zeotra user, until Google approves more. That's why each plan has a daily cap alongside its monthly allowance: 3 a day on Free, up to 15 on Pro ($19/month) and up to 40 on Premium ($49/month), with part of each day reserved for paid plans. Every limit is on the pricing page.
If you're deciding between building your own uploader and using one, the bulk upload guide compares the API route with Studio and CSV-based tools.
Quick answers
Does an upload still cost 1,600 units?
Not in Google's current quota table. Uploads now have their own videos.insert bucket of 100 calls a day, separate from the 10,000 shared units.
Can I pay for more quota?
Google's documentation describes the audit and extension form as the way to get more; it doesn't list a paid option.
What error do I get when the quota runs out?
A quotaExceeded error. It clears when the quota resets at midnight Pacific time.
Don't want to build and audit your own uploader? Upload and schedule to your channels with Zeotra, starting on the Free plan.
Start free