YouTube API quota reset time: midnight Pacific, errors cost 1

YouTube Data API daily quota resets at midnight Pacific Time, according to YouTube's quota calculator page. The same page says every API request costs at least one quota point, even an invalid one, so a retry loop on a failing call drains quota without doing any work.

Everything below comes from the quota calculator and the quota and compliance audits guide, both read 2026-10-02.

The default allocation

The audits guide lists the baseline for a project: 100 search.list calls, 100 videos.insert calls, and 10,000 units per day combined for all other endpoints. Costs for methods that sit in the 10,000-unit pool are below.

Doing the sums

With only the shared pool and nothing else running, 10,000 units allows 200 thumbnail uploads (10,000 divided by 50), or 25 caption uploads (divided by 400). Mixed workloads share that one pool, so a batch that sets a thumbnail and a playlist entry per Short spends 100 units per video, which is 100 videos per day, the same number as the upload bucket.

Extra result pages also cost points, per the calculator page, so paging a list call is not free.

What midnight Pacific means in UTC

Pacific Time is UTC minus 7 hours during daylight saving time and UTC minus 8 hours after it ends. Today, 2026-10-02, daylight time still applies, so the reset lands at 07:00 UTC. Schedule a resumed queue after that moment, and avoid hard-coding the offset: use a timezone-aware library for America/Los_Angeles.

Rules for a batch worker

• Validate the request locally before sending it; an invalid call still costs a point.
• Do not retry a quotaExceeded response until after the reset.
• Check the Quotas page in Google Cloud console, which the audits guide names for monitoring usage.
• Need more than the default? That is a compliance audit, covered in the audit forms post.

Where Sume fits

Sume does not spend your YouTube quota, because it never calls the YouTube API for you. It can render the files ahead of time: a bulk run queues up to 100 Format runs, so a quota-limited day of uploads can draw from a finished stock.

The takeaway for schedulers

Because the reset is tied to a fixed clock and not to the time of your first call, a worker that starts at noon has no more quota than one that started at 00:05 Pacific. Plan the busiest part of the batch just after the reset, and keep a small reserve for retries and read calls.

Since invalid requests still cost a point, a bad payload in a loop is the most expensive kind of bug. Validate file paths, titles and field lengths locally first, then send. That one habit protects both your quota and your upload window.