App Store · Guideline 2.3.3

Guideline 2.3.3 Accurate Metadata: screenshots

Accurate Metadata: screenshots don’t show the app in use

Guideline 2.3.3 — Accurate Metadata: screenshots don’t show the app in use. Your screenshots are mostly marketing art, a splash or login screen, or the wrong device — a stretched iPhone screenshot in the iPad slot is the classic.

Updated

What this rejection means

Your screenshots are mostly marketing art, a splash or login screen, or the wrong device — a stretched iPhone screenshot in the iPad slot is the classic.

Why reviewers send it

Screenshots are a promise about what people will get. Apple rejects sets that are mostly marketing art, splash or login screens, or captures from the wrong device — a stretched iPhone image in the iPad slot is the most common one.

The message App Review sends

Guideline 2.3.3 - Performance - Accurate Metadata

We noticed that your screenshots do not sufficiently reflect your app in use. Specifically, your 13-inch iPad screenshots show an iPhone image that has been modified or stretched.

The exact wording changes from one review to the next; the guideline number is what to look for.

How to fix it

  1. Use screenshots of the app’s real screens in use. Captions and frames are fine, but the app has to be what people see.
  2. Use iPad screenshots taken on an iPad (13″ size), or stop offering the app on iPad.
  3. Skip the login and splash screens; show the main features.
  4. Replace them in App Store Connect and resubmit. A metadata-only fix keeps the same build.

The screenshot size checker tells you which App Store slot each screenshot fits and exports the missing sizes.

What to reply in App Store Connect

Replace the [brackets] with what you actually changed:

Guideline 2.3.3 — We replaced the screenshots with captures of the app in use on [iPhone 6.9″ / iPad 13″], showing [screens].

Got a different message?

Paste the whole rejection into the rejection explainer. It recognises this one and 26 others, in your browser — nothing is uploaded.

Other App Store rejections

Fixed it? Send the build back to App Review

CapWrapp builds the fixed commit on GitHub’s Mac machines, uploads it to TestFlight, and sends the build you pick to App Review from one page — no Xcode.

  • Free to start
  • No credit card
  • Sign in with Google or GitHub