App Store 2.3.3 rejection: App screenshots

By The Draftbit team · Updated
Sources checked

This guide is for iPhone and iPad submissions whose store screenshots don't show the app in use.

You’ve uploaded polished artwork, but Apple wants to see the app. Guideline 2.3.3 says screenshots should demonstrate actual use, rather than consisting only of a title image, login page, or splash screen.

Choose screens that explain the product

Walk through the main task with a test account and capture useful states: browsing real example content, completing an action, or seeing its result. We’d show the experience a person is downloading the app for, especially if sign-in is only the first step.

Text and image overlays can help explain an interaction. Keep the app itself accurate and visible. Check each required device set and localization for obsolete screens.

Replace and verify the assets

Capture the current build with fictional account data. Replace image-only or sign-in-only sets with screenshots showing the actual experience, and check that any paid features are identified as required by 2.3.2.

Preview the uploaded images in App Store Connect at readable sizes. Tell Apple which screenshot sets changed. If a depicted feature needs a particular account state, include the steps to reach it in your review notes.

Messages this guide can help with

App Store 2.3.3 rejection; app store 2.3.3 denial; Guideline 2.3.3; App screenshots

Official sources

We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.

Your next stepSubmit your iPhone or iPad app for review