App Store Screenshot Generator: 5 Frames That Convert

Use an app store screenshot generator workflow to build five portrait 9:16 frames, with the first two frames delivering your complete acquisition pitch. Search-result previews commonly show only the first 2–3 screenshots before a person scrolls, so put an outcome-led caption above a recognisable in-app screen in frames 1 and 2. Reserve the top 20% of each 1080 × 1920 working canvas for the caption, show one user benefit per frame, and translate captions for each storefront locale before paying to localise the UI.

Key takeaways

•Search-result previews commonly expose only the first 2–3 screenshots without a scroll.
•Apple App Store listings accept 1–10 screenshots per supported device size.
•Google Play requires at least 2 screenshots and accepts up to 8 per device type.
•A 1080 × 1920 px canvas gives a 9:16 working frame for portrait Play Store assets.
•Reserve the top 20% of a 1080 × 1920 canvas—384 px—for a readable caption zone.

This guide is for mobile product designers, founders, and engineers who can capture iOS and Android app screens and prepare store-listing assets.

Time: 45 minutes · You'll need: Five representative in-app captures from iOS and Android, A 1080 × 1920 px portrait composition file in Figma, Sketch, or similar, App Store Connect access and Google Play Console access, A spreadsheet containing storefront locales and approved benefit copy

What's on this page

•Write the two-frame acquisition pitch
•Choose one outcome for each app screenshot design
•Compose portrait play store screenshots at 9:16
•Localise captions before localising the UI
•Export and validate the five-frame set
•Reference table

•Common mistakes
•FAQs

Build app store screenshots in five frames

1. Write the two-frame acquisition pitch

Write the message for frames 1 and 2 before arranging any device mockups. Search-result previews commonly reveal only the first 2–3 screenshots without scrolling; the exact crop and count vary by storefront, device, and placement. Treat frame 1 as the primary promise and frame 2 as proof that the promise is attainable. A finance app could lead with “Know what you can spend today” above its balance screen, then “Catch subscriptions before they renew” above its recurring-payment view.

Do not make frame 2 dependent on someone reading frame 4. Each must make sense when shown alone. Write three more benefits for frames 3–5: activation, habitual use, and a differentiator. This creates a five-frame set in which the first two carry the full pitch and the remaining three answer likely objections.

Tip: If frame 1 says only “Personal finance made simple,” replace it with the decision the person can make after opening the app.

2. Choose one outcome for each app screenshot design

Assign exactly one user outcome to every frame. Use a result, decision, or completed task as the caption; do not name a feature. “Plan dinner in 10 minutes” is an outcome. “Smart meal planner” is a feature label. “Send an invoice before you leave the job” is an outcome. “Mobile invoicing” is not.

Match the in-app capture to the claim. If the caption promises a faster decision, show the screen where that decision is visible, not a settings screen or a generic home screen. Keep interface text large enough to identify the task, but do not ask the screenshot to explain the product alone. The caption-above-device composition is the dominant store-listing pattern because it gives the viewer the claim before they have to decode a small interface. A bare screenshot starts with navigation chrome, labels, and unfamiliar data; an outcome caption supplies the reason to inspect it.

Tip: Use the test “What changes for the user?”; if the answer contains the feature’s product name, rewrite the caption.

3. Compose portrait play store screenshots at 9:16

Create a 1080 × 1920 px, 9:16 working canvas for each portrait composition. Reserve the top 20%—384 px on this canvas—for the headline and any short supporting line. Place the device, cropped app screen, or full-bleed interface below that zone. Keep the caption on a plain or controlled background rather than over variable app content, so translation does not make the image unreadable.

The 9:16 canvas is a composition system, not an Apple upload-size rule. Google Play permits screenshots in 16:9 or 9:16 orientation, and Play asset files must meet its current image requirements. Apple requires screenshots for the device display sizes you support in App Store Connect, so export the same composition into Apple’s accepted pixel dimensions rather than uploading a generic 1080 × 1920 file. Preserve the caption’s relative top zone when resizing; do not scale the whole artwork until text reaches the notch or status-bar area.

Tip: Keep one editable master per frame; flattening text into each exported device size makes later locale changes slow and error-prone.

4. Localise captions before localising the UI

Translate and review the five captions for each App Store and Google Play storefront locale before commissioning translated interface captures. Caption text carries the acquisition claim, while the UI usually serves as visual proof. This order exposes problems early: German, Finnish, and Portuguese strings can require materially more width than English, and a two-line caption may need a different line break within the 384 px top zone.

Create one approved caption sheet with locale, frame number, source claim, translated claim, and line-break instruction. Then duplicate the 1080 × 1920 master for each language and fit the caption without shrinking it into a label. Only localise the UI when on-screen language is necessary to support the claim, when the product is already translated, or when visible English would undermine trust in that market. Do not fabricate a translated UI solely for a store image; it must match the app experience people install.

Tip: For right-to-left storefronts, review both text direction and the visual reading order of the device and directional illustrations.

5. Export and validate the five-frame set

Export five final frames for each platform and locale, then validate them against the current upload rules in App Store Connect and Google Play Console. Apple allows 1–10 screenshots per supported device size. Google Play requires at least 2 screenshots and allows up to 8 per device type. A five-frame campaign therefore fits both platforms without forcing a different narrative.

Use the manual route when needed: resize each approved master to Apple’s required device screenshot dimensions, export the required PNG or JPEG files, and upload them to the matching App Store Connect device slot. For Google Play, export compliant 9:16 assets and upload them under the relevant phone or tablet store-listing section. Check frame order on actual mobile search and product-page previews before release. If you want to automate production after approving the masters, floow.design’s free App Store Screenshot Generator can caption and frame up to 10 screenshots, then export store-size variants; keep only the first 8 for a Google Play device type.

Tip: Upload frames 1 and 2 first, then inspect the storefront preview at phone scale before spending time polishing frames 3–5.

Reference table

Store limits and working composition

Platform or canvas	Figure	Use
Apple App Store	1–10 screenshots	Per supported device size
Google Play	2–8 screenshots	Per device type
Portrait working canvas	1080 × 1920 px	9:16 composition
Caption safe zone	384 px	Top 20% of canvas

Do it with the free App Store Screenshot Generator

Caption and frame up to ten screenshots, then export them at every App Store and Play Store size at once.

Open the App Store Screenshot Generator → — free, no sign-up.

Common mistakes

Putting the product name and logo in frame 1 instead of a user outcome.

Make frame 1 state a completed benefit and show the screen that makes it credible. Brand identification can remain present but cannot consume the acquisition message.

Using five screenshots as a sequential tutorial.

Make frames 1 and 2 independently persuasive because search-result previews may not expose frames 3–5. Use later frames as proof, breadth, or objection handling.

Submitting the same 1080 × 1920 file to every Apple device slot.

Maintain the 9:16 file as a working composition, then export into the device-specific screenshot dimensions App Store Connect requires.

Translating the caption after localised interface screenshots are already finished.

Approve caption length and line breaks first. This prevents redoing five expensive interface captures when a translated headline overruns its top safe zone.

Frequently asked questions

How many app store screenshots should I use?

Use five app store screenshots when you need one complete pitch that works on both Apple and Google storefronts. Five fits within Apple’s 1–10 screenshot limit and Google Play’s 2–8 screenshot limit per device type. Put the core promise in the first two, because later frames may require a scroll to appear.

What should the first App Store screenshot say?

The first App Store screenshot should state the clearest user outcome your app produces and show the screen that proves it. Use a claim such as “See every bill due this week,” not a feature category such as “Bill tracker.” Keep the message in the caption area above the interface rather than relying on tiny in-app labels.

Do Play Store screenshots need to be 9:16?

Google Play screenshots can use either 16:9 or 9:16 orientation, so 9:16 is a strong portrait choice rather than a universal requirement. A 1080 × 1920 px master provides a practical 9:16 composition canvas. Check the current Play Console asset requirements before upload, especially if preparing tablet assets.

Why is caption-above-device better than a bare app screenshot?

Caption-above-device works better than a bare app screenshot when the caption states the benefit before the viewer has to interpret a reduced-size interface. Store previews make navigation, data, and labels hard to decode at a glance. The caption gives the interface a job: it becomes evidence for one specific outcome.

Should I localise app screenshots or captions first?

Localise captions before app screenshots because captions carry the sales claim and expose language-length problems first. Fit each approved translation into the top caption zone, then decide whether visible interface language must also be translated. Any UI shown in a listing should match the installed product in that storefront.

Where this leaves you

A conversion-oriented screenshot set is not a feature inventory. It is a five-frame argument built for a storefront where the first 2–3 images receive most of the attention. Frame 1 makes a concrete promise. Frame 2 proves the promise. Frames 3–5 show the next outcomes without requiring the viewer to follow a tutorial. Use a 9:16 master with a protected top caption zone, then export platform-specific files rather than treating one image size as universal. Your next action is to write the five outcome captions, beginning with the two claims that can win an install on their own.

Design the screens first

Describe the screen you need in plain English and floow.design generates production-ready iOS and Android layouts you can iterate on by chat, then export to Figma or code. Design your mobile app screens in floow.design first, then build.

Start designing free →

•WebP Converter — Batch-convert PNG, JPEG, WebP and AVIF in your browser, with a quality slider, optional resize and a live size comparison.
•SVG to PNG Converter — Rasterise any SVG at 1x to 4x, or export every iOS scale and Android density as one archive.
•App Name Generator: Name a Mobile App — Use an app name generator and a practical naming process to create mobile app names that f
•ASO Tool Free: Run an App Store Screenshot A/B Test — Use an aso tool free workflow to test App Store and Google Play screenshots, set a sample
•Design by AI: A Realistic Workflow for Mobile App Teams — Learn a realistic Design by AI workflow that helps mobile app teams move from clear briefs