Why App Store Screenshots Get Rejected (And How to Fix Them)

Last verified: September 9, 2026

A practical guide to troubleshooting App Store Connect screenshot rejections, understanding Apple Guideline 2.3.3, and fixing metadata errors before resubmission.

Understanding App Store Guideline 2.3.3

App Store Review Guideline 2.3.3 states that screenshots must accurately show the app in use, highlighting its main features and functionality. When Apple human reviewers reject a metadata submission, they routinely cite Guideline 2.3.3 alongside specific screenshot asset errors.

Receiving an App Store rejection notice delays your launch timeline because you must update your marketing graphics and submit a new app build for approval. Understanding the exact causes behind App Store Connect validation failures helps you audit your assets prior to submission.

Alpha channels and transparency errors

The single most frequent automated rejection error in App Store Connect is uploading PNG files containing an alpha channel. Unlike general web graphic standards, Apple's upload pipeline strictly forbids transparency in screenshot files.

If your PNG image editor exports files with 32-bit RGBA color channels, App Store Connect halts file processing and displays an error message during transfer: "Images cannot contain alpha channels or transparency."

• The Fix: Re-export your screenshot files as 24-bit RGB PNG images. Remove the alpha channel entirely or flatten all transparency onto a solid background color before uploading.
• Color Profile Check: Ensure your image editor exports in RGB or sRGB. Images saved in CMYK or grayscale color spaces cause immediate validation errors.

Mismatched or unreleased hardware frames

Using hardware device frames around your UI captures is standard practice in app store marketing. However, using incorrect or mismatched hardware bezels leads directly to metadata rejections during manual app review.

Common hardware frame rejection triggers include:

• Depicting legacy home-button bezels on modern 19.5:9 display submissions (such as 6.9-inch or 6.5-inch slots).
• Mismatched camera cutouts: Displaying an older notch cutout on a 6.9-inch submission designed for iPhone 16 Pro Max hardware.
• Unreleased device concepts: Rendering hypothetical future device bezels or non-standard Apple hardware frames.

Reviewers inspect screenshot sets to ensure the hardware framing matches the target display tier. For a comprehensive overview of required device sizes and resolutions, review our reference on App Store screenshot sizes.

Placeholder text and dummy screenshots

Submitting screenshots with placeholder text such as "Lorem Ipsum", "Sample Headline", or test user accounts (e.g., "John Doe test@test.com") violates Guideline 2.3.3. Reviewers flag placeholder content because screenshots must represent a real operational app experience.

• Replace dummy text with real, polished value proposition headlines and localized app copy.
• Ensure all sample data shown in UI cards (such as dates, transaction amounts, or user names) looks realistic and professional.
• Do not display blank screens, broken image loading states, or development debug menus in your marketing graphics.

Pricing, discounts, and promotional text

Apple strictly separates app metadata graphics from pricing and subscription management. Including explicit pricing details, discount percentages, or temporary promotional offers in your screenshot text overlays is prohibited.

Avoid captions containing text such as:

• "Now only $4.99 per month"
• "50% off holiday sale"
• "Free subscription included"

Because app prices vary by currency tier and regional store location, placing fixed price claims in screenshots misleads users in foreign store locales. Manage all pricing information via App Store Connect In-App Purchase and Subscription settings instead.

Unlicensed logos and third-party trademarks

Displaying copyrighted third-party logos, trademarked brand icons, or social media badges without explicit authorization results in immediate metadata rejection. Apple protects intellectual property rights and requires developers to prove licensing rights for any third-party imagery used in marketing assets.

• Remove third-party corporate logos, partner badges, and social media brand marks from UI screenshots.
• Replace trademarked vector icons with generic, open-license iconography.
• If your app integrates directly with an official API partner, keep partner logo placement subtle and ensure you hold written usage permission.

For more detailed technical guidelines on iOS asset formatting, cross-reference Apple App Store Review Guidelines (Section 2.3) and our master guide on App Store screenshot requirements.

Common questions

Why did Apple reject my screenshots under Guideline 2.3.3?

Guideline 2.3.3 rejections occur when screenshots do not accurately represent the app in use, show unreleased hardware frames, contain placeholder text, or include misleading promotional claims.

How do I fix the alpha channel upload error in App Store Connect?

To fix alpha channel errors, open your screenshot images in an editor and re-export them as 24-bit RGB PNG files with transparency flattened onto a solid background color.

Can I put pricing or discount offers in my App Store screenshots?

No. Apple prohibits explicit pricing claims, currency amounts, or time-limited discount offers in screenshot graphics. All pricing must be managed via App Store Connect pricing tiers.

Are device frames allowed in App Store screenshots?

Yes. Device frames are allowed as long as the hardware frame accurately matches the aspect ratio, bezel style, and screen generation of the targeted submission slot.

How long does it take for Apple to re-review updated screenshots?

Once you re-submit updated screenshot assets in App Store Connect, manual review typically takes between 24 to 48 hours.