Meta App Review Screencast: How to Record It in 2026

If your app asks Facebook, Instagram or WhatsApp users for permissions such as pages_manage_posts, instagram_basic, instagram_content_publish or business_management, Meta will want to see your app use them before it grants access to anyone outside your team. You show that with screen recordings, uploaded inside the App Review submission.

Our overview of app review demo videos covers Meta in a few lines. This post goes further: what Meta's documentation says, what each common permission needs on screen, and the mistakes Meta lists as reasons for rejection.

Written by Bibin Mathew, who makes Nook. Requirements checked on October 28, 2026 against Meta's developer documentation, linked throughout.

#Short answer

• One recording per permission or feature. Meta's screen recordings guide says your submission "must include screen recordings that demonstrate how to use your app to test every permission and feature." A missing one means that permission is not approved.
• Start logged out. Capture "the entire login flow, from logged-out to logged-in," including the user granting the permission.
• Show the data in use. Show the user accessing data that needs the permission "and show what your app does with that data."
• English, or explain it. Set the UI to English if you can. If not, or if parts are not obvious, add captions and tool-tips.
• Assume no sound. Meta's tips say: "Omit audio; our reviewers will not listen to it." Put explanations on screen.
• Make sure reviewers can get in. If they cannot access your app or cannot find and use Facebook Login, the whole submission is rejected.

#Why Meta asks for recordings

When you build a Business, Consumer or Gaming app, Meta automatically gives it Standard Access to permissions and features. According to Meta's access levels page, "Permissions with Standard Access can only be requested from app users who have a role on the requesting app." That is enough for you and your teammates to build and test.

To request a permission from any user, you need Advanced Access. The same page says Advanced Access "must be approved on an individual permission and feature basis through the App Review process," and that "Business Verification is required to get Advanced Access."

The recordings are your evidence, permission by permission.

#What Meta's documentation actually says

Most of the rules come from two pages: the screen recordings guide and the submission guide.

#Every permission and feature needs its own recording

"Ensure that your screen recording shows your app using every permission and feature in your submission. If you omit one, it may not be clear to our reviewers how to test it, and your submission will be rejected." In the submission form, you upload a recording against each permission or feature.

Meta's WhatsApp App Review page is more direct: "Do not submit a video that includes multiple permissions supporting different use cases." Following that everywhere keeps each clip easy to review.

#Show the full login and the grant

"Our reviewers need to see how an app user logs into your app." Meta asks you to log out of any test accounts before recording and to capture everything from logged out to logged in. If you use Facebook Login for Business or Business Login for Instagram, show the user clicking that login button "and the app user granting your app the permission you are demonstrating." Then "Capture the complete authorization flow."

If people can also sign in without Meta's login, record that flow too.

#Show the data being used

"For each permission and feature in your submission, show an app user accessing data that requires the permission or feature and show what your app does with that data." Show the Pages list appear, the post get published, the message arrive.

#Recordings show how, the form explains why

Meta says recordings only need to show how to test each permission. They "do not need to explain why your app needs each of them," because the form asks for that separately. Each permission also gets its own written description, and Meta asks you to be specific and not copy and paste.

#Language, captions and unclear buttons

"If possible, please set the app UI language to English before recording." If your app is not available in English, or parts of it are not self-explanatory, Meta asks you to "Provide captions and tool-tips" and to "explain the meaning of any buttons or other UI elements that are not immediately obvious."

#Recording tips Meta lists as optional

The screen recordings guide calls these "optional tips":

• "Record in high-resolution, ideally 1080 or better." (The submission guide words this more firmly: "Make sure to record in high-resolution, 1080 or better.")
• "Decrease your monitor's resolution to a width of 1440 or less when you record."
• Use the mouse rather than the keyboard, with a bigger cursor.
• "Omit audio; our reviewers will not listen to it."
• "We recommend that you use annotations for all of the permissions and features that you are requesting."
• Zoom in on hard-to-see sections.
• "Record only what we need to see."

#Where Meta is vague

These pages state no length, file format or file size limit. Check what the upload field accepts when you reach it in the App Dashboard.

#Before you record: access, accounts and test users

The submission guide says: "Your app must be publicly available or you must provide instructions on how to access it." In the App Verification Details step, you describe how reviewers can reach and test your app.

On accounts, Meta says three things worth reading closely:

• "We will test your app using our own test accounts." Meta also says not to include your personal account's credentials.
• If users can sign up and log in without Facebook Login, "we recommend that you include credentials for one of these test users as well."
• Do not use a fake Facebook account. Meta's common mistakes page says that giving login details for a fake account leads to rejection of the whole submission.

For Advanced Access, there is also a prerequisite that has nothing to do with video. The submission guide says to "Make at least 1 successful API call using each permission for which you are requesting advanced access," within 30 days of submitting. The call can take up to 2 days to be logged, and until then the request button stays grayed out. You may also be prompted to complete business verification and to answer data handling questions.

#Per-permission recording plan

Meta's permissions reference gives screencast notes for many permissions. Here they are for the common ones, turned into a plan. Each dependency you request is also on your submission, so cover it too.

For business_management, the reference only asks for the login and grant. The last column follows Meta's general rule to show what your app does with the data. For pages_show_list and business_management, if you request them only as a dependency, Meta asks you to name the main permission in the written use case.

#How to record each clip

1. Start clean. A private window, logged out of Facebook and your app, notifications off.
2. Log in with Meta. From your app's login page, click the Facebook Login (or Business Login for Instagram) button.
3. Grant the permission. Pause on the consent step long enough to read it. Select the Page, Instagram account or business if asked.
4. Use the feature. Do the action that needs this permission, slowly.
5. Show the result where it lands. In your app, and on Facebook, Instagram or WhatsApp if the permission writes something there.
6. Label each step on screen. For example: "Granting pages_manage_posts," "Publishing the post," "Post now visible on the Page."

Record one clip at a time, so a mistake in clip four does not force you to redo clip one. Cut loading waits, never the login or the grant. Because reviewers watch without sound, captions do the work narration usually does. Short, literal sentences are easiest to read, and easier to get right if English is not your first language.

#Common rejection reasons

From Meta's common mistakes page and the guides above:

• The app is inaccessible. "If we can't access your app for any reason, your entire submission will be rejected."
• Facebook Login does not work or cannot be found. The whole submission is rejected.
• A fake account. Also rejects the whole submission.
• The app is still in development, or you request a permission you "might need later."
• A permission has no recording, or the recording does not show it being used. That item is not approved.
• A screenshot instead of a video, or a draft never submitted. Both from the WhatsApp page.

Forum posts and consultancies list other causes. Meta does not document them, so I left them out.

#Checklist

• My app is finished and reachable by reviewers, or I wrote clear access instructions.
• I only request permissions the current version uses, including the dependencies listed in the reference.
• Each permission I request for Advanced Access has at least one successful API call in the last 30 days.
• Business verification is done or under way.
• I have one recording per permission or feature, labelled with the permission name.
• Each recording starts logged out and shows the full login.
• Each recording shows the grant, then the data being used and where it ends up.
• The UI is in English, or captions and tool-tips explain it.
• The clip is 1080p or better and makes sense with the sound off.
• No personal account, real customer data, access tokens or secrets are visible.
• I am not using a fake Facebook account. If users can sign up without Facebook Login, I included test user credentials.
• Each permission has its own specific written description, not copied and pasted.
• I pressed Submit for Review and did not leave it in draft.

#Where Nook fits

Nook does not record your screen. You record each permission's flow yourself with QuickTime, OBS, Loom or anything else, then upload the file (MP4, MOV or WebM, up to 15 minutes; phone recordings work too).

Choose the Meta App Review purpose on the upload page, and Nook sets up the script to show each permission being used. It writes the explanation from what is on screen, adds captions, and zooms on clicks so the consent dialog and the result are easy to see. Since Meta's reviewers do not listen to audio, the captions are the part that matters most. You can pick captions only. Before you download, Nook checks the video is rendered, has no watermark, is 1080p, has captions on, and is understandable with the sound off. It also writes a step-by-step guide (PDF, Word or Markdown) you can reuse for the reviewer instructions and permission descriptions.

Your first video is free, up to 1 minute, with a watermark. That one is for trying it out, not for submitting. After that it is $9 per video, or Pro at $19/month for 10 videos, with lower prices in many countries. See Nook for Meta App Review screencasts.

#FAQ

#Do I need a separate screencast for each permission?

Meta asks for recordings that show how to test every permission and feature, and you upload one against each item. Its WhatsApp guidance says to use a separate video for each permission. One clip per permission is the safest way to meet both.

#Should I add voiceover to my Meta App Review video?

It will not help the reviewer. Meta's tips say, "Omit audio; our reviewers will not listen to it." Use captions and annotations instead, which Meta recommends for every permission you request.

#My app is not in English. Can I still submit?

Yes. Meta asks you to set the UI to English if possible. If it is not available in English, add captions and tool-tips that explain what is happening and what each unclear button does.

#Do I need to give Meta test credentials?

Meta says it tests with its own test accounts and tells you not to include your personal account's credentials. If users can create accounts and log in without Facebook Login, Meta recommends including credentials for one of those test users. Never supply a fake Facebook account.

#Do I need business verification?

For Advanced Access, yes. Meta's access levels page says Business Verification is required to get Advanced Access, and you may be prompted to complete it during submission.

#How long does Meta App Review take?

The submission guide says you "should receive a decision within a week." The WhatsApp page gives an average of about 24 hours for WhatsApp permissions. Neither is a guarantee.

#Can I reuse the same recording for dependent permissions?

Meta does not say this directly. Each permission you request needs a recording that shows it in use. If a permission like pages_show_list is only there as a dependency, show where the Page list appears in your app, and name the main permission in its written use case.

#Wrapping up

A Meta App Review screencast is a set of short, plain clips, one per permission, each starting logged out and ending with the data in use. Put explanations on screen and match each clip to Meta's note for that permission. For other platforms, see our app review demo video requirements. And if you already have the raw recordings, Nook can turn them into captioned, zoomed clips that pass its sound-off checks.