Start with store-ready dimensions
iPhone portraits at 1290×2796 (Apple's 6.9-inch slot, scaled down for smaller iPhones) are the baseline for most iOS listings. Correct sizing keeps type crisp next to competitor screenshots and avoids App Store Connect rejections for the wrong resolution. When you also ship Android, export Play phone 1080×1920 from the same creative system, but never assume one PNG fits both stores without a resize check.
Open the App Store screenshot generator when you have production captures ready. For deeper guidance, read the App Store screenshot size guide.
Pair visuals with ASO copy
Each slide should lead with a user benefit, not a feature dump. StoreShots generates headlines from your real in-app screens so the marketing frame and the product stay aligned. If a headline needs a paragraph to make sense, choose a clearer capture or rewrite the promise.
Use App Store screenshot copy guidance and App Store screenshots that increase downloads as drafting aids. The frame should communicate at thumbnail size before the shopper reads the listing description.
Plan the first five slides
Open with the strongest outcome, then prove the main workflow, show a differentiator, add truthful proof, and finish with context. Five distinct slides beat ten repeated screens. Slide one must earn the scroll without relying on a caption under the image.
Use the App Store screenshot order guide as a slide-by-slide checklist, then adjust for your category. Games, utilities, and B2B tools share the same honesty rule: do not promise UI the build does not contain.
Keep UI truth visible
Uploaded screens remain the product source. Surrounding art can add hierarchy and brand, but it should never invent features. Remove beta labels, placeholder data, and outdated navigation before generating the pack. Screenshots are promises made at the moment of install.
Review before App Store Connect
Check headline contrast at phone size, safe areas, file dimensions, ordering, and current Apple requirements. Preview the exported ZIP on a real phone before uploading. StoreShots creates assets and exports; it does not submit to App Store Connect or guarantee approval. Run the store screenshot checklist as a final gate.
Localize the story, not just the words
When you add a market, translate the benefit and the supporting UI context together. Longer strings may need a new line break or shorter headline. Keep the app capture in the language users will see after install whenever the product supports localized builds. See how to localize App Store and Play Store screenshots.
Refresh only what changed
A new release does not always require a complete redesign. Replace outdated screens, update claims tied to changed features, and preserve the visual system that already explains the product. Keep the final ZIP and copy decisions with the release notes so the next update stays coherent.
A repeatable iOS workflow
Collect production captures from the build you will ship.
Define the audience, promise, and five-slide story.
Generate narrative frames in StoreShots; one credit covers each slide.
Revise the weakest slide; approved-work re-export is free.
Review the ZIP on a phone, then upload manually to App Store Connect.
Record what changed for the next release.
When you do not have screens yet
The App Store generator is for real product screens. If the product is still a concept, start in the Mobile UI hub and AI Mobile UI generator to explore connected flows and export HTML, React, and React Native for engineering. Switch back once production captures exist.
Dual-store strategy and comparisons
Aspect ratios and messaging density differ between iOS and Android carousels. Read Play Store vs App Store screenshot strategy and the sibling Play Store hub. Play phone screenshots are 1080×1920; the 1024×500 feature graphic is a separate asset StoreShots does not generate yet.
For conversion craft and mid-funnel research, use the ASO hub and the comparison set: StoreShots AI vs. storeshots.org, StoreShots vs AppScreens, StoreShots vs ScreenshotWhale, and Best AI app store screenshot generators 2026.
Use samples as a quality bar
Review samples for hierarchy, legibility, device scale, and consistency across the set. Samples show possible output; they are not customer case studies or a guarantee that every category needs the same composition. A strong pack passes product, design, and operations review before upload.
Conversion details that still matter
Color hierarchy, device framing, and background treatments should support the product UI, not bury it. Prefer high-contrast headlines, consistent device scale, and brand backgrounds that do not look like stock wallpaper. See App screenshot design best practices and the AI workflow from raw captures.
If you are evaluating AI composition, read AI app screenshot generator vs designers. Many teams use a hybrid: StoreShots for speed on truthful frames and a designer for brand-critical heroes.
Pair the hub with the generator
Read dimensions and copy guides before opening the generator, then return to the checklist after the first draft. The useful loop is education, generation, review, and a small revision—not a single prompt followed by an immediate upload.
CTA: Generate App Store screenshots · See pricing · Browse samples · All topics