7 screenshot mistakes that quietly kill downloads.

Most app listings don't lose the install in the description — they lose it in the first two frames of the screenshot carousel, in under a second. These are the seven mistakes we see constantly, why each one costs you, and the five-minute fix.

1. Raw UI dumps with no headline

The most common mistake by far: exporting the app's actual screens and uploading them untouched. A raw screenshot asks the visitor to do the work — figure out what the app is, find the value, imagine using it. Nobody does that work. Store visitors give each frame a fraction of a second, and a screen full of small UI text communicates nothing at that speed.

The fix: every frame gets one short headline that states a benefit — "Track every subscription," "Fall asleep faster" — with the UI shown as evidence below it. Benefit first, interface second.

2. Describing features instead of outcomes

"Customizable dashboard." "Powerful sync engine." Feature language makes the visitor translate capability into value, and they won't. The listings that convert speak in outcomes: not "AI-powered budgeting engine" but "Know where your money goes."

The fix: for every headline, ask "so what?" until the answer is something the user feels. Then use that.

3. Burying the best frame

On both stores, only the first two or three screenshots render in search results — before anyone even opens your listing. Teams routinely open with a splash screen, a login page, or an onboarding carousel, and save the killer feature for frame five. Frame five may as well not exist.

The fix: lead with your single strongest "this is why you want me" moment. If you're not sure which frame that is, it's the one you'd show a friend first.

4. Wrong sizes — or one size stretched everywhere

Apple wants exact pixel dimensions per display class (1320×2868 for iPhone 6.9", 2048×2732 for iPad 13"), and Google Play has its own set. Stretching one export into every slot produces blurry, letterboxed frames — and mismatched dimensions get uploads rejected outright. Details in our size guide.

The fix: design once, export per-size. Any tool worth using renders every slot from a single design instead of making you rebuild per device.

5. A carousel with no visual system

Five frames, five different background colors, three fonts. Each frame might be fine alone, but as a carousel it reads as chaos — and chaotic listings read as low-quality apps. Stores show your frames side by side; they're a set, not five posters.

The fix: one template, one palette, one type scale across the whole set. Vary the content per frame, never the system.

6. Text the thumbnail can't survive

Your screenshots render at full size on your monitor exactly once — during design. Everywhere else they're thumbnails: search results, the top of a crowded listing, a phone held at arm's length. Ten-word headlines in 40px type turn into gray smudge at that scale.

The fix: three to five words per headline, set enormous. If it isn't readable at 25% zoom, it isn't readable where installs happen.

7. Shipping once and never testing

Screenshots are the highest-leverage asset on the listing, and most teams ship a set at launch and never touch it again. Meanwhile headline order, first-frame choice, and even background color measurably move conversion — Apple's own product-page optimization exists because screenshot variants change install rates.

The fix: treat the set as living marketing. Re-render a variant in minutes, ship it, and watch what the store analytics say.

Fix all seven in one pass

This is exactly what ShotCanvas is for: drop in your raw screens, pick one of 26 professional templates (or let AI compose the set and write the headlines), and export pixel-exact PNGs for every App Store and Google Play slot — or publish straight to both stores. The free tier covers your first sets, no credit card.