App Rejected Over Screenshots? Fixing Apple Guideline 2.3.3 Fast

A phone card in a soft warning halo turning into a clean approved card in indigo light

Your app got rejected and the review notes cite Guideline 2.3.3. The good news: this is one of the fastest App Store rejections to fix, because it is about your screenshots, not your binary. Here is what 2.3.3 actually demands, why listings trip it, and how to resubmit within the hour.

What Guideline 2.3.3 actually says

Apple requires screenshots to show the app in use. The reviewer wants to see your actual interface doing its actual job, not a poster about it. Metadata-only rejections like this one are handled in App Store Connect: you fix the images, resubmit, and no new build is needed.

The usual triggers

Most 2.3.3 rejections come down to one of these:

  1. Splash screens or login walls as screenshots. A logo on a gradient tells the reviewer nothing about the app. Same for a login form as your first frame.
  2. Pure marketing images. Slides that are only text and lifestyle photography, with no visible app UI anywhere.
  3. The wrong device's UI. iPad slots showing a stretched iPhone capture, or screenshots with another platform's status bar.
  4. Content that is not yours or not in the app. Borrowed imagery, features that do not exist yet, store badges inside the screenshot.

How to fix it fast

Replace the offending images with slides where your real UI is clearly the subject. Styled screenshots are completely fine, Apple explicitly tolerates marketing framing (captions, backgrounds, device frames), as long as genuine app content is visible and current-generation. In LookFrame the real capture always stays the visual core of the slide, with the caption and background around it, which is exactly the composition 2.3.3 wants. Check your set against the required dimensions while you are at it (App Store screenshot sizes): resolution mismatches often ride along with 2.3.3 notes.

Then resubmit from App Store Connect. Metadata reviews usually come back fast, often within a day.

Staying safe permanently

Adopt one rule: every screenshot contains a recognizable, truthful piece of your interface. You can lead with your strongest benefit as a caption (write captions that sell and index), keep beautiful backgrounds, use device frames. Just never ship a frame where a reviewer could ask "but where is the app?".

The short version

2.3.3 means "show the product". Kill the splash screen slide, make your real UI visible in every frame, resubmit the metadata, and you are typically back in review the same day.

Frequently asked questions

Do I need to submit a new build to fix a 2.3.3 rejection?

No. Guideline 2.3.3 is a metadata rejection: you replace the screenshots in App Store Connect and resubmit. Metadata-only reviews typically come back much faster than binary reviews, often within a day.

Are styled screenshots and device frames allowed?

Yes. Captions, backgrounds and device frames are standard practice and fine with Apple, as long as your genuine, current app interface is clearly visible in the frame. What triggers 2.3.3 is screenshots that show no real app UI at all.

What are the most common 2.3.3 triggers?

Splash screens or login walls as screenshots, marketing-only slides with no interface, iPad slots filled with stretched iPhone captures, and imagery showing features that do not exist in the shipped app.

Related guides

A phone screenshot being composed on a bright canvas with indigo caption blocks floating above How to Make App Store Screenshots (Free, No Designer Needed) July 9, 2026 · 2 min read Two phone cards on twin pedestals with a beam of light tilting toward the winning one A/B Testing Screenshots: Apple PPO vs Google Play Experiments July 5, 2026 · 2 min read Three phone silhouettes of increasing size with soft indigo measurement guides on a light background App Store Screenshot Sizes in 2026: Every Dimension That Matters July 5, 2026 · 2 min read