App Store Screenshot Requirements: A Pre-Submission Checklist

The requirements that affect your asset list

Apple can scale the highest-resolution screenshots down when the interface is identical across device sizes. That saves production time, but it does not remove the need to review tablets, landscape layouts or any device family where the interface genuinely changes. Always verify the current table in App Store Connect before export because supported devices and accepted dimensions evolve.

Google Play may show screenshots in search, recommendations and the store listing. Its minimum of two is enough to publish, not necessarily enough to explain the product. Four coherent portrait or landscape screenshots at the recommended resolution provide a better working set.

Order the screenshots around user decisions

Do not begin with every feature the team built. Begin with the questions a visitor asks in a few seconds.

1. What result does this app help me get?
2. What does the main workflow look like?
3. Why should I trust it with my time, money or data?
4. What makes it useful after the first session?
5. Is it right for my situation?

For a course app, the first image might show the learning result, the second the lesson experience, the third progress or teacher feedback, and the fourth offline access. For delivery, lead with ordering and expected arrival, then show live status, payment and support. A screenshot set should read like a short product demonstration, not a list of menu items.

Keep captions readable and claims honest

Captions need enough contrast, a short line length and a size that remains readable in the store gallery. Put one clear idea on each image. Do not depend on small labels inside the captured interface to explain the feature.

Use current screens and realistic sample data. Do not show an admin function, payment method, medical result, AI capability or subscription benefit that is unavailable in that build or market. Avoid rankings, awards, testimonials or price claims unless the relevant store rules clearly allow the exact use and the claim can be maintained.

Build the asset package before the final build

The screenshot owner needs a stable build, test accounts and approved sample data. Capture the clean state of every important screen, then place those captures in a reusable layout system. Keep source files separate from final exports so text, device frames and localization can be changed without recapturing everything.

Before upload, check:

• accepted pixel dimensions and file format;
• portrait or landscape consistency;
• no transparency, accidental status-bar data or private information;
• correct device family and current interface;
• readable caption at actual gallery size;
• correct language, currency, date, address and payment context;
• the first three images still make sense without the rest;
• no important element sits in a likely crop or overlay zone;
• filename, version and locale are traceable internally.

Review localization as a product decision

Translation is only one layer. A market may need different currency, examples, trust signals, payment methods or feature order. That is why the localized set should be reviewed by someone who understands the product and the market, not only by the person exporting graphics.

Read the separate screenshot localization guide for the market-specific work. The technical master and the localized variants should share a system, but they do not have to tell exactly the same story.

Measure the set after release

Record the date and order of each screenshot change. Compare product-page views, installs and conversion by store and locale. Change one clear hypothesis at a time: the first promise, screenshot order, caption, product context or visual treatment. A conversion lift that leads to weaker activation can mean the store promise is stronger than the actual first-session experience.

How Appfyl handles store assets

Appfyl connects screenshots to the release checklist, analytics and the real product flow. We plan the required states during development, use safe sample data, verify device layouts and leave enough time for localization and store review. That reduces the last-minute situation where a marketing image exposes an unfinished screen or a release is delayed by missing assets.

Want to see how Appfyl turns scope into shipped products? View Appfyl cases.

A five-screen story that survives the thumbnail test

Write the headline before choosing the layout. A practical target is two to six words, with the strongest search phrase included only when it sounds natural. Then hide the interface mentally and read only the headlines. They should still tell a persuasive story: problem or desired outcome, the change the app creates, proof, the feature that delivers it and a final result or trust signal.

Give every frame one job. Make the first screenshot a cover with one large outcome, one dominant visual and at most one proof point. Across a five-image set, use real product UI as evidence in two or three frames; leave one or two frames for a human situation, result, catalog, proof object or other no-phone composition. Keep the same product design system, but change scene structure, crop, density and color rhythm so adjacent images do not look like the same template.

At preview size, one headline and one dominant proof element usually beat several labels. Avoid vertical text, five centered phones, tiny interface walls and a gallery that can be shuffled without changing its meaning. When producing standard iPhone portrait files, Appfyl uses 1290 × 2796 as the working preset. Export each screenshot as a separate full rectangular canvas with square outer corners, then validate it against the current device requirements before upload.

Related Appfyl guides

• ASO before mobile app launch
• App Store screenshot localization
• Mobile app launch checklist
• App Store rejection fixes
• Appfyl feature brief quiz

Want to see how Appfyl turns scope into shipped products? View Appfyl cases.

Next step

List the device families, locales and five product promises your launch needs. Add them to the Appfyl feature brief quiz so store assets, analytics and release work are included in the estimate.

Questions people ask