YouTube stopped forcing unverified API uploads to private
By ShipContent.
Published November 6, 2026.
On 2 November 2026 Google reversed the 2020 rule: videos uploaded through videos.insert from unverified API projects are no longer restricted to private. If your code omits status.privacyStatus, the video now defaults to public, although certain uploads might default to private based on creator account settings. Check your upload code today. We have not tested this yet.
Decision
Set status.privacyStatus on every videos.insert call. Show the user the visibility before the upload goes, then read back the visibility that YouTube returns.
Google changed the rule on 2 November
The revision history entry of November 2, 2026 says:
Videos uploaded through the videos.insert method from unverified API projects are no longer restricted to private viewing mode. This change reverses the policy announced on July 28, 2020, which restricted videos uploaded from unverified API projects created after that date to private viewing mode until the project completed an audit.
It then gives the default:
If you don't specify a value for the status.privacyStatus property in a videos.insert request, the uploaded video's privacy status defaults to public. Certain uploads might default to private based on creator account settings, as explained in the YouTube Help Center.
The videos.insert reference says the same about the lock: "Videos uploaded from unverified API projects are not restricted to private viewing mode." The upload guide says: "The default behavior is for an uploaded video to be publicly visible (public)."
Check these five things before your next upload
-
Search your code for
privacyStatus. If avideos.insertcall omits the field and you relied on the old lock to keep the video private, set the field today, because the lock no longer protects you. Start with unverified API projects created after 28 July 2020, since those were the ones the old rule restricted. If you test the default, use a video you are willing to have public.{ "status": { "privacyStatus": "private" } } -
Read back the visibility that YouTube returns. Do not assume the value that you sent. A status from the platform and a record in our database are two separate facts: a Reel was live on our own Facebook Page while our job did not record it as published. As a general rule for our channels, a post counts as published only after the platform confirms it, and our channels overview says "a queued or running state is not a provider receipt." We have not run that read-back on a public YouTube upload.
-
Do not read a private result as proof that the old rule still applies. Certain uploads might default to private from creator account settings, so check those settings before you draw a conclusion from one video.
-
The audit remains the route to extra quota. According to the entry, it no longer gates visibility. A
videos.insertcall "has a quota cost of 1 unit in the Video Uploads quota bucket", and the quota guide says: "If you would like to request additional quota beyond the default allocation, you must first complete an audit". Count your uploads against that bucket before you start an audit. -
Show the user the visibility before the upload goes. Section III.C.3 of the developer policies still says "users must have final control over the data that will be published to YouTube Applications." Under the old rule, an upload from an unverified API project created after 28 July 2020 ended in private until the project completed an audit. A missing field now defaults to public, although certain uploads might default to private, so a tool that skips this step can make public a video the user meant to keep private. If you buy an upload tool, ask which value it sends and whether it shows you that value first.
An official page still reads the old way
Videos locked as private - YouTube Help shows no date. When we read it on 6 November 2026, it had not caught up with the 2 November entry:
For videos that have been locked as private due to upload via an unverified API service, you will not be able to appeal. You'll need to re-upload the video via a verified API service or via the YouTube app/site. The unverified API service can also apply for an API audit.
The same page lists "Has been uploaded by an unverified third party API service" among content to avoid. We are not ruling on which page wins. No source we read says that videos already locked as private will change, so do not assume that they have.
We prepared for the old rule and have not tested the new one
Our domain was verified on 2 October 2026, our OAuth approval came on 10 October 2026, and we wrote an audit package. The audit is still open.
Our own docs stated the old rule until the week of 2 November. They said YouTube locks public and unlisted uploads as private for a project that has not completed an audit. We corrected them after the 2 November entry.
We built our YouTube upload for one MP4 up to 50 MiB, private by default in ShipContent, with no YouTube metrics.
We have not tested this yet. No public upload from our hosted app has been read back, so we make no claim about what a public upload from ShipContent does. We will update this post with the result.
Sources
- YouTube Data API: revision history, checked November 6, 2026
- YouTube Data API: videos.insert, checked November 6, 2026
- YouTube Data API: uploading a video, checked November 6, 2026
- YouTube Data API: quota and compliance audits, checked November 6, 2026
- YouTube API Services: developer policies, checked November 6, 2026
- YouTube Help: Videos locked as private, checked November 6, 2026
- ShipContent docs: channels overview, checked November 6, 2026