Google OAuth Verification Video: Requirements and Shot List (2026)

If your app asks Google users for sensitive or restricted scopes, such as Gmail, Drive or Calendar data, the OAuth review team has to verify it. Part of that review is a demo video. It is a short, plain recording, and small mistakes in it cost you another round of emails.

This guide covers what Google's documentation says the video must show, where to upload it, how long review takes and the issues Google lists as common, with a shot list and a checklist. For how Google's rules compare with Shopify, Meta, HubSpot and others, see our app review demo video requirements overview.

Written by Bibin Mathew, who makes Nook. Requirements checked October 28, 2026, against the Google pages linked in the sources section at the end. Google changes these pages without notice, so open them again before you submit.

#When Google asks for a demo video

Verification is tied to the scopes your app requests. Google's help center puts it simply: "If your app utilizes only non-sensitive scopes, it is not mandatory for your app to complete the app verification process." Apps that use only non-sensitive scopes but want their name and logo on the consent screen go through a lighter brand verification instead.

Once you request sensitive or restricted scopes, you need data access verification, and the demo video is part of it. Google's sensitive scope and restricted scope verification pages both ask you to "Prepare a video that fully demonstrates how a user initiates and grants access to the requested scopes."

Two things must be in place before you can request it:

• Published branding. Google says "you must have a published branding status before you can request verification for data access." Do brand verification first.
• The basics on your site. Your authorized domains verified in Google Search Console, a home page that is "publicly accessible, and not just accessible to your site's logged-in users," and a privacy policy "hosted within the same domain as your application's home page."

#When you do not need verification

Google lists exceptions where "you don't need to submit it for review": personal use (you or a few users you know personally), apps in development, testing or staging, service accounts that access only their own data, and internal apps used only within your Google Workspace or Cloud Identity organization. Read the exact wording before deciding you are exempt.

#What the video must show

Google describes the video on its verification pages and on the Demo Video page in the Google Cloud help center. Together, they ask for the following.

#1. The full grant flow, in English

"Show the OAuth grant process that users will experience, in English." Google adds that "This includes the consent flow and, if you use Google Sign-In, the sign-in flow." The help center page asks for "the end-to-end flow of your app including the OAuth grant process," and every point where your app integrates with the Google API you are requesting. If your app has more than one OAuth consent workflow, show each one.

In practice, start from a signed-out state, click whatever a real user clicks to connect Google, and do not cut until you are back in your app with access granted.

#2. The complete consent screen, with the exact scopes

The help center page asks for the complete OAuth consent screen, and says it must show the same scopes you requested in your verification submission. It also says to switch the screen's language to English using the language toggle in the bottom-left corner.

Request exactly the scopes you submitted, no more.

#3. The app name on the consent screen

"Show that the OAuth consent screen correctly displays the App Name." It should match the branding you submitted.

#4. Your OAuth client ID in the address bar

Google's verification pages say: "Show that the browser address bar of the OAuth consent screen correctly includes your app's OAuth client ID."

The consent screen URL contains a client_id= parameter, and the reviewer needs to read it. Many apps open the consent screen in a small popup where the address bar is cut off. Google does not say how to handle this. A practical approach is to widen the popup or open the flow in a full tab, click into the address bar so the full URL shows, and hold it for a few seconds. Check that the client ID belongs to the Cloud project you submitted.

#5. Each scope being used

"To show how the data will be used, demonstrate the functionality that's enabled by each sensitive scope that you request." The restricted scope page covers restricted scopes too, and the help center asks for your app's overall purpose as well.

After consent, walk through one feature per scope. If you request read access to Calendar, show your app displaying events. Name each scope as you go, out loud or in a caption.

#Narration

Google does not require a voiceover, but the help center says "Voice or text narration highlighting the points above can greatly help facilitate our review." A short line per step, such as "This feature uses the calendar.readonly scope," is enough.

#What Google does not specify

Google's pages do not set a length, resolution or file format, and say nothing about captions, music or cuts. Where Google is silent, aim for one continuous, readable recording that shows each required item and nothing extra.

#Where to upload it

The verification pages say: "Upload the video to YouTube Studio and set its Visibility as Unlisted." You then paste the link into the YouTube link field of the verification form.

Unlisted means anyone with the link can watch it, but it does not appear in search. A Private video cannot be opened by the reviewer. Test the link in a signed-out browser window.

If Google asks you to fix the video later, the help center page says to reply to the verification team's email with a link to the updated video on YouTube, Google Drive, or another accessible location. So the first submission goes in the form's YouTube field, and follow-ups go by email reply.

#How long review takes

Google gives rough timings, not guarantees:

• Brand verification: the automated check "usually completes in a few minutes." If it cannot reach a result, manual review "usually takes 2-3 business days."
• Sensitive scope verification: "typically takes 3-5 business days to complete."
• Restricted scope verification: "can potentially take several weeks to complete." Restricted scopes also need a security assessment by "an independent, third-party assessor that is approved by Google," based on the App Defense Alliance's CASA framework. Google says apps "must be reverified for compliance and complete a security assessment at least every 12 months."

These do not include the back-and-forth if the video is rejected, and Google does not say how long resubmissions take.

#Common rejection reasons

The help center lists four common issues with demo videos:

• Video link not accessible. The video is private, deleted, or behind a login. Use Unlisted and test the link signed out.
• Video shows a different app. The name, branding or flow in the video does not match the app you submitted. Record the submitted app, with the same name, branding and scopes.
• No consent workflow shown. The video starts after the user is already connected, or skips the consent screen. Show the full workflow and the full screen with every requested scope. Google adds that the consent configuration must also meet its branding guidelines.
• Insufficient functionality shown. The video shows the login but not what the app does with the data. Show the app's overall purpose and how it uses each scope.

The client ID in the address bar is not on that list, but the verification pages require it, so a cropped or unreadable address bar is worth checking for too.

#Preparing to record

• Record the submitted app. The app name, consent screen and client ID all have to match what you submitted.
• Use a test Google account with realistic but fake data. Anyone with the link can watch the video.
• Revoke earlier access. If the test account has already granted access, the consent screen may not appear in full. Remove your app from the account's third-party access first.
• Set the language to English. Both the consent screen toggle and your own app's interface, if it has a language setting.
• Clean the screen. Use a fresh browser profile, close unrelated tabs, and turn on do not disturb.
• List your scopes. Write them down with the feature that uses each one. That list is your recording order and your narration outline.

#Recording shot list

Record it as one continuous take if you can. Trim dead time like page loads, but do not cut between the consent screen and the return to your app.

#Turning the recording into a reviewable video

A raw recording often has no narration and long pauses. That is where Nook can help. Nook does not record your screen. You record the flow with any recorder, even a phone, then upload the file (MP4, MOV or WebM, up to 15 minutes). Nook writes narration from what is on screen and voices it with an AI voice, or keeps your own voice, or adds captions only. It adds captions, zooms on clicks, and writes a step-by-step guide you can export as PDF, Word or Markdown.

On the upload page there is a "Google OAuth verification" purpose. It keeps blur off so the consent screen, app name and client ID stay visible, and it runs checks before you submit: the video rendered, there is no watermark, it is 1080p, captions are on, and nothing on the consent screen is blurred. You then upload the finished video to YouTube as Unlisted yourself.

Your first Nook video is free, but it is limited to 1 minute and carries a watermark. Do not submit a watermarked video to Google. Make the real one as a paid video: $9 per video, or Pro at $19 a month for 10 videos, with lower prices in many countries.

#Checklist

Run through this before you paste the link into the form.

• Brand verification is published.
• Authorized domains are verified, the home page is public, and the privacy policy is on the same domain.
• The video shows the app I submitted, with the same name and branding.
• The recording starts signed out and shows the full grant flow, including Google Sign-In if the app uses it.
• The consent screen is set to English and fully visible, with the app name and every requested scope readable.
• The scopes on screen match my submission exactly.
• The address bar on the consent screen shows my OAuth client ID.
• Every sensitive and restricted scope is shown in use, with a visible result.
• Every consent workflow in the app is shown.
• Narration or captions say which scope each feature uses.
• Only a test Google account and fake data appear on screen.
• Nothing the reviewer needs is blurred, cropped or zoomed out of view.
• There is no watermark.
• The video is on YouTube as Unlisted, and the link plays signed out.

#FAQ

#Does every Google OAuth app need a demo video?

No. Google says apps that use only non-sensitive scopes do not have to complete app verification. The video is part of data access verification for sensitive and restricted scopes. Personal-use, development, internal and service-account-only apps are also exempt under Google's listed exceptions.

#Does the video have to be on YouTube?

For the first submission, yes: upload it to YouTube as Unlisted (not Private) and paste the link into the YouTube link field. For an updated video, the help center says you can reply to the verification team's email with a YouTube, Google Drive or other accessible link.

#How long should a Google OAuth verification video be?

Google does not specify a length. Make it long enough to show the full grant flow, the consent screen, the client ID and each scope in use, and cut dead time like page loads.

#Does the video need narration?

It is not required, but Google says narration "can greatly help facilitate our review."

#My app is not in English. What should I do?

Google asks for the grant process "in English." Switch your app to English for the recording if you can. English narration or captions help, though Google does not say whether they are enough on their own.

#How long does Google OAuth verification take?

Sensitive scopes "typically" take 3 to 5 business days. Restricted scopes "can potentially take several weeks," partly because of the security assessment. Rejections add time.

#Can I use a free Nook video for verification?

No. The free video is limited to 1 minute and has a watermark, so do not submit it. Use a paid video.

#Sources

All checked October 28, 2026:

• Google Cloud Help: Demo Video
• Google Cloud Help: OAuth App Verification Help Center
• Google Cloud Help: Submitting your app for verification
• Google for Developers: Sensitive scope verification
• Google for Developers: Restricted scope verification
• Google for Developers: Brand verification

#Wrapping up

The verification video is evidence, not marketing. Show the grant flow in English, the full consent screen with your app name and exact scopes, the client ID in the address bar, and each scope doing its job. If you already have the recording and want narration, captions and a written guide added without blur in the way, Nook for Google OAuth verification videos is built for that.