Beautiful screenshots are worthless if they get rejected. Understanding app store screenshot requirements — the sizes, formats, content rules, and submission process — is what ensures your carefully designed creatives actually reach users. This guide covers everything you need to submit screenshots successfully in 2026 and avoid the rejections that delay releases.
For the exact sizes, see our guide to App Store screenshot dimensions; for the design craft, designing App Store screenshots.
The two kinds of requirements
App Store screenshot requirements fall into two categories, and passing review means satisfying both. The first is technical: your images must match the required resolutions for each device class, be in the correct format, and be uploaded to the right slots. The second is content-based: your screenshots must accurately represent your app and follow Apple's content guidelines, without misleading mockups, placeholder text, or prohibited content. Teams often focus only on the technical side and get surprised by a content rejection, so understanding both is essential for smooth screenshots for app store submission.
Technical requirements
On the technical side, Apple expects exact apple app store screenshot sizes per device class. You provide screenshots for the required iPhone sizes, and for iPad if your app supports it. The app store connect screenshot size for each slot is specified precisely, and images that do not match are rejected. You can provide up to ten screenshots per device size, though as covered elsewhere, the first few carry most of the conversion weight. The safest way to meet these requirements is to design from current templates and confirm the specification in App Store Connect before uploading, since exact resolutions evolve as new devices launch.
Content requirements
The content rules matter just as much and catch many teams off guard. Apple requires that screenshots accurately represent the actual app — you cannot show features that do not exist or use misleading mockups that imply a different experience. Screenshots should not contain placeholder or lorem-ipsum text, offensive content, or references to other platforms. They must not imply endorsements you do not have. Beyond avoiding rejection, these rules protect your own interests: screenshots that over-promise attract users who install, discover the app is not what they expected, and churn — dragging down the retention signal that now heavily influences ranking. Honest app store screenshot guidelines compliance and good business are aligned here.
How to submit in App Store Connect
The submission process itself is straightforward once your images are ready. In App Store Connect, open your app and the specific version you are editing. Navigate to the section for app previews and screenshots, where you will find slots for each required device size. Upload your images in the correct resolution to each slot, arranging them in your intended order — remember that order is a conversion decision, not an afterthought. Save your changes, and the screenshots become part of the version you submit for review. If you are updating screenshots on an already-live app, some changes can be made without a full app update, while others are tied to a new version, so plan accordingly.
A submission checklist
A short pre-submission checklist prevents most problems:
| Check | Why it matters |
|---|---|
| Correct resolution per device size | Wrong sizes are rejected outright |
| Accurate representation of the app | Misleading content is rejected and hurts retention |
| No placeholder or prohibited content | Common, avoidable rejection cause |
| Uploaded to the right device slots | Misplaced images cause errors |
| Intended order preserved | Order drives conversion |
| Full resolution, no blur | Low quality looks unprofessional |
Running through this list before you submit turns review from a gamble into a formality.
A worked example
A team preparing a major update redesigns its screenshots and, having been burned before, follows a disciplined submission process. They design from current templates so every image matches the required resolution. They review each frame against Apple's content rules, confirming nothing implies a feature the app lacks and no placeholder text slipped through. They upload to the correct device slots in App Store Connect, preserving their tested order with the strongest frame first. They double-check resolution and clarity, then submit. The review passes without issue on the first attempt, avoiding the delay a rejection would have caused right before their launch. The lesson is that a little upfront rigor around app store screenshot requirements is far cheaper than a rejected submission at the worst possible moment.
Common submission mistakes
The frequent causes of rejection and delay are wrong dimensions, misleading or inaccurate content, placeholder text left in by accident, low-resolution or blurry images, and uploading to the wrong device slots. Each is entirely avoidable with a template-based workflow and a pre-submission review, and avoiding them keeps your releases on schedule.
Updating screenshots on a live app
Requirements are not only a launch concern; you will update screenshots throughout your app's life, and knowing how that works avoids surprises. On the App Store, some screenshot changes can be published as part of a new app version, tied to the release that goes through review, while metadata-only updates in certain cases can be made without shipping new binary. This matters for planning, because if you want to refresh your creatives to test a new message or reflect a new feature, you need to know whether that change rides along with your next version or can go live independently. It also matters for freshness: because updating creatives contributes to the metadata-freshness signal that supports ranking, a regular cadence of screenshot refreshes is worth building into your release rhythm rather than treating screenshots as a set-once asset. The key is to plan updates deliberately — align major creative refreshes with meaningful releases, keep your templates and dimensions current so re-exports are painless, and review each updated set against the same requirements checklist you used at launch. Handled this way, ongoing screenshot updates become a routine part of optimization rather than a periodic scramble, and they keep your listing both compliant and continually improving as you learn what converts best for your audience.
Let AppsLift manage your creatives and rankings
Meeting requirements is the baseline; designing, testing, localizing, submitting, and ranking a full creative strategy is the real work. AppsLift handles all of it. Since 2012 we have pushed 400+ iOS and Android apps to the top of store search, pairing keyword rankings with the conversion optimization that turns impressions into installs.
Start with a free AppsLift audit: paste your App Store link, pick your markets, and see your real keyword positions plus the install value of the Top 3. When you want your creatives and rankings handled for you, talk to our team. Next, read our guide to Google Play screenshot sizes and generators.
Want your app in the Top 3 for these keywords?
AppsLift ranks iOS & Android apps in App Store & Google Play search by your target keywords — 400+ apps pushed to the TOP since 2012, any geo, pure organic installs. Get a free ASO audit of your app, or order a ranking campaign.