No: an unverified YouTube API project is not automatically restricted to private-only videos. That's what Google's detailed videos.insert reference says as of October 8, 2026. But asking for public visibility is not proof that strangers can watch, and neither amounts to passing every possible app review.
So why do searches still insist that all API uploads must be private? Because even the official documentation has two competing explanations. The fine print matters more than whichever snippet shouts loudest.
Why do two Google pages disagree?
Older guidance said projects created after July 28, 2020, needed an audit before uploads could be public. That wording spread through tutorials. The current upload method, however, explicitly says videos from unverified API projects aren't restricted to private viewing. The general video-resource page still carries an older-looking summary despite stating the newer behavior further down.
A YouTube API team reply described in the source account also said API uploads aren't made private automatically. Crucially, a support ticket being closed is not an audit approval or a quota increase. The help desk is not handing out graduation diplomas.
How do you check that your upload is actually public?
Public, unlisted and private are different settings. With videos.insert, set status.privacyStatus to public explicitly. Google says the unspecified default is usually public, but creator-account settings may make it private.
Upload one short video you own the rights to. Confirm the destination channel, music and image rights, and absence of anyone else's private information. Check the returned video ID and privacy status, then try the link in a signed-out browser. An API success response alone doesn't tell you what a stranger sees.
If the connection drops halfway through, search for the uploaded video before retrying. Ten copies of “upload test, please ignore” make an unexpectedly convincing spam exhibition.
Does the API let you publish 100 videos a day?
The current quota calculator assigns a standard bucket of 100 videos.insert calls per day, not 100 guaranteed successful public videos. Failed requests can consume quota, and a channel may have separate limits. OAuth permission to upload, app verification, video visibility and higher-quota audits are separate concerns.
Need more calls? Use the official quota and compliance process, not a collection of duplicate projects to dodge limits.
Bottom line: Don't let an outdated private-only rule block a legitimate test. But don't turn one successful upload into a claim that every review, rights check or limit has vanished.
