Back to Blog

App Store Screenshots: Accurate Captures, Layout and Localization

Build screenshots around the real app experience, then check accepted dimensions and every intended localization. A decorative mockup is not evidence that a feature works.

Use the current accepted dimensions

Apple accepts multiple resolutions in some display groups and can scale suitable larger screenshots for smaller groups. You do not have to upload every device size. Apple’s screenshot specifications and upload instructions should guide the set you prepare.

Show the app in use

Choose actual screens that explain the core workflow, with fictional sample data and no private customer information. Overlays can clarify a benefit, but should not promise a feature missing from the app. Apple’s metadata guidance covers screenshots and previews.

Make the opening frames useful

Put a clear, representative task early in the sequence. “First three” is a design heuristic, not a rule requiring three particular features. Avoid filling all available slots with near-duplicates; use each frame to answer a different customer question.

Review the layout at store size

Keep captions short enough to remain readable when scaled down, but do not impose a universal word count on every language. Test line breaks, contrast, safe spacing and the visible app content. A template cannot certify the final export.

Localize the complete experience

Capture the localized app UI where supported, not just translated captions over an English screen. Review right-to-left composition, text expansion, regional formats and culturally relevant examples. Check every locale’s uploaded assets and fallback behavior rather than assuming one upload reaches all languages.

Test and measure

Use a defined Product Page Optimization test where appropriate. Keep asset hashes, treatment IDs, locale coverage and observation dates. Do not confuse a click, store impression, install or purchase: each is a different outcome with its own measurement source.

IconBundlr export and purchase scope

IconBundlr’s native iOS export contains three 1024×1024 PNG appearance assets (light, dark and tinted) and Contents.json inside AppIcon.appiconset. Appearance processing is best-effort: if foreground extraction cannot produce a distinct variant, a slot can reuse the light artwork. Review each result in Xcode. This is an iOS asset catalog, not an Icon Composer .icon file or a complete Android, macOS, watchOS, tvOS or visionOS package.

IconBundlr is free to download, with limited free generation. Available in-app purchase options can include a renewing subscription, lifetime export access and individual-icon unlock credits. The app shows the current price, included access, renewal terms and any eligibility requirements in your storefront before purchase. A subscription is not a lifetime purchase, and an icon credit does not grant unlimited generation.

Review generated artwork before publishing. An export purchase does not guarantee originality, exclusivity, trademark clearance or App Store acceptance. Check your inputs and any third-party artwork, fonts or marks against their applicable rights and the app’s terms. Read the terms.

Frequently asked questions

Can one screenshot set cover smaller displays?

App Store Connect can scale accepted larger sets according to its published fallback rules. Check the current requirements for your supported device families.

Does Xcode have a Preview in App Store screenshot button?

Do not rely on that invented step. Review the exported files and their App Store Connect presentation.

Documentation reviewed September 5, 2026. Sources: Apple screenshot specifications · Apple media uploads · Apple metadata guidance.

Explore IconBundlr

Try the available free generation, review the artwork and check the purchase terms before unlocking additional access.

Try Free →