App Store screenshot rejections and how to avoid them
Screenshot rejection is the most common reason a first App Store submission stalls. The reviewer accepts the binary but bounces the metadata, and you start the clock over on appeals. The good news: the rule set is small and stable. Most rejections cite the same handful of guidelines. Here's that list, in rough order of how often each one trips.
1. Status bar inconsistencies
Apple wants screenshots to look like real device states. A faked status bar that doesn't match — wrong time, mismatched battery icons across panels, signal bars on a Wi-Fi-only iPad — gets flagged. Use the conventional 9:41 time across all panels (the standard marketing convention), keep battery at 100% or hide the indicator entirely, and match cellular vs Wi-Fi consistently.
Cited under Guideline 2.3.10 (accurate metadata) or 4.3 (spam).
2. Screenshots that don't show the actual app
This is the most consistent rejection reason for "designed" carousels: panels that show a marketing image rather than the app itself. A panel of pure brand graphic, a panel showing people using a phone, or a panel that's all caption with no app content all violate the rule that screenshots must show app functionality.
The fix: every panel must contain a recognizable app UI element. You can wrap it in a device frame, add a caption, change the background — but the app UI has to be present and identifiable.
Cited under Guideline 2.3.3 (screenshots show app functionality).
3. Promotional or pricing claims in the screenshot
Screenshots can't contain pricing, "limited offer", "$5 off", "Free for a week", or any claim that would change with App Store metadata. Apple wants the screenshot to remain valid across price changes, sales, and regions.
"Award-winning" works if you can substantiate it. "Best app of the year" is fine if Apple themselves gave you the award; otherwise it's a marketing claim that needs proof, and reviewers sometimes flag it.
Cited under Guideline 2.3.10 or 3.1.4.
4. Third-party trademarks or logos
Showing the Spotify logo in your screenshot because your app integrates with Spotify is risky. Same for Apple's own product logos (don't show the Apple logo, don't show iCloud iconography unless you're using Apple's official integration). User-uploaded content that contains trademarks is also a risk.
The safe path: stylized placeholder content in screenshot mockups. If you must show a brand integration, use the brand's official marketing assets exactly as their guidelines allow.
Cited under Guideline 5.2 (intellectual property).
5. Device frames that misrepresent platform
iPhone screenshots in an Android frame, or vice versa, get rejected. Mixed device classes in one carousel (an iPhone 6.9" frame alongside a 4-inch SE in the same panel set) get questioned.
Each screenshot upload class needs its own appropriate device. Apple's own guidelines say "screenshots should reflect the platform the user is shopping on". Use iPhone-class devices for iPhone screenshot uploads, iPad for iPad uploads.
Cited under Guideline 2.3.10.
6. Content that's adult, scary, or violent without the right age rating
Apple's content reviewers see the screenshots before the app. If a screenshot suggests adult content, violence, or scary themes that exceed your app's declared age rating, the submission gets bounced for an age-rating mismatch even if the rest of the metadata is fine.
The fix is either tone down the screenshot or update the age rating. Updating the rating has knock-on effects on which storefronts your app can ship in, so most apps tone the screenshot.
Cited under Guideline 1.1 (objectionable content).
7. Wrong upload class dimensions
Apple now requires only 6.9" iPhone (1320 × 2868) and 13" iPad (2064 × 2752) for new submissions. Smaller classes are accepted but optional. Trying to upload a 6.5" screenshot at 1242×2688 to the 6.9" class will fail validation at upload time, not at review time.
This isn't strictly a "rejection" since App Store Connect catches it during upload, but it accounts for a meaningful share of the "my screenshots aren't going through" support tickets. See the 2026 size reference for the full table.
8. Inconsistent screenshots across locales
If your en-US screenshots show one app state and your fr-FR screenshots show a different app state, reviewers sometimes flag this as confusing metadata. The expectation is that screenshots across locales should be the same scenes with translated captions, not different scenes.
Translation alone is fine. Wholesale redesign per locale should be intentional and consistent within each locale (i.e., if you redesign for Japan, redesign all the Japan panels; don't mix).
What to do this week
- Audit every panel for status-bar consistency. Same time, same battery, same cellular state.
- Make sure every panel shows actual app UI. No pure-marketing panels.
- Strip any pricing, promotional, or sale language.
- Verify no third-party trademarks beyond your own.
- Confirm device frame matches platform per upload class.
- Cross-check against your declared age rating.
If a rejection lands anyway, the appeal process is usually fast — write a clear explanation citing the specific guideline you believe applies, and Apple's review team responds within a few days.