How-To Guide

How much does the YouTube API cost?

Google charges nothing for the YouTube Data API; quota meters it: 100 searches, 100 uploads, 10,000 units a day, plus the audit and engineering around them.

9 min read

By the Superdirector editorial team. Google's YouTube Data API documentation, including the Quota Calculator, getting-started guide, revision history, videos.insert reference, audits guide, developer policies and API Services terms, was fetched on November 14, 2026; the calculator's own last-updated stamp reads November 12, 2026 UTC. Third-party prices are as each vendor's page prints them on that date.

At a glance

How much does the YouTube API cost?

Zero dollars to Google. No rate card, no per-call fee and no paid tier appears in any official YouTube Data API page. The meter is quota: 100 search.list calls, 100 video uploads and 10,000 units combined for everything else, per project per day, resetting at midnight Pacific Time, with every request, invalid or not, costing at least one unit. What actually costs is the engineering around it: consent verification for upload scopes, the compliance audit on the road to more quota, the resumable upload flow, and the retry discipline that keeps a drained bucket from draining your next one.

  • Google's fee is $0 on every line of this guide; the [Quota Calculator](https://developers.google.com/youtube/v3/determine_quota_cost)'s allocation line gives a project 100 search.list calls, 100 videos.insert calls and 10,000 units a day combined for all other endpoints.
  • Two dated changes that old guides miss: December 4, 2025 moved an upload from approximately 1,600 units to approximately 100, and June 1, 2026 gave uploads and searches their own 100-call buckets at 1 unit per call.
  • More quota has exactly one documented path: an API compliance audit plus the Audit and Quota Extension Form, with no published turnaround and a one-project-per-client rule that bars sharding.
  • When the calendar matters more than the code, managed layers price the maintenance for a subscription: wrappers from $19 a month on the pages read for this guide, or an operated account at $199 a month (ours).
Three stacked daily quota meters, one per bucket: 100 search calls, 100 uploads and 10,000 shared units per Google Cloud project.

The 2026 meter is three buckets, not one price, and all three reset at midnight Pacific Time. Original diagram from Google's Quota Calculator allocation line, read November 14, 2026.

Superdirector

Make it work for your brand

Find it. Remake it. Post it. Superdirector turns the viral formats in your niche into your brand's carousels, X posts and video scripts, and keeps the calendar full.

What Google charges for the YouTube Data API

The search you just did probably expected a price table. Google never built one for the Data API. The YouTube Data API is Google's programmatic interface to YouTube resources: videos, channels, playlists, comments, captions and the uploads endpoint, and Google meters it with quota instead of money. Its own getting-started guide sets the tone plainly: the quota exists so that developers use the service as intended and do not create applications that unfairly reduce service quality or limit access for others. Nothing in the seven official pages behind this guide, from the Quota Calculator to the API Services terms, prints a price, a per-call fee or a paid tier.

So the honest answer to what the YouTube API costs is that Google's invoice total is zero on every line. The bill that actually arrives is everything the zero implies: a Google Cloud project and credentials, verification review before upload scopes face the public, a compliance audit before quota grows, and the engineering to live inside three daily ceilings. Here is the line-item view, with Google's fee next to what each row really asks of you:

Line itemGoogle's feeWhat each line item really asks of you
API calls, reads and writes$0Every request, including an invalid one, costs at least one quota unit, so careless retries charge your own budget rather than any card
Google Cloud project and API key$0Setup work: enable the YouTube Data API, create credentials, and keep to exactly one project per API client under the developer policies
OAuth consent screen verification$0A privacy policy, a homepage, scope justifications and a demo video when upload scopes go public; one analysed guide's reading of Google's pages adds that unverified apps show a warning screen and cap out at 100 new users in total
API compliance audit$0Calendar time with no published turnaround; required before any quota beyond the default allocation, and YouTube re-runs audits periodically
Upload engineering$0A resumable session rather than a single call: metadata first, chunked bytes next, and a range probe to resume after any interruption, plus caps like 100-character titles and 5,000-byte descriptions
Data duties after revocation$0Stored authorized data must be deleted within 30 calendar days of a consent revocation, and scraping YouTube is barred to API clients outright
More quota$0Not purchasable at all: the documented path is the audited extension form, which Google reviews against no published timeline

Two rows in that table decide most of the calendar, and both come from Google's own pages. Verification is the gate on the upload scope: an analysed guide quotes YouTube's OAuth documentation directly, that a public application using scopes which permit access to certain user data must complete a verification process, and the review of that submission is the only timing figure anywhere in the stack, typically three to five business days on that guide's reading of Google's pages. The audit is the gate on quota itself, and it answers to no published clock at all, which the extension section below covers.

Map your workload onto the three quota buckets

The metering is three buckets, not one price. Google's Quota Calculator states the default allocation in one sentence: 100 search.list calls, 100 videos.insert calls, and 10,000 units per day combined for all other endpoints. The two dedicated buckets are new: the revision history records that on June 1, 2026 the Data API began transitioning to a granular quota system covering smaller sets of methods, starting with videos.insert and search.list, and Google framed the change as simplifying the path to quota increases by letting YouTube verify and approve requests based on specific method usage.

The per-method costs are the part worth keeping at hand. Reads are the cheapest row: videos.list, channels.list, playlistItems.list and commentThreads.list each cost 1 unit against the shared pool, so one batched videos.list call that reads 50 video IDs costs one unit. Most writes cost 50 units: videos.update, comments.insert, playlistItems.insert and the thumbnail call. Captions are the expensive rows still on the shared pool, with captions.insert at 400 units and captions.update at 450. Live Streaming calls draw from quota as well, each extra page of a paginated result charges the method's cost again, and the whole allocation resets at midnight Pacific Time.

OperationWhere it billsCost as Google's calculator prints it
videos.list: read video detailsShared 10,000-unit pool1 unit
search.list: any keyword searchIts own bucket100 calls per day; each call costs 1 quota
videos.insert: upload a videoIts own bucket, named the Video Uploads bucket100 calls per day; each call costs 1 quota
videos.update, comments.insert, playlistItems.insert, thumbnail setShared pool50 units each
captions.insert / captions.updateShared pool400 / 450 units
Every request, valid or invalidWhichever bucket it reachesAt least 1 unit
Each extra page of resultsSame as the methodThe estimated quota cost again
Daily resetAll bucketsMidnight Pacific Time

The dated arithmetic explains why so many older guides mislead. Google's revision history records that on December 4, 2025 the documentation and Quota Calculator were updated for the quota cost of a video upload moving from approximately 1,600 units to approximately 100 units. Under the older single-pool rule, one analysed page's summary of the prior state, an upload burning 1,600 units of a shared 10,000, comes to roughly six uploads a day. After the two 2026 changes, the binding numbers moved from units to counts: 100 searches and 100 uploads a day per project. That is why the profiles below start from call counts rather than unit prices, and why a stale guide that warns you off over upload costs is arguing with a version of the system that no longer exists.

Price your own posting volume in quota arithmetic

Three worked profiles show where each kind of workload first runs into a wall. The arithmetic uses only the official unit costs above, and the profiles are illustrative examples for your own math, not customer results:

  1. One channel, two scheduled uploads a day, comment notifications pulled through the day and a stats read over 20 videos: two calls from the 100-call upload bucket, one batched videos.list, a handful of commentThreads.list reads and one channels.list. That is roughly five units of the shared pool and two of the 100 upload calls, so nothing binds.
  2. An agency posting once a day to ten client channels from one project: 10 of the 100 upload calls, plus one read set per channel, still about 30 to 40 units of the shared pool. Project quota is not the first wall here; the channel-level upload allowance is the one to name in your plan, because that limit returns uploadLimitExceeded independent of the project's buckets.
  3. A trend researcher running 50 search queries every morning and reading stats for the top results: about 50 of the roughly 100 daily search calls in the first pass, plus cheap batched stats reads. The search bucket is the wall, since it resets to 100 again tomorrow no matter how many unused units the shared pool holds.

The first-hit rule is easy to write down before you build anything. Count upload calls per project per day, count search calls per project per day, and price everything else in units against the shared pool. Google's own Quota Calculator page exists so you can run your full method list through it, and the Quotas page in the Google Cloud console shows a project's usage, so measure your first week rather than trusting any guide's profile, this one included.

Two operating habits keep the free tier from costing you the day after launch. First, treat quotaExceeded as a stop signal rather than a transient error: it arrives as an HTTP 403, and every retry costs at least a unit, so a tight retry loop spends tomorrow's allocation before the real traffic gets any. Second, cache and batch: one videos.list call takes up to 50 video IDs at one unit, so the pattern the arithmetic rewards is discovery through search a limited number of times per day, then cheap batched reads against the cached IDs. Both habits show up in the analysed pages as the difference between workloads that fit the default allocation and workloads that file an extension form in month one.

A workload-by-limit matrix with one accented cell in each row showing the ceiling that profile hits first, and none for the indie uploader.

Your first wall depends on the shape of the workload, and for the ten-channel agency it sits outside project quota. Original diagram from this section's three illustrative profiles, arithmetic only, with no customer outcomes.

Get more quota through the audit and extension form

Beyond the defaults, Google sells nothing and grants little by right. The audits guide is explicit: to request additional quota beyond the default allocation, you must first complete an audit showing your project complies with the YouTube API Services Terms of Service, then fill out and submit the YouTube API Services Audit and Quota Extension Form, and a member of YouTube's API Services team will contact you as soon as possible. A project that completed an audit within the last 12 months uses the same form for a further extension, and a failed audit has its own appeals form. YouTube also runs periodic audits to verify compliance over time, so the review relationship continues after approval.

What that path costs is patience, and the honest answer about time is that Google publishes no turnaround. The one community datapoint worth carrying comes from an analysed competitor page, which describes developer community reports of waits running from a few weeks to multiple months, and Google publishes no list of denial reasons either. Neither number is a promise or a rate; it is the shape one page's reporting gives. The practical plan the analysed pages agree on is to design the first month to live inside the default allocation, ship it, and apply for an extension with real usage data attached rather than projections.

The policies also decide the one obvious workaround before anyone proposes it: you cannot shard. Google's developer policies require exactly one (1) API Project for an API Client and forbid using that one project for multiple API Clients, and the terms of service bar attempting to exceed or circumvent use or quota restrictions. Inactivity carries its own clause: YouTube can disable or curtail access to a project inactive for 90 consecutive days. The rules leave one clean door for agent-built tooling, and it is written in the policies themselves: API credentials may be shared with agents operating solely on your behalf under a written duty of confidentiality, so a helper that posts for you stays policy-legal without a second project.

A four-step numbered path from shipping inside the defaults to submitting the extension form, ending in a dashed line that runs off the frame.

More quota is audit-gated, and the wait is the cost. Original diagram from Google's audits guide and developer policies, read November 14, 2026.

Decide build direct, rent a wrapper, or hand the calendar over

Build direct when YouTube is the product. The API is free, well documented and the source of truth for your own channels, and the 2026 quota changes made the default more generous for uploads than it has ever been. Direct is the right call when upload tooling and quota accounting are features worth owning, when your verified consent screen and audited project are already behind you, when you need surfaces the wrappers do not carry, such as live streaming, and when every channel you publish for is one you own, leaving headroom in 100 upload calls and 100 search calls a day.

Rent a managed layer when posting is the whole job and the audit buys you nothing. The two vendors whose pages this guide read and dated print their own numbers: Blotato's at-a-glance table puts its unified API on paid plans from $29 per month and ties creating an API key to its paid Starter plan, while Outstand's comparison lists $19 per month including 3,000 posts, then per-post pricing after that, with a $249 monthly unlimited add-on. For read-heavy research rather than posting, ScrapeIO prices lookups in credit packs from $47 for 25,000 credits on its own comparison table. Wrapper prices move often, so read the live pages before deciding, and match a per-post price to a per-seat price only after deciding which of those two jobs yours actually is.

Hand the calendar over when the real gap is an empty pipeline rather than an integration project. Superdirector (ours) is not an API product: it watches accounts and keywords on Instagram, TikTok, YouTube and X, remakes what is working into carousels, X posts and video scripts in your brand, and fills the month's calendar. On Growth, $199 per month covers one AI-run operated account, and extra accounts are $99 per month each. Publishing runs on account-level posting permission: you turn posting on once per account, after one warning that names the account, the public effect and the cost, and that standing grant carries the account's eligible posts with no approval step on any single post. The honest scope, as our own pricing page prints it: today that grant publishes eligible Instagram carousels and single X text posts, YouTube sits in the watch set and in the script-and-storyboard work, finished AI video that would post to YouTube is marked upcoming rather than live, and the $29 Starter is the hands-on version you drive yourself from Claude or ChatGPT.

Whatever you choose, keep the two cost columns apart when you compare. Google's column reads zero on every row and will keep doing so. The other column, verification patience, audit waiting, token care, retry discipline and the 30-day deletion duty, is what wrappers and operated services actually price. A team whose product is YouTube decides that column is worth owning. A team whose product needs YouTube posting to happen decides it is not. That distinction, not the API's price, is the decision this question turns on.

Frequently asked questions

How much does the YouTube API cost?

Nothing in dollars. Google charges no rate card, no per-call fee and no paid tier for the YouTube Data API, its own pages price nothing at all, and every guide read for this page agrees on what that absence means. What meters you is quota: a Google Cloud project with the Data API enabled gets 100 search.list calls, 100 video uploads and 10,000 units combined for every other method each day, and every request, even an invalid one, costs at least one unit. The invoice from Google arrives at zero and stays there. The bill is everything around the call: consent-screen verification for upload scopes, the compliance audit that unlocks more quota, and the engineering to live inside three daily ceilings.

Is the YouTube API free?

Yes, in the specific sense Google's documentation means it. Google's getting-started guide describes the quota's purpose as keeping developers from creating applications that unfairly reduce service quality or limit access for others, not as a billing system, and no official page publishes a price. Free of dollars is not free of work: OAuth verification when your app uses the upload scope, API compliance audits on the road to scale, resumable-upload engineering, and data duties such as deleting stored authorized data within 30 calendar days of a consent revocation all bill your calendar instead.

What does a YouTube API key cost?

Nothing. A key registers the project in Google's records and links API activity to it, and no page we read charges money for the key or for calling with it. What the key carries is accountability: Google's developer policies require exactly one API Project per API Client, forbid using that one project for multiple clients, and let YouTube disable or curtail access to a project inactive for 90 consecutive days.

What is the YouTube Data API cost per upload?

One quota unit per upload, against its own 100-calls-per-day bucket. Google's quota calculator states that allocation, and the videos.insert reference carries it as the Video Uploads quota bucket. Check the date on older answers: the revision history records that on December 4, 2025 the upload cost moved from approximately 1,600 units to approximately 100, and the June 1, 2026 granular-quota update then gave uploads and searches their own buckets at 1 unit per call. An upload that once billed roughly six uploads' worth of a shared pool now costs one call out of 100.

How many videos can I upload per day through the YouTube API?

100 uploads per day per Google Cloud project on the default allocation. Two other ceilings sit outside project quota, and a scheduler needs both in view: videos.insert can return uploadLimitExceeded when the channel itself has hit its own upload allowance, and one analysed guide's reading of YouTube's upload limits page adds a per-file cap of 256 GB or 12 hours, whichever is less, with 15-minute video lengths until the channel is verified.

How do I get more YouTube API quota?

One documented path. Complete an API compliance audit showing your project follows the YouTube API Services Terms of Service, then fill out and submit the Audit and Quota Extension Form; Google's audits guide says a team member will contact you as soon as possible. A repeat extension within 12 months of an audit uses the same form, and a failed audit has its own appeals form. No page publishes a turnaround, and community reporting collected on one analysed page describes waits running from a few weeks to multiple months. The durable plan is the one those pages agree on: ship inside the default allocation first, then apply with real usage data attached.

What happens when I hit the YouTube API quota?

The method stops. The errors surface as HTTP 403 with reason quotaExceeded on whatever bucket ran dry, and nothing charges you an overage, because there is nothing to bill. Retrying makes the day worse rather than better, since every request, valid or not, costs at least one unit and daily quotas reset only at midnight Pacific Time. A 400 with reason uploadLimitExceeded means something different: the channel's own allowance, a limit separate from your project's quota.

How much does a managed YouTube posting alternative cost?

On the vendor pages read and dated November 14, 2026: Blotato's at-a-glance table puts its unified API on paid plans from $29 per month and notes that creating an API key ends its free trial; Outstand's comparison lists $19 per month including 3,000 posts, then per-post rates past that, with a $249 monthly unlimited add-on; ScrapeIO prices read-only lookups in credit packs from $47 for 25,000 credits, which suits research more than posting; and Superdirector (ours) runs the calendar as an operated account at $199 per month on Growth, with the $29 Starter as the hands-on version you drive yourself from Claude or ChatGPT. Vendor prices move, so read the live pages before deciding.

Related practical guides

Run your own method list through the calculator

List the Data API methods your integration will call each day, price them against the three buckets on Google's Quota Calculator, and if uploads or searches pass 100 calls or the shared pool passes 10,000 units, start the audit before the launch, because its calendar has no published turnaround.