App Review Demo Video Requirements by Platform (2026)

If you build integrations or apps on top of someone else's platform, sooner or later a reviewer will ask you for a video. Sometimes it is a hard requirement and your submission will not move until you send one. Sometimes it is optional but strongly encouraged. And the rules for what goes in that video are different on every platform.

This guide collects the app review demo video requirements for the platforms small SaaS teams submit to most often: Shopify, Meta, Google OAuth verification, HubSpot, Google Play, Pinterest, LinkedIn, Zoom, Slack, Atlassian, Product Hunt and Apple. For each one you will find what is required, what to show, what length and hosting the platform asks for, and a link to the official page so you can confirm the details yourself.

All of the facts below were checked against the official pages on 2026-10-22. Platforms update these pages without much notice, so treat this as a map, not a contract, and re-read the source page before you hit submit.

#Why platforms ask for a demo video

A reviewer at Meta, Google or HubSpot is being asked to approve your app's access to their users' data. To do that responsibly they need to see three things:

1. What the app asks for. Which permissions, scopes or API access the app requests, and when.
2. Why it asks for it. The specific feature that uses each permission, so the reviewer can judge whether the access is justified.
3. What the user sees. The consent screens, disclosures and login flow, so the reviewer can confirm users are told what is happening.

Reviewers could, in theory, log in and click through every app themselves. In practice that is slow and error prone. Test accounts expire, third-party services need credentials, and some features only appear after setup steps that are hard to reproduce. A recording removes that guesswork. It shows the reviewer the exact path through your app, in order, with nothing skipped.

That is also why so many rejections come back with a note about the video. If a permission is requested but never shown in use, the reviewer has no evidence it is needed. If the login flow starts halfway through, they cannot see the consent screen. The video is your evidence, and the rules below describe what evidence each platform wants.

#Summary table: demo video requirements by platform

If you are working through several of these at once, our overview of app review videos groups the most common submission types in one place.

#Shopify App Store review

Status: required.

Shopify's app requirements checklist asks for "a complete screencast showing your app's setup process and functionality". This is the video the review team uses to understand your app before testing it.

Key points from the checklist:

• Language. "Make screencasts in English or with English subtitles."
• Expected outcomes. Show the expected outcome of each test case, so the reviewer knows what success looks like.
• Credentials. If your app connects to third-party services, provide valid test credentials for those integrations.
• Payments apps. Payments apps need screencasts for every browser they support.
• Length, format and hosting. The checklist does not specify these.

Do not confuse the review screencast with the listing promo video. The promo video on your App Store listing is a separate asset. It should run 2 to 3 minutes, be "promotional rather than instructional", and screencast footage should make up no more than 25% of it. The review screencast is the opposite: instructional, complete and plain.

For a deeper walkthrough, see our Shopify app review screencast guide and the Shopify app demo video page.

#Meta (Facebook and Instagram) App Review

Status: required.

Meta's screen recordings guide explains that every App Review submission must include screen recordings showing how to test each permission and feature you request. The main points:

• Every permission. Each requested permission and feature needs a recording that shows how to test it. If a permission has no recording, the submission can be rejected.
• Full login flow. Start from a logged-out state and show the whole login, through to logged in.
• Language. Set your app's interface to English if you can. If the interface is not in English, or is not self-explanatory, Meta suggests adding "captions and tool-tips" to explain what is happening.
• Quality. Among its optional best-practice tips, Meta says: "Record in high-resolution, ideally 1080 or better."
• Length and format. Not specified.

The practical lesson from Meta is to plan one clear segment per permission. If you request five permissions, a reviewer should be able to find five clear moments in your recordings where each one is used. Our Meta app review screencast page covers this in more detail.

#Google OAuth app verification

Status: required for apps requesting sensitive or restricted scopes.

Google's OAuth verification demo video help page is one of the most specific of any platform. The video must show:

• "The end-to-end flow of your app including the OAuth grant process."
• "The complete OAuth Consent Screen."
• The scopes on that screen. In Google's words, "The consent screen must also show the same exact scopes you are requesting."
• Your app's name and branding, matching what you submitted.
• Each consent workflow, if your app has more than one.
• The features that use each requested scope.

Google also asks you to set the language selector on the consent screen (bottom-left corner) to English before recording.

Narration is optional, but Google notes that "Voice or text narration highlighting the points above can greatly help facilitate our review."

Hosting: upload the video to YouTube, Google Drive, or another accessible location, and send the link by replying to the verification team's email. Length: not specified.

The most common mistake here is cropping or zooming past the consent screen. The reviewer needs to read the scope list on screen and compare it with what you requested. Leave the full screen visible for a few seconds. See Google OAuth verification video for a recording walkthrough.

#HubSpot App Marketplace certification

Status: required for certification.

HubSpot's app certification application page is direct: "The team will not review your app unless you submit a demo video that meets all requirements."

The requirements:

• "Be at least three minutes long."
• "Include audio (preferred) or text descriptions."
• Describe the app's purpose and its common use cases.
• Show how to install, configure and use the app, how it interacts with HubSpot, and how to disconnect and uninstall it, including what happens to data when you do.
• Submit it as a YouTube URL.

HubSpot also warns: "Promotional sales and marketing videos will be rejected."

The HubSpot listing itself has a demo video section, but the page does not make clear whether a video is required for a listing alone. Certification is where the requirement is explicit.

The three-minute minimum matters for planning. A tight two-minute walkthrough that would be ideal elsewhere will not meet HubSpot's bar. Make sure you actually cover disconnect and uninstall, since those steps are easy to forget. More on this at HubSpot app certification video.

#Google Play permission declarations

Status: required in some cases.

Google Play does not ask every app for a video. It asks when you declare certain sensitive permissions or features. Three common cases:

Background location. The background location declaration page asks for a video that shows the feature using location, the prominent in-app disclosure, and the runtime permission prompt, recorded on an Android device. Google says: "Aim for a video duration of 30 seconds or less." A YouTube link is preferred, and a Google Drive link to an MP4 is accepted.

Foreground service types. The foreground service declaration page says: "Include a link to a video demonstrating each foreground service feature."

AccessibilityService. The AccessibilityService policy page asks for a link to a short video showing the app being opened, the disclosure and consent flow, and the feature that uses the API.

Keep these videos short and focused on one feature each. They are not product tours.

#Pinterest API access upgrade

Status: required to move from Trial to Standard access.

Pinterest's access tiers page tells you to "Prepare a video recording of your app completing an action using the Pinterest API." The user authentication flow must be included. Length and hosting are not specified on that page.

#LinkedIn APIs

Status: required in some cases.

LinkedIn's API partner support guide lists a video in two situations:

• Advertising API, Standard tier: a video, shared as a Google Drive or SharePoint link, showing campaign creation, editing and optimization in your app.
• Community Management API, Standard tier: a screen recording of your app.

#Zoom App Marketplace

Status: test plan required; listing video optional.

Zoom's common rejection issues page says: "A test plan is required for each submission, including re-submissions." That test plan can be a written document or a demo video. Separately, you can add an optional video to your listing, up to 40 MB.

If you choose a video as your test plan, treat it like a review screencast: complete steps, test credentials, and clear outcomes. Remember that re-submissions need a test plan too.

#Slack Marketplace

Status: optional, strongly recommended.

Slack's Marketplace app guidelines say "We strongly recommend you consider adding a video". If you do, it should be 30 to 90 seconds, shared as a public YouTube link with captions turned on, filmed in a real Slack environment, and show your production app.

#Atlassian Marketplace

Status: optional.

Atlassian's Marketplace listing guide lets you add an optional YouTube video. Short videos of 30 seconds or less that show how the app is used are preferred.

#Product Hunt

Status: optional.

Product Hunt's launch preparation guide and posting help article treat a video as optional. "For videos, only YouTube links are supported." Use the full YouTube URL rather than a shortened link, and make sure the video is not private. Our Product Hunt demo video page has more on preparing one.

#Apple App Review

Status: no video requirement.

Apple does not ask for a review video. Instead, if your app needs a login, Apple asks for a demo account or a demo mode so the reviewer can use the app directly. App Previews on the App Store are optional marketing videos and are not part of review.

#Common rules across platforms

Every platform phrases things differently, but the same habits show up again and again. If you follow these, your video will be close to acceptable almost everywhere, and you will only need small adjustments per platform.

#Start from logged out

Meta asks for the full login flow from logged out to logged in. Google wants the end-to-end OAuth grant. Pinterest wants the authentication flow included. Begin every review video from a clean, signed-out state, ideally in a fresh browser profile or private window, so nothing is pre-filled and nothing is skipped.

#Use English, or caption it

Shopify asks for English or English subtitles. Meta asks you to set the UI to English if possible and add captions otherwise. Google asks you to switch the consent screen to English. Slack wants captions on. Even when the UI is already English, captions help a reviewer who is watching without sound.

#Show every permission and scope

If you ask for it, show it in use. Meta can reject a submission when a permission has no recording. Google wants the features behind each scope. HubSpot wants the full lifecycle including uninstall. A simple rule: make a list of every permission, scope and API product you request, and tick each one off as it appears on screen.

#Use test accounts, never real customer data

Record with test accounts, sandbox stores, demo workspaces and fake records. Shopify explicitly asks for valid test credentials for third-party integrations. Beyond what reviewers ask for, real customer names, emails and order data should never end up in a video you upload to YouTube or share by link.

#Keep the footage continuous

A reviewer is trying to confirm that one step leads to the next. Hard cuts that jump from a login page to a fully configured dashboard raise questions. Trim dead time, such as waiting for a page to load, but avoid edits that hide how you got from one state to another.

#Label what is happening

Meta suggests captions and tool-tips. Google says narration can help the review. HubSpot prefers audio. Short labels like "Requesting the calendar.readonly scope" or "Disconnecting the integration" save the reviewer from guessing.

#Keep it instructional

Shopify and HubSpot both separate review videos from promotional ones, and HubSpot will reject sales and marketing videos outright. Keep music, slogans and logo animations out of review recordings.

#A reusable recording plan and shot list

You can use one plan for most platforms and adjust the details. Here is the shot list we recommend, with notes on which platforms care most about each part.

#Before you record

• Write down every permission, scope and API product you request.
• Create clean test accounts on both your app and the host platform.
• Seed the test accounts with fake but realistic data.
• Set the app UI, browser and consent screens to English.
• Close unrelated tabs, notifications and chat apps.
• Set your screen to a resolution that records clearly. Meta suggests 1080 or better.
• Write a short script or outline. Our demo video script guide has templates.

#While you record

• Move the mouse slowly and pause on important screens.
• Hold on consent screens for a few seconds.
• Say or show which permission each feature relates to.
• If something fails, stop and re-record that part rather than editing around it.

#After you record

• Watch the whole video once as if you were the reviewer.
• Check every permission on your list appears.
• Check that nothing private is visible: real emails, phone numbers, card numbers, API keys or tokens.
• Export as MP4 and upload to the host the platform wants (YouTube, Google Drive or another link).
• Check the link works in a signed-out browser.

This is where a tool like Nook can save time. You upload a raw screen recording and Nook writes a clear English script from what you said or what is on screen, voices it with a natural AI voice, and adds English captions. It also flags and blurs emails, phone numbers, card numbers and API keys it finds. Always check the blurred result, because the reviewer still needs to read things like the app name and the scope list on a consent screen, and a blur in the wrong place could hide exactly what they are looking for.

#Narration vs captions

Platforms differ on how they want your video explained, and the safest choice is often to do both.

• HubSpot asks for audio (preferred) or text descriptions. If you only do one, do voiceover.
• Google says voice or text narration can greatly help the review. Either is fine.
• Meta suggests captions and tool-tips when the UI is not in English or not self-explanatory.
• Slack wants captions turned on.
• Shopify accepts English or English subtitles, which matters if you record in another language.

Some reviewers watch with the sound off, which makes captions valuable even when you have narration. Others follow along more easily with a voice explaining each step, which is why HubSpot prefers audio. A narrated video with burned-in or uploaded captions covers both.

If you are not comfortable recording your own voice, or English is not your first language, an AI voiceover over a clean script is a reasonable option. Nook produces both the voiced narration and English captions from the same script, so the two always match.

#How to keep videos current when platforms change

Review videos go stale in two ways: your app changes, or the platform's requirements change.

When your app changes. If you add a permission, rename a feature or redesign onboarding, the old video no longer matches what the reviewer will see. Re-record at least the affected segments. Zoom requires a test plan with every re-submission, and other platforms may ask again when you request new scopes.

When the platform changes. Consent screens get redesigned, marketplaces add requirements, and minimum lengths move. Keep a short note per platform with the date you last checked its official page and the link. Re-check before each submission.

A few habits make this easier:

• Keep your raw recordings, not just the final export, so you can re-edit without re-recording everything.
• Record in segments that match your shot list, so you can swap out one segment when one feature changes.
• Keep your script in a document next to the code it describes.
• Store a written step-by-step version of the flow. Many platforms ask for test instructions as well as video, and the two should match.

Nook outputs an MP4 download, a share link, and a written step-by-step guide built from the same recording. The written guide can double as test instructions for reviewers, which helps keep your video and your written steps in sync.

#A caution about changing requirements

Everything in this article was checked on the official pages on 2026-10-22. Platforms change these pages regularly and do not always announce it. Before you submit:

• Open the official page linked in that platform's section above.
• Compare its current requirements with your video.
• If the page and this article disagree, follow the page.

We have tried to describe only what the official pages say. Where a page does not specify length, format or hosting, we have said "not specified" rather than guessing. If a reviewer asks for something that is not on the page, follow the reviewer's instructions.

#Checklist

Use this before every submission.

• I have re-read the platform's official requirements page today.
• I know whether a video is required, optional or not used for this platform.
• The video starts from a logged-out state.
• The app UI, and any consent screen, is in English, or the video has English captions.
• Every permission, scope and API product I request is shown in use.
• The full consent screen is visible, including app name, branding and exact scopes (Google).
• Each test case shows its expected outcome (Shopify).
• Install, configure, use, disconnect and uninstall are all shown, including the effect on data (HubSpot).
• The video is at least three minutes long (HubSpot).
• Only test accounts and fake data appear on screen.
• No real emails, phone numbers, card numbers, API keys or tokens are visible.
• Any blurring does not hide the app name, scopes or other details the reviewer needs.
• Footage is continuous, with no edits that skip steps.
• Narration or captions explain what is happening.
• The video is instructional, not promotional.
• The video is uploaded to the host the platform asks for, and the link opens in a signed-out browser.
• Written test instructions match what the video shows.

#FAQ

#Do all app marketplaces require a demo video?

No. Shopify, Meta, Google OAuth verification (for sensitive or restricted scopes) and HubSpot certification require one. Google Play, Pinterest and LinkedIn require one in specific cases. Zoom requires a test plan, which can be a video. Slack, Atlassian and Product Hunt treat video as optional. Apple does not ask for a review video and uses demo accounts instead.

#How long should an app review demo video be?

It depends on the platform. HubSpot certification requires at least three minutes. Google Play suggests 30 seconds or less for background location videos. Slack recommends 30 to 90 seconds for listing videos, and Atlassian prefers 30 seconds or less. Shopify, Meta and Google OAuth do not specify a length, so make the video as long as it needs to be to show everything clearly.

#Where should I host my review video?

Follow the platform. HubSpot wants a YouTube URL. Google OAuth accepts YouTube, Google Drive or another accessible link sent by email reply. Google Play prefers YouTube for background location and accepts a Google Drive MP4 link. LinkedIn's Advertising API asks for Google Drive or SharePoint. Slack, Atlassian and Product Hunt use YouTube. Whatever you use, test the link in a signed-out browser.

#Can I use one video for every platform?

You can use one recording plan, but you will usually need a separate video per platform. Each one shows a different host platform, different permissions and different consent screens, and the length rules conflict. A three-minute HubSpot video is too long for a Google Play declaration, for example.

#Is a voiceover required?

Not usually. HubSpot prefers audio but accepts text descriptions. Google says narration helps. Meta suggests captions and tool-tips. Captions plus voiceover covers every platform listed here.

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

Switch the interface to English if you can, as Meta asks. Google asks you to set the consent screen language to English. If you cannot change the language, add English captions or subtitles, which Shopify and Meta both accept.

#What is the difference between a review screencast and a listing video?

A review screencast is for the reviewer. It is instructional and complete. A listing video is for potential customers. Shopify's listing promo video, for example, should be "promotional rather than instructional", while HubSpot rejects promotional videos for certification. Keep the two separate.

#Can I use Nook for a HubSpot certification video?

Yes, with a paid video. Nook's first video is free but limited to 1 minute and includes a watermark, so it will not meet HubSpot's three-minute minimum. Paid videos can run up to 15 minutes and cost $9 each (see pricing). Nook does not upload to YouTube for you: you download the MP4 and upload it to YouTube yourself, since HubSpot asks for a YouTube URL.

#Does using an AI voice or AI captions affect approval?

None of the official pages listed here say anything about AI voices or AI captions. What reviewers look for is whether the video shows the required flows clearly. No platform endorses or specifically accepts any particular video tool, so judge the result against the platform's requirements.

#Wrapping up

Review videos are not hard to make once you know what each reviewer is looking for. Start logged out, show every permission in use, keep the consent screens readable, use test data, and explain each step in English. Then check the official page one more time before you submit.

If you want help turning a raw screen recording into a narrated, captioned review video with sensitive details blurred and a matching written guide, take a look at Nook for app review videos. Your first video is free, and you can start here.