Meta App Review
How to Record a Meta App Review Screencast Reviewers Can Actually Follow
The screencast is the strongest evidence in an App Review submission. This is the structure, tooling, and editing approach I use for every permission request.
Treat the App Review screencast as a test case
A reviewer watches the video to answer one question per permission: is this permission used for the feature described, and only for that? I plan every screencast like an end-to-end test. Each permission gets its own scenario with a clear start, an action, and a visible result.
When a screencast is unclear, the usual result is the “unable to verify use case” rejection. Most of those rejections are preventable with a better recording, not a better product.
Prepare the environment before recording
- Prepare a clean test user and a test Page, Instagram professional account, or WhatsApp number with realistic sample data.
- Log out of everything so the login and permission dialog can be shown from the beginning.
- Close unrelated tabs, notifications, bookmarks bars, and anything showing personal information.
- Set the app and browser language to English, or plan to add English captions.
- Use the same app build and environment the reviewer will access with the test credentials.
- Write a short script listing each permission and the screen where it is used.
A screencast structure reviewers can follow
- Intro card: the app name and the list of permissions demonstrated.
- Login flow: the user signs in and connects their Meta account, with the permission dialog visible.
- Asset selection: the user picks the Page, Instagram account, or WhatsApp number to connect.
- One chapter per permission, with an on-screen label naming the permission.
- For each chapter, the action in the app and the effect on Meta's side.
- Closing: where users disconnect the account or request data deletion.
I keep the chapter order identical to the order of permissions in the submission. Reviewers often watch with the submission open next to the video.
Show both sides of every API call
A feature that only shows your own UI is weak evidence. The reviewer needs to see data moving between your app and Meta. If the app reads comments, show the comment on Instagram first and then in your app. If the app sends a Messenger reply, show it being sent from your inbox and then arriving in Messenger. A split screen or a quick switch between windows works well.
Captions and editing rules
Editing is allowed, but it must not hide anything important. I cut waiting time and loading screens, never the moment where data moves between the app and Meta. Captions are short and factual, such as “Reply sent from our inbox using pages_messaging”. I keep a readable resolution, avoid zooming so far that the reviewer loses context, and use a mouse highlight so clicks are easy to follow.
Audio narration is optional. If you add it, keep it in English and make sure the captions say the same thing, because some reviewers watch without sound.
Screencast mistakes that cause Meta App Review rejections
- One long, unlabeled video where the reviewer has to guess which part relates to which permission.
- Demonstrating a permission in Graph API Explorer instead of the real product.
- Skipping the login flow because the user was already connected.
- Showing a different app version than the one the reviewer can access.
- Showing a permission in use without showing why the user needs it.
- Using placeholder data that makes the feature look unfinished.
Tools and settings I use for recording
Any screen recorder that produces a clear MP4 works. I record the browser window rather than the full desktop, at a resolution where text is readable without zooming, and I enable a click highlight so reviewers can follow interactions. For mobile apps, I use the device's built-in screen recording or a simulator, and I keep the device in portrait mode unless the app requires landscape.
I record each chapter separately and join them in a simple editor. That makes it easy to re-record one permission without redoing the whole video when something changes. Captions are added as large, high-contrast text in a consistent position, usually the top of the frame, so they never cover the part of the UI being demonstrated.
Before uploading, I watch the final video once at normal speed without sound, with the submission text open next to it. If I cannot match every permission to a timestamp, I fix the video. I also keep the source recordings, because a future resubmission often needs only one chapter replaced.
Special cases: messaging and Human Agent
Messaging permissions need extra care because reviewers check the policy rules, not only the feature. For the Human Agent feature, the video must show a real person replying from an agent interface. I explain the details in Human Agent permission: why Meta rejects it. For AI replies, show where automation stops and how users reach a human, as described in building a compliant AI reply agent.
Frequently asked questions
How long should a Meta App Review screencast be?
Long enough to show every permission clearly. For a few permissions, three to six minutes is typical. Clarity matters more than length.
Can I upload a separate video for each permission?
Yes. Separate videos work well when the features are unrelated. Just make sure each one still shows how the user connected their account.
Do I need narration?
No. Clear on-screen captions are enough and often easier for reviewers. If you narrate, keep captions in sync.
What if my app's UI is not in English?
Switch the UI to English for the recording if possible. Otherwise, add English captions explaining each step and button.