WowShotsWowShotsAll Articles
ASO GuidesNovember 21, 20266 min read

App Store Screenshot Rejected? How to Diagnose and Fix It

Separate upload errors from App Review feedback, compare screenshots with your submitted build, and prepare a focused response before resubmitting.

WowShots AI app screenshot workflow
A visual reference from the WowShots asset workflow.
ByWowShots Team

A screenshot that uploads successfully can still raise an App Review issue. Start by recording the exact message: an upload error calls for a file check, while review feedback calls for a closer look at what the image communicates.

This guide is a diagnostic workflow, not a guarantee of approval. Apple's message and the current guidelines govern your submission.

First, identify where the problem occurred

If App Store Connect rejects the file during upload, check the selected device slot, dimensions and file format against Apple's current screenshot specifications. Export again from the source rather than stretching a finished image until it fits. Our screenshot sizes guide can help you plan the files, but check Apple's table for the current requirements.

If the submission reaches App Review, save the review message and note the guideline, affected locale and screenshot position. Do not assume the first image is the only one at issue. Open each submitted set, including translated versions, alongside the build sent for review.

Compare every claim with the submitted app

Apple's App Review Guidelines, section 2.3 require metadata to reflect the app's core experience. Under 2.3.3, screenshots should show the app in use rather than merely title art, a login page or a splash screen. Text and image overlays are allowed; they still need to describe the actual experience accurately.

For each frame, write down the action it depicts and reproduce it in the submitted build. A project-planning app might show a completed task board with the caption “See your week at a glance.” If that view exists only in a design mockup or an unreleased build, replace the capture or revise the claim. Use fictional account information and confirm you have rights to the material shown, as Apple requires under 2.3.9.

Check paid features too. Guideline 2.3.2 says screenshots and other listed metadata must clearly indicate when featured items, levels or subscriptions require additional purchases. Make the distinction understandable next to the feature; do not imply that a paid capability is included when it is not.

Check copy and context, not just the pixels

Read captions at full size and as a small preview. Remove unsupported promises, stale interface elements and irrelevant store or platform imagery. Apple's 2.3.7 addresses metadata containing prices, terms or descriptions that do not belong in that metadata type; 2.3.10 addresses references to other mobile platforms or alternative marketplaces, with an exception for specific approved interactive functionality. Check the exact wording before deciding how it applies.

Apple also requires screenshot metadata to be appropriate for a 4+ audience, even when an app has a higher age rating. Review the image itself and any overlays, not only the app's age-rating answers.

When screenshots are localized, compare the translation with the actual feature and purchase conditions in that market. A caption that fits beautifully but changes the promise still needs revision. Use the localization checklist to track versions and reviewers.

Prepare a focused correction

Keep a small record so the next person can verify the change:

RecordExample
FeedbackGuideline and exact reviewer concern
ScopeDevice slot, locale and screenshot positions
EvidenceBuild version and the screen used for each replacement
ChangeOld claim, revised claim and exported file
VerificationUpload result and final order in App Store Connect

Fix the issue across all affected sets, then inspect the uploaded result for cropping, legibility and ordering. If the reviewer asks for clarification, respond to the actual concern and explain the concrete changes through App Store Connect. If you disagree or need help, Apple's guidelines describe ways to contact App Review and appeal. Whether a new build is necessary depends on the issue and the state of the submission; check App Store Connect rather than assuming.

Build a reusable review pass

Before the next release, ask someone who did not design the images to compare each claim with the current build. Keep source captures, localized copy and exports together, so an interface change prompts a check of the affected frames.

AppShot Maker's rejection guide organizes common problems by guideline. AppGrowthKit's guide also emphasizes matching images to the submitted build. Both are useful starting points; Apple's current wording and the review message take precedence.

If you need to rebuild a set, use the WowShots App Store screenshot generator with captures from your actual app. Review every generated frame yourself, then choose a paid credit pack for the work you need. Generation does not replace Apple's review.

App StoreApp Reviewscreenshots

Move from research to production with the tool that matches your next step.

Related Articles

Create a reviewable App Store and Google Play screenshot direction with AI assistance.