17 App Store Screenshot Mistakes That Hurt Downloads

TL;DR: The most expensive App Store screenshot mistakes are text too small to read in search, raw screens with no message, a splash or login screen first, and features described instead of benefits. Technical slips such as wrong sizes, alpha channels and messy status bars cause upload errors, while outdated or misleading screens risk rejection under Apple's Guideline 2.3.

These are the mistakes that make shoppers scroll past before they've understood what your app does. Each one is the flip side of a rule in our App Store screenshot best practices.

1. Text too small to read in search results

In search, portrait screenshots appear three across, so each is about a third of the screen wide. A 60 px caption on a 1290 px canvas becomes unreadable. Fix: set headlines around 120–150 px on a 1320 px wide canvas and keep them to 3–6 words. Our guide to fonts for App Store screenshots shows the math.

2. Raw screenshots with no captions

A bare capture of your home screen asks shoppers to figure out the value themselves. Most won't. Fix: give each screenshot a headline that names the benefit, and frame or crop the UI so the relevant part is large enough to see.

3. Several messages on one screen

"Track habits, set reminders, sync with Health and share with friends" says four things and lands none. Fix: one screenshot, one message. If a feature needs explaining, give it its own screen.

4. Low contrast and busy backgrounds

Photos, patterns and gradients behind thin text make captions disappear at thumbnail size. Fix: use solid or gently graded backgrounds behind text, keep strong contrast and check the set at small size on a real phone.

5. Inconsistent style across the set

Different fonts, colors or device angles on each screen make the gallery look stitched together. Fix: one template, one font family, one accent color. Vary the content, not the system.

Even a beautiful set fails if it tells the wrong story or tells it in the wrong order.

6. Leading with the splash, login or onboarding screen

These screens show nothing about what the app does. Apple's Guideline 2.3.3 says screenshots should show the app in use, not merely the title art, login page or splash screen. Fix: open with your strongest result screen and your clearest value proposition.

7. Feature names instead of benefits

Internal names mean nothing to a stranger. Compare:

Fix: write what the user gets, then show the screen that proves it. See more patterns in App Store screenshot captions.

8. Burying the best feature

The first three screenshots are the ones visible in search results, and many people never swipe further. Fix: put your main promise and your most differentiating feature in screens one to three, and save settings, integrations and extras for later.

9. Ignoring what searchers came for

If people find you by searching "budget planner", a first screenshot about community features feels off-target. Fix: check the keywords that bring you traffic and make sure the first screens answer that intent directly.

These won't always hurt conversion, but they block uploads or make the set look careless.

10. Wrong dimensions or stretched images

App Store Connect only accepts exact pixel sizes. The required iPhone set is 6.3-inch (1206 × 2622 or 1179 × 2556), and iPad apps need 13-inch screenshots. Stretching a capture to fit distorts the UI. Fix: design at the exact size and check the App Store screenshot size guide before exporting.

11. Transparent PNGs with an alpha channel

Images with an alpha channel are a common cause of upload problems, and Google Play rejects them outright. Fix: export flattened JPEG or PNG without transparency. The free screenshot size checker flags alpha channels and tells you which store slot an image fits.

12. A messy status bar

Low battery, a carrier name, notifications and odd times distract and look unpolished. Google's own screenshot guidance asks for full battery, Wi-Fi and signal icons. Fix: override the simulator status bar before you capture, as explained in clean status bar for screenshots.

13. Blurry, upscaled or over-compressed images

Upscaling a small capture or saving a gradient at low JPEG quality produces soft text and banding. Fix: capture at the device's native resolution and export at full quality.

Apple's Guideline 2.3 asks that screenshots accurately reflect the app's core experience and stay up to date with new versions. Breaking that can mean rejection, as explained in Apple's App Store screenshot guidelines.

14. Showing UI that isn't in the app (or isn't anymore)

Concept art, planned features or an old design after a redesign all mislead shoppers. Fix: update screenshots with every visible UI change and only show features available in the current version.

15. Other platforms' devices, names or badges

Guideline 2.3.10 asks you not to include names, icons or imagery of other mobile platforms in your metadata. An Android phone in an iOS screenshot, or a Google Play badge, invites trouble. Fix: keep store-specific sets, with Apple devices on the App Store and no store badges on either.

16. Real personal data or unlicensed content

Guideline 2.3.9 asks you to show fictional account information instead of data from a real person, and to have the rights to everything you show. Fix: use demo accounts with invented names, avatars you're allowed to use and content you own or license.

17. English screenshots in localized listings

Translating your description but leaving English captions in your screenshots sends mixed signals, and half-translated sets with overflowing German text look worse than English. Fix: localize captions for your priority markets, capture the UI in that language where possible and check every headline for overflow. Our guide on how to localize App Store screenshots covers the workflow.