Guideline 2.3.3 rejection: Screenshots that do not show the app in use
What it means, why it happens, and how developers get through it.
Subject line you may see: Guideline 2.3.3 - Performance - Accurate Metadata
What Apple's guideline says
Screenshots should show the app in use, and not merely the title art, login page, or splash screen.
From App Review Guidelines, 2.3.3, as revised October 16, 2026. Apple's help: 2.3.3 Show your app in use with screenshots.
Common causes
- Screenshots that are mostly title art or marketing slides
- Only the login page or splash screen
- Overlays that cover the app interface
- Screenshots from an older version that no longer match the current interface
- Device frames with no app interface behind them
How to fix it
- For each device type, make more than half of the screenshots show the app in use (Apple's example: two of three, three of four)
- Show the main features, from the current version
- Keep overlays and marketing text from hiding the app
- Remove screenshots that show only a login page or splash screen
- Reply saying which screenshots you replaced, per device
What to put in your reply
A sample reply note. Replace the brackets with your facts and remove anything that does not apply.
Hello, Thank you for the review. Regarding Guideline 2.3.3, we replaced the screenshots for [devices]. Now [3 of 4] screenshots for each device show the app in use: [feature 1], [feature 2], [feature 3]. Thank you.
Real cases: others who got 2.3.3
No public cases logged yet.
Questions developers ask about 2.3.3
What does a Guideline 2.3.3 rejection mean?
Most of your screenshots show marketing art, a login page, or a splash screen instead of the app in use. Apple approves only when more than half of the screenshots for each device show the app in use.
Why do apps get rejected under Guideline 2.3.3?
Common causes, based on Apple's guideline text: screenshots that are mostly title art or marketing slides; only the login page or splash screen; overlays that cover the app interface; screenshots from an older version that no longer match the current interface; device frames with no app interface behind them.
How do I fix a Guideline 2.3.3 rejection?
1. For each device type, make more than half of the screenshots show the app in use (Apple's example: two of three, three of four). 2. Show the main features, from the current version. 3. Keep overlays and marketing text from hiding the app. 4. Remove screenshots that show only a login page or splash screen. 5. Reply saying which screenshots you replaced, per device.
Do I need a new build for Guideline 2.3.3?
Fix the listing, then reply. Metadata issues can often be fixed on the product page without a new build. Change the fields, then reply listing exactly what changed. This is how the guideline is usually resolved, not a prediction for your app.
How should I reply to App Review about Guideline 2.3.3?
Reply in App Store Connect. Thank the reviewer and name Guideline 2.3.3, say exactly what changed and in which version and build, give a numbered path the reviewer can follow, and attach proof such as screenshots or a screen recording.
How many of my screenshots must show the app in use?
More than half for each device type, per Apple's 2.3.3 help article. With three screenshots, two must show the app in use; with four, three must.
Stuck on 2.3.3?
Do it yourself, faster
App Store Rejection Rescue Kit: the full decoder, 12 reply templates, Notes for Review templates, and a 60-point preflight checklist.
Get the kit, $12Have it written for you
Send your rejection, get a reply drafted for your exact case. Kit buyers get $10 off.
AI-assisted, built on Apple's App Review Guidelines. Not a guarantee of approval. If we do not deliver within 24 hours, you get a full refund.
Reply service, $29Related rejections
See also: 2.3.14 creative assets · 2.3.10 other platforms
Source: Apple's App Review Guidelines, section 2.3.3, as revised October 16, 2026. Last checked . Always read the current official text. How we write these guides.