App Review Screenshot Guidelines: Apple's Rules Summarized

Why does Apple care about screenshots specifically?

The App Store is curated. Apple's position, restated in the introduction to the App Review Guidelines, is that a high-quality store benefits both users and developers. Screenshots are the user's first impression; misleading screenshots erode trust in the store as a whole. That is why screenshot enforcement is among the strictest parts of App Review and why fixing issues fast matters more than arguing.

What does “accurate representation” mean (2.3.3)?

Guideline 2.3.3 requires that screenshots show the app actually running. The grey area is what counts as “running”. Apple is strict about:

• Concept art for features that do not ship in the binary you submitted
• Pre-rendered marketing illustrations that show the app inside a hypothetical scenario
• Competitor screenshots dressed up as your own

Apple is more permissive about:

• Device mockups — your real app screen composited inside an iPhone frame is fine
• Captions and headlines — text overlays explaining what the screen does
• Backgrounds — gradient or photographic backgrounds behind the device frame
• Generated sample data that plausibly represents what a real user would see

Why is placeholder content a problem?

Lorem ipsum, “User Name”, and obvious test accounts (e.g. “test@test.com”) signal an unfinished product. App Review treats these as representative of the app being unfinished — a fast path to rejection. Populate every field with plausible data: real-looking names, realistic transaction amounts, current dates. Generated data is fine; obvious placeholder data is not.

What about wrong device sizes (2.3.10)?

Guideline 2.3.10 covers metadata accuracy. Submitting a 6.1-inch screenshot in the 6.7-inch slot — even if upscaled — is rejected because the resulting image does not represent the app at the larger device's actual aspect ratio. Use the device-specific renders we list in the App Store screenshot sizes guide, and let the Screenshots.live API generate each device natively rather than scaling.

Can you mention Android in iOS screenshots?

No. Guideline 2.3.10 prohibits references to other mobile platforms inside iOS metadata, including screenshots. Common offenders:

• “Now on Android” banners
• Google Play download badges
• Screenshots that show your app inside an Android device frame (Pixel, Galaxy) instead of an iPhone frame

The fix is per-platform variants: same template, different device frame configuration. Render the iOS variant with iPhone frames, the Android variant with Pixel frames, and upload to the appropriate store. See the multi-platform support feature for the configuration.

What about marketing claims (2.3.7)?

Apple has rejected listings for unverified superlatives: “#1 productivity app”, “Best note-taker on iOS”, “Used by 10M+ teams”. The fix is either:

• Cite a source in the screenshot or caption (“Top 10 in Productivity, App Store, US, March 2026”)
• Be specific instead of superlative (“Trusted by 8,432 teams” if that number is accurate)
• Remove the claim entirely and lean on the product itself

How do age ratings interact with screenshots?

The age rating you select in App Store Connect applies to every asset on the listing — including screenshots. A 4+ app that shows alcohol, tobacco, intense violence, or suggestive content in screenshots gets bumped to a higher rating, or rejected if the rating cannot accommodate the content. Match content to rating from the start: if your screenshot needs a wine-list UI, the app's rating must already accommodate alcohol references.

Which device frames are allowed?

Apple permits showing your app inside an Apple device frame for the device class you are listing (iPhone, iPad, Apple Watch, Apple TV). Do not:

• Modify the device frame visually (custom colors, logos)
• Mix Android frames into iOS listings
• Use generic “phone-shape” frames not blessed by Apple

Use Apple's official device frame assets (Sketch / Figma libraries) when designing your template.

What about third-party logos and copyrighted content?

Guideline 5.2 covers intellectual property. The most common screenshot offender is a fake push notification from a brand the app is not licensed to use: “Slack: New message from Eve” in a screenshot of a non-Slack app, for example. Use generic mock notifications, anonymized brand-like UI (no real logos), or licensed content with provable rights.

How does pricing accuracy apply (3.1.1)?

If a screenshot says “Free forever” but your app uses a $4.99/month subscription, expect rejection. Pricing claims in screenshots must reflect the actual IAP / subscription you ship. The same applies to “No ads” claims, “One-time purchase” claims, and “Free trial” durations — every one must match what the user encounters in the app.

What about locale-level mismatches?

A US dollar price tag in your German listing reads as careless to App Review and to users. Same for date formats (MM/DD/YYYY in a German listing), social references (“Trending on Twitter” in a Mainland China listing where Twitter is blocked), and holidays (Thanksgiving callouts in non-US listings). The localization guide covers per-locale overrides for exactly these cases.

What do you do when you are rejected?

Most screenshot rejections are easy to fix: change the offending element in your template, re-render via API, re-upload, resubmit. The full cycle is usually under an hour. Two pieces of advice:

• Read the exact guideline Apple cites in Resolution Center. The fix is almost always narrower than you think — sometimes a single element on a single screenshot.
• Resubmit before appealing. Appeals through Resolution Center take days; resubmissions after a fix are usually processed within hours. Appeals make sense when you genuinely believe the review was wrong — not when the fix is obvious.

How do Google Play's rules differ?

Google Play's Store Listing and Promotional Content Policy covers similar ground but is generally more permissive on marketing language and stricter on misleading functionality. The basics — accurate representation, no fake notifications, age-rating consistency — apply on both platforms. The technical specs differ; see our Google Play screenshot requirements guide for those.

The bottom line

The fastest way to stay out of App Review's screenshot rejection bucket is to start from a template that already follows the rules — accurate device frames, no cross-platform references, plausible sample data, no unsubstantiated claims. Generate variants from that template, and the rejection rate drops to near zero.