What a YouTube API Quota Extension Costs You in Paperwork

What is a YouTube API quota extension?

Every YouTube API quota extension is an audit outcome rather than a settings change: Google's own guide states that "if you would like to request additional quota beyond the default allocation, you must first complete an audit to show that your project is in compliance with the YouTube API Services Terms of Service." There is no slider in the Cloud Console that raises a YouTube Data API limit. There is a form, a review by YouTube's API Services team, and a decision.

That has been the rule since 1 July 2021, when YouTube's revision history announced that "all developers using YouTube's API Services must complete an API Compliance Audit in order to be granted more than the default quota allocation of 10,000 units."

The only path to more quota

Default quota

Audit and Quota Extension Form

Review by YouTube's API Services team

Decision

What is the default quota?

The default is no longer a single number, and this is the part most write-ups still get wrong. As of the 1 June 2026 change, Google's quota pages say:

"Projects that enable the YouTube Data API have a default quota allocation of 100 search.list calls, 100 videos.insert calls, and 10,000 units per day combined for all other endpoints."

Two methods now sit in their own buckets. The revision history describes it as "transitioning to a granular quota system covering smaller sets of methods, starting with videos.insert and search.list," so that YouTube can "more easily verify and approve requests based on specific method usage." A third bucket arrived on 3 June 2026 with videos.batchGetStats, which has "a quota cost of 1 unit in its own granular quota bucket" and "a default quota of 10,000 units per day."

Daily quotas reset at midnight Pacific Time.

What does each call cost?

Costs come from the Quota Calculator. Read operations are cheap, writes are not.

Method	Cost
activities.list, channels.list, videos.list, playlists.list, comments.list	1 unit
videos.getRating	1 unit
videos.update, videos.rate, videos.delete, videos.reportAbuse	50 units
playlists.insert, playlistItems.insert, subscriptions.insert	50 units
thumbnails.set, channels.update, watermarks.set	50 units
captions.insert	400 units
captions.update	450 units
search.list	100 per day, 1 unit per call
videos.insert	100 per day, 1 unit per call

Two things narrow the budget faster than the table suggests. "All API requests, including invalid requests, incur a quota cost of at least one point," so a malformed call still bills you. And pagination compounds: if a method "returns multiple pages of results, each request to retrieve an additional page of results incurs the estimated quota cost."

Where does Google's own documentation contradict itself?

On the Quota Calculator page, in two places at once.

The body text and the table both say videos.insert has a default daily limit of 100 and "the quota cost is 1 per call." The auto-generated Page Summary at the top of the same page, last updated 2026-09-04, says something else: "The table shows that methods like videos.insert have the highest cost of 1600 points." The machine-readable summary at the foot of the page repeats it, describing costs "ranging from 1 for actions such as list to 1600 for actions like videos insert."

The 1,600 figure is a fossil. The revision history entry for 4 December 2025 records that the docs were "updated to reflect a change in the quota cost of a video upload from approximately 1600 units to approximately 100 units," and the June 2026 bucket change moved uploads out of the shared pool entirely. The summary widget never caught up. If you are budgeting from the 1,600 number, you are budgeting against a cost Google retired ten months ago, on a page that still shows it.

There is a second, smaller mismatch. The Quota and Compliance Audits page carries a summary line reading "with a default allocation of 10,000 units per day," while the body of that same page lists the three-part allocation. Both were last updated 2026-09-04.

What does the form actually ask for?

One URL covers most of it: https://support.google.com/youtube/contact/yt_api_form, the YouTube API Services Audit and Quota Extension Form. Google routes three separate situations to that same address. Beginning an audit, requesting an extension after passing an audit within the last 12 months, and completing a periodic audit you were contacted about all go through it. A failed audit goes to a different address, yt_api_appeals, and a change of control goes to yt_api_change_of_control_form.

The form opens by asking you to select the reason for the request, with two options: complete a compliance audit to request additional quota, or complete a compliance audit to keep current quota if you were asked to re-audit. After that it collects, in order:

• Organisation and contact details. Full legal name, organisation legal name, parent company, a primary website URL that must start with https://, a complete legal address, a business category, an organisation size, and separate primary, technical and business contacts.
• Business model. A description of your YouTube-related work with a 100 character minimum and a 5,000 character ceiling, your target audience, your monetisation model, questions about ad placement and whether YouTube approved it, and any existing Google representative relationship.
• API client overview. The client name and whether it contains the word "YouTube," the primary access URL, privacy policy URL, terms of service URL, whether the client is publicly accessible, and demo account credentials including a username, a password and any special access instructions.
• Use cases and quota. Between one and ten projects. For each: the Google Cloud project number, use case categories, whether OAuth is required, expected daily volume, screenshots of your privacy policy, homepage and terms, conditional screenshots of the OAuth flow, upload interface or dashboard, the specific endpoints you need, and a total daily quota figure with a justification.

The demo credentials block is the one that stops teams, even though the form marks those fields optional. A closed beta, an internal tool or a client whose only entry point is behind a paywall still needs a way for a reviewer to see it working.

What does Google not document?

Everything about the outcome.

Google publishes the form URLs, the audit requirement, the default allocation and the per-method costs. It publishes no review timeline, no service level, no approval criteria, no scoring rubric, no partial-approval policy and no deadline for appeals. The Appeals Form exists for projects that "recently failed an API Compliance Audit," and "recently" is the only qualifier given.

What applicants report in public developer forums is long and variable waits, decisions that grant less quota than was asked for, and submissions that go unanswered for months. Those accounts are worth knowing about, but they are self-selected complaints rather than a published distribution, and none of them is a commitment from Google. Plan on the documented parts and treat the rest as unbounded.

The practical response is to not need the extension. Cache aggressively, use videos.list with explicit part values rather than search.list where an ID is already known, and batch reads. The same discipline applies across every network with a metered API, from Bluesky's points-based write budget to Pinterest's per-endpoint ceilings and Instagram's 100 posts per 24 hours. If your workload is publishing rather than analysis, the scheduling APIs comparison is the more useful starting point than a quota request.

Frequently asked questions

How much YouTube Data API quota do I get by default?

100 search.list calls, 100 videos.insert calls, and 10,000 units per day combined for every other endpoint. Google states that allocation on both the Quota Calculator and the Quota and Compliance Audits pages. Quotas reset at midnight Pacific Time.

Does videos.insert still cost 1,600 units?

No. Google's revision history records the change from approximately 1,600 units to approximately 100 units on 4 December 2025, and the June 2026 bucket change moved uploads into their own allocation at 1 unit per call with 100 calls a day. The auto-generated summary on the Quota Calculator page still prints 1,600, which is stale.

Can I raise my YouTube API quota without an audit?

No. Google's guide states that additional quota beyond the default requires completing an audit first. The Cloud Console shows your usage and your limits, but the limits themselves are set by YouTube's API Services team after review.

How long does a YouTube API quota extension take?

Google does not publish a timeline. The Quota and Compliance Audits page says only that "a member of YouTube's API Services team will contact you as soon as possible." Public developer reports describe waits ranging from weeks to months, with some submissions unanswered, but Google commits to no service level.

What happens if I fail the audit?

You can submit the Appeals Form at support.google.com/youtube/contact/yt_api_appeals, which covers projects that recently failed a compliance audit or were denied a quota increase. Google does not publish the criteria used in either the original decision or the appeal.

What error does YouTube return when I run out of quota?

quotaExceeded, as a 403, described in the API error documentation as "the request cannot be completed because you have exceeded your quota." A separate rateLimitExceeded appears as a 400 for sending too many requests in a given timeframe.

What is the exact URL for the YouTube API quota extension form?

Google routes audits and quota requests to https://support.google.com/youtube/contact/yt_api_form, the YouTube API Services Audit and Quota Extension Form. The same address covers three situations: starting an audit, requesting an extension after passing one within the last 12 months, and completing a periodic re-audit.

Where does a failed YouTube API audit get appealed?

A failed audit or a denied quota increase goes to the Appeals Form at support.google.com/youtube/contact/yt_api_appeals, a separate address from the main request form. Google's only stated criterion is that the project "recently failed an API Compliance Audit," with no published timeline or scoring rubric for the appeal itself.

Why does a YouTube API quota request need demo account credentials?

The form asks for a working demo account, including a username, a password and any special access instructions, because a reviewer has to sign in and watch the client behave before approving anything. A closed beta, an internal tool or a client hidden behind a paywall should still supply a working account, though the form leaves those credential fields optional.

How can I avoid needing a YouTube API quota extension at all?

Cache aggressively, call videos.list with explicit part values instead of search.list when the ID is already known, and batch reads instead of firing one request per item. That discipline keeps daily usage inside the 100 search.list calls, 100 videos.insert calls and 10,000-unit pool most projects get by default, and it sidesteps a process with no published timeline or approval criteria.