# StoreShots AI > StoreShots AI generates App Store and Play Store screenshots from raw iOS or Android app screens, designs multi-screen mobile UI/UX from a prompt with HTML, React, and React Native export, and creates app mascot GIFs with variant trees. Listing PNGs at 1290×2796 (App Store) and 1080×1920 (Play Store). Canonical site: https://storeshotsai.com/. Short index: https://storeshotsai.com/llms.txt. Summary: https://storeshotsai.com/ai.txt. Support: clyrolabs@gmail.com. StoreShots AI is the ClyroLabs product at storeshotsai.com. It is not the unrelated open-source project at storeshots.org. ## AI models StoreShots AI uses Claude Opus 5.5 from Anthropic as its core text and vision model: it reads and understands your uploaded app screenshots; writes ASO headlines and subtext for every store slide; plans layouts, device placement, and the campaign story; runs quality checks on generated slides; and writes Mobile UI screens as HTML, then converts them to React and React Native on demand. Background art, mascot images and the in-app photos inside Mobile UI screens come from dedicated image-generation models (Google Gemini image models or OpenAI GPT Image). - Text & vision model: **Claude Opus 5.5** by Anthropic - Claude Opus 5.5 reads and understands your uploaded app screenshots - Claude Opus 5.5 writes ASO headlines and subtext for every store slide - Claude Opus 5.5 plans layouts, device placement, and the campaign story - Claude Opus 5.5 runs quality checks on generated slides - Claude Opus 5.5 writes Mobile UI screens as HTML, then converts them to React and React Native on demand - Claude Opus 5.5 art-directs every mascot — a fixed character bible for the base, variants and animations — and quality-checks each image, regenerating once when it misses - Images: Background art, mascot images and the in-app photos inside Mobile UI screens come from dedicated image-generation models (Google Gemini image models or OpenAI GPT Image). - Uploaded app screens stay the UI source; the AI composes marketing around them and does not redraw the product UI. ## Pricing - Starter: $10 for 50 credits - Studio: $18 for 100 credits - Credits never expire and work across store screenshots, Mobile UI, and Mascot Studio. No subscription. - 1 credit = 1 final store screenshot slide, 1 Mobile UI screen, 1 mascot base PNG, or 1 mascot variant; 2 credits = 1 mascot GIF; 0.5 credit = 1 wizard preview frame; re-export is free. - Live pricing: https://storeshotsai.com/pricing ## How it works ### Store screenshots 1. **Create a project** — Choose your app niche, target store (Google Play or Apple App Store), brand color, and language for ASO screenshot copy. 2. **Add your app screens** — Upload one to ten in-app captures from the same iOS or Android app. Optionally preview one App Store or Play Store frame before generating the full pack. 3. **AI renders every slide** — StoreShots AI adds ASO headlines, backgrounds, and a consistent device frame — one polished App Store or Play Store screenshot per uploaded screen. 4. **Download store-ready PNGs** — Export Play Store screenshots at 1080×1920 or App Store screenshots at 1290×2796. Chat-edit any single slide, then re-export for free. ### Mobile UI/UX from a prompt 1. **Describe the app** — Open Mobile UI/UX, write a short product brief, and optionally attach reference images for color and photography. 2. **Plan connected screens** — StoreShots AI proposes a multi-screen flow — home, detail, checkout, and related states — so the visual language stays consistent. 3. **Generate on a live canvas** — Each screen renders on the canvas. Chat-revise one screen without regenerating the rest of the set. 4. **Export HTML, React, and React Native** — Download a ZIP with PNG renders plus HTML, React, and React Native code for development. One credit equals one Mobile UI screen. ### Mascot Studio 1. **Brief the character** — Open Mascot Studio and describe your brand character — species, colors, personality, and where it will appear. 2. **Lock a base mascot** — Generate still PNG options, pick a base, then create variants that keep the same silhouette and palette. 3. **Animate and export** — Turn the base into transparent GIF loops for celebrate, idle, and similar moments. One credit equals a base or variant; two credits equal a GIF. ## Products ### App Store screenshot generator for 1290×2796 listings URL: https://storeshotsai.com/app-store-screenshot-generator Upload real iPhone screens from your app. StoreShots AI writes ASO headlines, frames each capture, and exports App Store screenshots at 1290×2796 — accepted in App Store Connect's 6.9-inch iPhone slot. - Portrait size: 1290 × 2796 px (accepted for the 6.9-inch iPhone slot) - Format: PNG, ordered ZIP - Copy: Editable ASO headlines and subtext - Device: iPhone frame or frameless art plate - **Correct iPhone listing size** — Every export is 1290×2796, a size App Store Connect accepts for the 6.9-inch iPhone slot. No Photoshop canvas math, no crop surprises. - **ASO copy on every slide** — Headlines and supporting lines are written from the actual UI you uploaded, so the listing explains the product instead of repeating the app name. - **One credit per screenshot** — 1 credit = 1 generated App Store slide. Re-exporting an approved set does not charge again. Packs start at $10 for 50 credits. ### Turn real iPhone screens into a clear App Store story Start with the product moments that already show value: the onboarding payoff, primary workflow, differentiator, or a useful empty state. Upload those captures, describe the audience and promise, and let StoreShots map them into a sequence instead of a random gallery. Your uploaded screen remains the UI source inside the device frame. StoreShots composes the surrounding marketing art, typography, backgrounds, and ASO copy suggestions; it does not redraw the product UI. Browse [sample packs](/sample) before you buy, and confirm Apple's current requirements before submitting. - Lead slide one with a user outcome, not a logo splash. - Give each slide one job: promise, workflow, differentiator, proof, or context. - Inspect copy at phone scale and keep claims truthful to the shipped app. ### A practical App Store screenshot checklist A focused five-slide story is usually stronger than ten repeated frames. Use one visual system across the set, keep headline contrast high, and preview the ordered ZIP before uploading to App Store Connect. 1. Collect sharp captures from the same iOS build. 2. Define one audience and one outcome before generating copy. 3. Check the strongest screen on slide one. 4. Revise weak slides individually instead of rebuilding a finished pack. 5. Review the final PNGs on a phone and against current Apple guidance. ### What the App Store generator does not do StoreShots creates listing assets and copy suggestions. It does not submit App Store Connect metadata, guarantee approval or ranking, or replace keyword research and policy review. If the app is not built yet, start with [AI Mobile UI](/ai-mobile-ui-generator); if Android is also ready, use the [Play Store generator](/play-store-screenshot-generator) for its native phone canvas. ### Use the same creative direction across stores A shared product story should survive both platforms, but the exports should remain native to each store. Keep the promise, audience, and slide order aligned while using the App Store 1290×2796 canvas for iPhone and the Play workflow for 1080×1920 phone screenshots. That keeps the listing recognizable without asking one stretched image to fit two specifications. If localization is part of the launch, treat translation as an editorial pass. Languages can change line length and hierarchy, so shorten or rewrite headlines before exporting instead of shrinking type until it becomes unreadable. For a broader tool comparison, see [StoreShots vs AppScreens](/blog/storeshots-vs-appscreens). - Keep the product promise consistent while adapting line length per locale. - Use real UI states that match the build you submit. - Link to [App Store screenshot copy guidance](/blog/how-to-write-app-store-screenshot-copy) before finalizing headlines. ### Credits and a simple launch plan StoreShots uses one-time credit packs rather than a subscription. Starter is $10 for 50 credits and Studio is $18 for 100 credits; credits never expire. One credit covers one final store slide, Mobile UI screen, mascot base, or mascot variant. A mascot GIF uses two credits, and approved-work re-export is free. See [pricing](/pricing) for current pack details. A small launch can start with five strong slides: lead with the outcome, prove the main workflow, show the differentiator, add truthful proof, and finish with context. Generate from real captures, revise only the weak slide, then preview the ZIP on a phone before upload. [See generated App Store examples](https://storeshotsai.com/sample) ### A good handoff is part of the export Before a release, compare the PNGs with the live build, remove claims that are not available to every user, and ask someone unfamiliar with the app to explain the story from the first three slides. That quick review catches vague headlines, tiny type, and screens that require too much context. StoreShots accelerates repetitive production, but it does not replace App Store Connect review, accessibility judgment, or release management. Keep the source captures, copy decisions, and final ZIP with the launch checklist so the next update can refresh the changed slides instead of starting from a blank canvas. ### A repeatable App Store release workflow For each release, collect the current production captures, identify the one promise that matters most, and decide which slides need a new screen. Generate a baseline, inspect it at thumbnail size, and ask someone who does not know the app to explain what they think it does. If their answer does not match the product, fix the headline or the screen before upload. Keep the accepted copy and final images with your release notes. This turns screenshot production into a small repeatable system: refresh changed UI, preserve the visual grammar, and avoid paying time to rebuild slides that still represent the product accurately. ### What to prepare before you generate Choose captures that show the product doing useful work rather than only showing setup screens. A finance app might use the first completed review, a fitness app might show a plan becoming a completed session, and a collaboration app might show the moment a teammate gets value. The examples are prompts for thinking, not templates you must copy. Write down the audience, the primary promise, and any claim that requires proof. This gives the copy pass enough context to avoid generic headings. Keep the app name and logo in their proper role: recognition helps, but a benefit explains why someone should keep scrolling. - Use sharp captures from a current build. - Remove personal or unreleased data before uploading. - List the feature claims that must remain exact. - Decide which screen proves the promise best. #### What App Store screenshot size does StoreShots export? Portrait iPhone App Store screenshots at 1290×2796 pixels, which App Store Connect accepts for the 6.9-inch iPhone slot (alongside 1320×2868 and 1260×2736) and scales down for smaller iPhones. #### Can I edit App Store screenshot copy after generation? Yes. Chat-revise any single slide without regenerating the full pack. Re-export of an already generated set is free. #### Do I need Figma to make App Store screenshots? No. Upload the real iOS screens from your build. StoreShots AI adds headlines, layout, and the store-ready PNG size. #### How many App Store screenshots should I create? Start with five strong slides and add more only when each introduces a distinct benefit. A coherent story is more useful than filling every slot with repeated UI. #### Does StoreShots redraw my app UI? No. Your uploaded screen remains the UI source. StoreShots composes marketing backgrounds, device framing, typography, and copy around the capture. #### Can I use App Store screenshots for Google Play? Use the same approved story and captures, but export the Play phone set through the Play workflow at 1080×1920 rather than stretching an App Store PNG. ### Play Store screenshot generator for 1080×1920 phone listings URL: https://storeshotsai.com/play-store-screenshot-generator Upload Android app screens once. StoreShots AI produces a cohesive Google Play screenshot set at 1080×1920 with ASO headlines, device frames, and ZIP export for Play Console. - Portrait size: 1080 × 1920 px (phone listing) - Format: PNG, ordered ZIP - Copy: Editable ASO headlines and subtext - Also export: App Store 1290×2796 from the same slides - **Correct phone listing size** — Exports are 1080×1920 portrait — the phone screenshot size Google Play expects. No stretching a 1290×2796 iOS asset into Play Console. - **One pack, two stores** — Generate from the same screens, then export Play Store and App Store sizes from the approved slides. - **Credits that also cover Mobile UI** — The same $10 / 50 credit and $18 / 100 credit packs power listing screenshots and AI mobile UI screens. ### Build a Play Store pack from real Android screens Upload the Android screens that explain the product: the first useful moment, the main workflow, and the feature that makes the app different. StoreShots generates a cohesive phone set with headlines, subtext, device framing, and an ordered ZIP for Play Console. The UI inside the frame remains your real capture. The generator creates the surrounding listing composition and does not redraw your product interface. If you also ship iOS, the same approved story can be exported to the App Store canvas. - Treat slide one as the outcome a shopper wants. - Keep the Android set at 1080×1920; do not stretch iPhone art. - Keep feature claims and screenshots aligned with the current build. ### Phone screenshots and feature graphics are different Google Play phone screenshots tell the product story in the gallery. A Play feature graphic is a separate wide 1024×500 asset. StoreShots currently generates the phone set, not a dedicated feature-graphic export. Do not represent a 1080×1920 screenshot as a feature graphic. For feature-graphic guidance, read [feature graphic vs screenshots](/blog/play-store-feature-graphic-and-screenshots). Produce the banner separately when your listing requires it. ### Before you upload to Play Console Review the ordered ZIP on a phone, check text safe areas, and verify current Google Play asset rules. StoreShots creates files; it does not submit the listing, guarantee approval, or run closed testing. For managed Google Play testing after the build is ready, [TestMyApps](https://testmyapps.app) is a related ClyroLabs product. 1. Capture the production Android build. 2. Define the audience and benefit before generating headlines. 3. Keep the first three slides distinct and easy to scan. 4. Confirm 1080×1920 dimensions and open every exported PNG. 5. Upload only after Play policy and product truth checks are complete. ### Make the first Play slide earn the scroll The first phone screenshot is the largest opportunity to explain the app. Use an outcome-focused headline and a legible real screen. ‘Track spending in under a minute’ gives a shopper a reason to continue; ‘Welcome to BudgetApp’ only names the product. Slides two and three should prove the action and differentiator before later slides add depth or trust. Keep each slide focused. Avoid six claims around a tiny phone, do not put important text near crop edges, and check the set at thumbnail size. The [Play Store screenshot guide](/blog/play-store-screenshot-generator-complete-guide-2026) covers the broader workflow, while [Play feature graphic vs screenshots](/blog/play-store-feature-graphic-and-screenshots) explains the separate wide asset. - Slide one: outcome and strongest screen. - Slide two: core workflow in action. - Slide three: differentiator or high-value feature. - Later slides: variety, trust, and the next reason to install. ### One project can support Android and iOS If you ship on both stores, use the same product truth, audience, and narrative order, then export each platform's native canvas. App Store is 1290×2796 for the supported iPhone listing; Play phone screenshots are 1080×1920. The images should feel related, but neither should be a resized afterthought. StoreShots credits are shared across store slides, Mobile UI screens, and mascot assets. Starter is $10 for 50 credits; Studio is $18 for 100; credits never expire and approved-work re-export is free. Compare [pricing](/pricing), see [samples](/sample), or read [StoreShots vs ScreenshotWhale](/blog/storeshots-vs-screenshotwhale) if a feature graphic is a hard requirement. [Review Play Store sample packs](https://storeshotsai.com/sample) ### What belongs in a Play listing pack A useful pack explains the product in the order a new visitor needs it: the outcome, the action that creates it, the differentiator, and enough depth to make the app feel real. Keep marketing text outside the phone readable and keep in-app UI authentic. Do not use a decorative background to hide a confusing or outdated production screen. When the product is ready for a new release, refresh only the slides whose UI or positioning changed. StoreShots supports per-slide iteration and free re-export of approved work, so a maintenance release does not need to consume a full new pack for unchanged assets. ### Refresh the listing without restarting A Play listing should evolve when the production UI, core positioning, or audience changes. It does not need a new visual identity for every bug-fix release. Replace the screenshots that are stale, keep the slides that still prove the product, and review the first slide whenever the app's main outcome changes. StoreShots supports a focused review loop: upload or preserve the real screen, revise the weak slide, and export the approved pack again. Keep a dated record of the source build and screenshots so an old beta screen cannot quietly return to the listing. ### Prepare a Play project for an honest review Before generation, put Android captures in the order that a new user should understand them. If the upload order is only the order in which screenshots were saved, the generated narrative will have to fight that accidental sequence. Add a short description of the audience and the result the app creates so headlines can explain the screen rather than merely label it. After generation, inspect the first three slides together. They should feel like one listing, not three unrelated posters. Check device scale, headline length, text contrast, screenshot clarity, and whether each claim is available in the version that will be submitted. Use the [FAQ](/faq) and [pricing](/pricing) pages for official credit and export facts, not old third-party snippets. #### What Play Store screenshot size does StoreShots export? Portrait Google Play phone screenshots at 1080×1920 pixels, ready to upload in Play Console. #### Can I use the same screens for Play Store and App Store? Yes. Generate the pack once, then export 1080×1920 for Google Play and 1290×2796 for the App Store from the same approved slides. #### How many Play Store screenshots can I generate? Upload up to eight Android captures per pack (Play’s typical phone set). Each generated slide uses one credit. #### Does StoreShots generate the 1024×500 Play feature graphic? No. StoreShots currently generates Play phone screenshots at 1080×1920. A 1024×500 feature graphic is a separate asset that needs another workflow. #### Does StoreShots submit files to Play Console? No. StoreShots exports the PNG pack and ZIP; you review the files and upload them to Play Console yourself. #### Do uploaded Android screens get redrawn? No. Your real app capture stays inside the composition. StoreShots adds the surrounding frame, background, layout, and ASO copy. ### AI mobile UI generator with HTML, React, and React Native export URL: https://storeshotsai.com/ai-mobile-ui-generator Describe the app in one prompt. StoreShots AI plans connected screens with one shared design system, renders each as live HTML on the canvas — with AI-generated in-app photos and a real web font — and converts any screen to React or React Native when you need it. Export PNG renders and code as a ZIP. - Screens: Up to 12 connected screens per project - Code: HTML, plus React and React Native converted on demand - Imagery: AI-generated in-app photos and one Google Font per design - Previews: Live HTML on the canvas; PNG renders in the same ZIP - Edits: Per-screen chat revisions on the canvas - **Multi-screen, not one mock** — The generator plans a flow so home, detail, and checkout share type, color, and components instead of looking like five unrelated Dribbble shots. - **Code you can ship from** — HTML, React, and React Native export sits next to PNG previews. Use it as a starting point for the real app, not a throwaway visual. - **Same credits as store listings** — 1 credit = 1 Mobile UI screen. The same packs that generate App Store and Play Store screenshots power UI generation. ### Design a connected flow before engineering commits Start with the product, audience, and job to be done. A prompt such as ‘a calm weekly finance review for first-time budgeters’ gives the generator useful constraints. Add the states that matter—empty, loading, error, success, or confirmation—then refine the flow on the live canvas. A connected sequence such as home → detail → selection → checkout → confirmation is an exploration aid, not a promise that every edge state is production-ready. The value is shared alignment before APIs, navigation, and data wiring exist. - Name the user and their job. - Call out the screens and states that matter to the decision. - Specify density, contrast, tap-target, and visual-direction preferences. - Review transitions and repeated components, not just the hero screen. ### Export code as a handoff starting point Export HTML for browser inspection, React for a component-oriented web starting point, React Native for mobile implementation scaffolding, and PNG renders for stakeholder review. The exports are not a complete production app: connect real state and data, add navigation, replace sample assets, audit accessibility, test device sizes, and write tests before shipping. Once the real product exists, use the [App Store generator](/app-store-screenshot-generator) or [Play Store generator](/play-store-screenshot-generator) for listing assets. The same credit wallet can cover both workflows. ### Mobile UI versus store screenshots No usable screens yet? Start here. Product screens ready? Use a store workflow. Need transparent character motion? Use [Mascot Studio](/ai-mascot-generator). Teams often use all three, but generated UI still needs engineering, device testing, accessibility review, and store-policy review. 1. Prompt → connected Mobile UI flow → HTML/React/React Native + PNG. 2. Shipped screens → store pack → native App Store or Play export. 3. Brand character → mascot base/variants → transparent GIF loop. ### Choose a prompt that gives the generator product truth A good Mobile UI brief names the audience, job, tone, and screens that make the flow complete. ‘A calm weekly finance review for first-time budgeters’ gives stronger direction than ‘make a finance app.’ Add empty, loading, error, success, or confirmation states when they are important to the concept. References can guide color, photography, and density, but they do not replace review. After generation, check hierarchy, transitions, repeated components, contrast, and whether the primary task is obvious on each screen. Revise the weak screen first instead of regenerating a whole project unnecessarily. - Describe the user and job to be done. - Name the flow: home, detail, selection, checkout, confirmation, or your actual sequence. - State accessibility preferences such as contrast and tap-target size. - Use [How it works](/how-it-works) for the prompt-to-canvas workflow. ### From generated UI to engineering handoff HTML is useful for browser inspection, React is a component-oriented web starting point, and React Native is a mobile implementation starting point. PNG renders help stakeholders compare the intended visual direction with the code. None of these exports include your production backend, authentication, payments, live data, or final accessibility and device QA. Before shipping, rename components, connect real state and data, add navigation, replace sample assets, test keyboard and device behavior, audit labels and focus order, verify licensing, and write tests for critical paths. Once shipped screens exist, move to the [App Store generator](/app-store-screenshot-generator) or [Play Store generator](/play-store-screenshot-generator) for listing assets. 1. Compare PNG renders with exported code. 2. Connect state, data, navigation, validation, and error handling. 3. Test device sizes, keyboard behavior, contrast, and accessible labels. 4. Replace placeholders and verify asset licensing. 5. Run engineering tests before treating the export as production-ready. [See Mobile UI samples](https://storeshotsai.com/sample) ### Pricing and the workflow chooser Starter is $10 for 50 credits and Studio is $18 for 100 credits. Credits never expire. One credit covers one Mobile UI screen, store slide, mascot base, or mascot variant; two credits cover a mascot GIF, and approved-work re-export is free. The same wallet lets a team explore UI early and create store assets after the app is real. Use Mobile UI when you need structure before engineering. Use App Store or Play workflows when real screens exist. Use Mascot Studio when character motion is the missing launch asset. Read [pricing](/pricing), inspect [samples](/sample), and review [How it works](/how-it-works) before choosing the first project. ### A Mobile UI review checklist Before handing the export to engineering, compare the PNG render with the code, rename components to match your product vocabulary, connect real state and data, and add navigation that follows platform conventions. Check empty, loading, error, and success states rather than reviewing only the happy path. Then test common device sizes and keyboard behavior, audit contrast and accessible labels, replace sample assets, verify licensing, and write tests for critical actions. The generated flow is valuable because it makes product decisions visible early; it is not a claim that backend and native implementation have been completed for you. ### Prompt examples without over-specifying the implementation A useful prompt describes the user's situation and the sequence of decisions. For example: ‘A calm appointment app for independent therapists; show today's schedule, a client profile, rescheduling, and a confirmation state; use warm neutrals, clear hierarchy, large tap targets, and a reassuring tone.’ That brief constrains the product story while leaving room for the generator to propose a coherent visual system. Then review whether the proposed screens actually support the job. If a screen is visually attractive but does not move the user toward the outcome, revise the prompt or the screen. The goal is not to accept the first render; it is to make an early product conversation concrete enough for a team to improve. #### What does the AI mobile UI generator export? A ZIP with PNG screen renders plus HTML, React, and React Native code for development. You can chat-revise any screen on the canvas first. #### Is Mobile UI included in screenshot credit packs? Yes. The same credit packs power store listing screenshots and Mobile UI screens. One credit equals one generated UI screen. #### Do I start in Figma? No. Write a prompt, generate connected screens on the StoreShots canvas, then export code. Use Figma later only if your team still needs it. #### Does Mobile UI generate a complete production app? No. HTML, React, and React Native exports are implementation starting points. Engineering still needs to connect data, navigation, authentication, accessibility, platform behavior, and tests. #### Can I use Mobile UI before my app is built? Yes. A primary use is aligning on a connected flow and visual direction before engineering commits to the structure. Use real store screenshot workflows once product screens exist. #### What is one Mobile UI screen worth? One generated Mobile UI screen uses one credit. Starter is $10 for 50 credits and Studio is $18 for 100 credits; credits never expire and approved-work re-export is free. ### AI mascot generator with transparent GIF animations URL: https://storeshotsai.com/ai-mascot-generator Describe a brand character once, branch into outfit and pose variants, then export smooth transparent GIF loops for onboarding, empty states, and in-app delight — all from one mascot tree. - Base image: 1024×1024 PNG with transparent download - Animations: Smooth transparent GIF loops (wave, idle, celebrate, bounce, point) - Variants: Look, pose, and expression branches from any tree node - Credits: 1 credit base or variant · 2 credits GIF animation · same packs as screenshots - Export: Single files or full ZIP with manifest - **Transparent GIF loops** — Animations export as transparent GIFs ready for onboarding screens, loading states, and success moments inside your app. - **One character, many assets** — Variants and animations branch from the same parent image so colors, outfit, and style stay consistent across every asset. - **Tree-based workflow** — A visual layer tree shows root, variants, and GIF branches — select any node to preview, download, or keep building. - **Same credits as store listings** — 1 credit = base mascot or variant · 2 credits = transparent GIF animation. The same Starter and Studio packs power screenshots, Mobile UI, and mascots. ### Why apps use a mascot — and where it actually helps An app mascot gives a product a face people remember. Used well, it turns the quiet moments of an app — the first launch, an empty list, a long upload, a finished goal — into moments that feel guided instead of blank. Language-learning, fitness, budgeting, and kids' apps lean on characters for exactly this reason: a friendly figure makes repetition and waiting feel lighter. The hard part has never been the idea. It is producing a character that stays consistent across dozens of poses, expressions, and animations without hiring an illustrator and an animator for every new screen. StoreShots Mascot Studio is built around that consistency problem: every asset branches from the same parent image, so the character still looks like itself in its tenth variant. - Onboarding: a waving or pointing loop that introduces each step. - Empty states: an idle loop that softens “nothing here yet”. - Loading and progress: a short bounce while work happens in the background. - Success moments: a celebrate loop after a goal, purchase, or streak. - Store and marketing art: a still variant that matches your listing screenshots. ### How the mascot tree keeps one character consistent Mascot Studio starts with a root character: describe it in a short brief or upload a reference photo, then choose a style such as anime, chibi, kawaii, or a 3D render look. That root becomes the top of a visual tree. Select any node to branch a look, pose, or expression variant. Because each new image is generated from its parent, colors, proportions, and outfit details carry through. Animations branch the same way: pick a node and generate a wave, idle, celebrate, bounce, or point loop, or describe a custom motion. You can download single PNGs and GIFs or export the whole tree as a ZIP with a manifest for your developers. ### Transparent GIF loops vs. Lottie and video Transparent GIFs work almost everywhere — native iOS and Android image views, React Native, web pages, email, and design tools — with no runtime library. That makes them the fastest way to get character motion into an onboarding flow or an empty state. Vector formats such as Lottie can be smaller and scale perfectly, and they are a good fit if a motion designer will hand-tune timing later. A practical path many teams take: validate the character and the moments that need motion with GIF loops first, then decide whether any of them deserve a hand-built vector animation. - Keep loops short and seamless so they do not distract from the task on screen. - Reserve the most energetic motion (celebrate) for genuine wins. - Test each loop on light and dark backgrounds before shipping. - Respect reduced-motion settings: show a still variant when users ask for less motion. ### What a mascot set costs in credits Mascots use the same one-time credit packs as store screenshots and Mobile UI — there is no separate subscription. A base mascot or a variant uses 1 credit, and a transparent GIF animation uses 2 credits. For example, one base character, four expression or pose variants, and three animation loops comes to 1 + 4 + 6 = 11 credits, well inside the Starter pack ($10 for 50 credits). Credits never expire. See [pricing](/pricing) for current packs. Pair the character with the rest of your launch: generate [App Store screenshots](/app-store-screenshot-generator) and [Play Store screenshots](/play-store-screenshot-generator) from real app screens, or design new flows with the [AI mobile UI generator](/ai-mobile-ui-generator). For placement ideas, read the [mascot GIF onboarding guide](/blog/app-mascot-gif-onboarding-guide). #### What format are mascot animations exported in? StoreShots exports mascot animations as transparent GIF loops — ready to drop into mobile apps, marketing sites, and onboarding flows. #### Can I create variants from the same mascot? Yes. Select a node in the mascot tree and generate look, pose, or expression variants. New assets branch from that parent image. #### Do mascot credits use the same packs as screenshots? Yes. The same credit packs power mascots, store screenshots, and mobile UI. Base mascot and variants use 1 credit each. Transparent GIF animations use 2 credits. #### Can I start from a reference photo or sketch? Yes. Upload a reference image or describe the character in a short brief, then choose a style such as anime, chibi, kawaii, or a 3D render look. The generated base becomes the root of your mascot tree. #### What resolution is the base mascot? The base mascot is generated as a 1024×1024 PNG with a transparent download, which leaves room to scale it down for app icons, onboarding illustrations, and marketing art. #### Which animations can I generate? Built-in loops include wave, idle, celebrate, bounce, and point, and you can describe a custom motion. Each animation exports as a transparent GIF loop and uses 2 credits. #### Can I use the mascot in my App Store screenshots? Yes. Download a still variant as a transparent PNG and place it in your listing art, or pair it with StoreShots App Store and Play Store screenshot packs so the character and the store story feel like one brand. ## Frequently asked questions ### How does the AI App Store and Play Store screenshot generator work? StoreShots AI analyzes your uploaded in-app screenshots as one application, infers the product category and core flows, then generates one polished App Store or Play Store screenshot for each uploaded image — with ASO headlines, subtext, device frames, and the correct export dimensions. ### Which AI model powers StoreShots AI? StoreShots AI runs on Claude Opus 5.5, Anthropic's Claude model, for screenshot understanding, ASO copywriting, layout planning, quality checks, and Mobile UI code generation (HTML, React, and React Native). Background art, mascot images and the in-app photos inside Mobile UI screens come from dedicated image-generation models (Google Gemini image models or OpenAI GPT Image). Your uploaded screens stay the UI source — the model composes marketing around them and does not redraw your product. ### What App Store screenshot sizes can I export? Export portrait iPhone App Store screenshots at 1290×2796 px — an accepted size for Apple's largest iPhone screenshot category (iPhone with Dynamic Island, large display — the 6.9-inch slot); App Store Connect scales it down for smaller iPhones. Copy is editable before download. ### What Play Store screenshot sizes can I export? Export portrait Google Play phone screenshots at 1080×1920 px. Generate one cohesive Play Store screenshot set from the same app captures you use for iOS. ### How do credits work? 1 credit equals 1 generated App Store or Play Store screenshot slide, 1 Mobile UI screen, 1 mascot base PNG, or 1 mascot variant. GIF mascot animations use 2 credits. Wizard previews use 0.5 credit. Per-slide or per-screen chat revisions use 1 credit. Re-exporting an already generated set is free. ### Can I generate mobile app UI/UX, not just store screenshots? Yes. StoreShots AI includes a Mobile UI/UX studio. Describe the app, generate connected screens on a canvas, and export HTML, React, and React Native plus PNG renders in a ZIP. The same credit packs power listings and UI. ### Do credits expire? No. Credits never expire. Buy a credit pack when you need it and use them on store listing updates, Mobile UI screens, or mascot GIFs. ### Can I use one screenshot set for both the App Store and Play Store? Yes. Generate your screenshot pack once, then export at App Store 1290×2796 and Play Store 1080×1920 from the same approved slides. Chat-edit any single screenshot before export. ### Is there a bundle with TestMyApps closed testing? Yes. The Launch Stack bundle is $15 for 10 StoreShots AI screenshot credits and 1 TestMyApps testing credit. Message us on WhatsApp or email to opt in — credits are applied to both products after payment. ### Do you offer refunds? If the product is not a fit in the first 7 days, email support and we will help with the right resolution. ### What payment methods are supported? Credit pack purchases run through Dodo Payments — cards, UPI, and the local methods Dodo supports in your region. ### Is StoreShots AI the same as storeshots.org? No. StoreShots AI is the hosted ClyroLabs product at storeshotsai.com. storeshots.org is a separate, unrelated open-source project. Check the domain before relying on pricing, features, or support details. ### What is the $15 Launch Stack bundle? It includes 10 StoreShots AI screenshot credits and 1 TestMyApps testing credit for one launch pass. Opt in on WhatsApp or email — the team confirms payment and tops up both wallets. ### How much does one App Store or Play Store screenshot cost? One credit equals one final AI-generated store screenshot slide, one Mobile UI screen, one mascot base PNG, or one mascot variant. GIF mascot animations use 2 credits. The Starter pack is $10 for 50 credits and the Studio pack is $18 for 100 credits — one-time purchases with no subscription. ### Is there a free plan or free trial? No. StoreShots AI has no free tier or subscription: you buy a one-time credit pack (from $10 for 50 credits) and spend credits only on generated work. Re-exporting work you already generated is free. ### What do Mobile UI credits include? The same credit packs power Mobile UI/UX. Generated screens include a live canvas plus HTML, React, and React Native code you can export as a ZIP for development. ### How much do mascot GIFs cost? Mascot Studio uses the same credit wallet. Base mascot generation and variants each use 1 credit. Transparent GIF animations use 2 credits. Download PNGs and GIFs individually or export everything in one ZIP. ### Is re-export free? Yes. Re-exporting App Store or Play Store screenshots you already generated does not consume additional credits. ## Topic hubs ### App Store screenshot & ASO resource hub URL: https://storeshotsai.com/topics/app-store iPhone listing dimensions, benefit-led copy, slide order, localization, and export workflows for App Store Connect. Learn how to turn real product screens into a focused listing story. - **Start with store-ready dimensions** — App Store Connect's 6.9-inch iPhone slot accepts 1290×2796 portraits (alongside 1320×2868 and 1260×2736), so one 1290×2796 set covers most iOS listings. Correct sizing keeps type crisp next to competitor screenshots. - **Pair visuals with ASO copy** — Each slide should lead with a user benefit, not a feature list. StoreShots generates headlines from your real in-app screens. - **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. - **Keep UI truth visible** — Uploaded screens remain the product source. The surrounding art can add hierarchy and brand, but it should never promise a feature the shipped build does not contain. - **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 phone before uploading. - **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. - **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. - **A repeatable iOS workflow** — Collect production captures, define the audience and promise, generate the narrative, revise the weakest slide, and review the ZIP on a phone. Then record what changed so the next update can preserve the story while replacing only stale screens. - **Use the supporting guides** — Start with dimensions, move to screenshot copy and slide order, then read the conversion and localization guides before export. The App Store generator is for real product screens; Mobile UI is the better first step when the product is still a concept. - **Keep the listing truthful** — Screenshots are promises made at the moment of install. Remove beta labels, outdated navigation, and unsupported feature claims before export. If a screen needs a long explanation, improve the product story or choose a clearer capture rather than adding more copy around it. - **Use samples as a quality bar** — Review generated examples for hierarchy, legibility, device scale, and consistency across the set. Samples show the kind of output the workflow can create; they are not customer case studies or a guarantee that every app category needs the same composition. - **Pair the hub with the generator** — Read the 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. ### Google Play screenshot resource hub URL: https://storeshotsai.com/topics/play-store Phone screenshot sizes, feature graphics, listing order, localization, and what to ship after your Play Store visuals are ready. Keep 1080×1920 phone screenshots separate from the 1024×500 feature graphic. - **Phone screenshots first** — 1080×1920 phone PNGs are the core Play listing asset. Export App Store sizes from the same pack when you launch on both stores. - **Plan testing after creatives** — Listing screenshots and closed testing are different workstreams. When you need real testers, TestMyApps handles the 12-tester rule. - **Screenshots are not feature graphics** — Phone screenshots explain the app in the gallery at 1080×1920. A feature graphic is a separate wide 1024×500 asset; StoreShots currently generates the phone set, not that banner. - **Make slide one earn the scroll** — Use an outcome-focused headline and a legible production screen. Follow with the main action and differentiator, then add depth or trust only when each slide adds a new reason to install. - **Check the final Play upload** — Open every PNG, check text safe areas and current Google Play rules, and upload manually after review. StoreShots creates the files; it does not submit listings or run testing. - **Design for the phone carousel** — The first screenshot should make the product outcome clear without requiring a caption below the image. Follow with the action, differentiator, and proof. Keep each slide readable as a thumbnail and avoid putting key copy close to crop edges. - **Connect launch workstreams honestly** — Screenshot production and closed testing solve different problems. StoreShots creates listing assets; TestMyApps is a related ClyroLabs service for managed Google Play testing. Keep those calls to action and expectations separate in launch documentation. - **Localize after the first story works** — Translate the benefit, not only the literal headline. Longer strings may need a shorter variant, a different line break, or a separate capture when the app itself is localized. Review each locale at phone scale before uploading it to Play Console. - **Maintain a release checklist** — For each Android release, confirm the production build, screenshot order, 1080×1920 dimensions, file format, feature-graphic status, and policy requirements. Keep manual Play upload and any closed-testing service as separate checklist steps. - **Use one source of product truth** — The best Play packs begin with the current Android build and a short audience description. Keep screenshots, listing copy, and release notes aligned so a shopper sees the same promise before install that the app delivers after install. - **Document the final decision** — Keep the accepted headlines, source build, screenshot order, and upload date with the release record. A small record makes the next refresh faster and prevents old beta screens from returning to the live listing. ### Screenshot conversion & creative workflow hub URL: https://storeshotsai.com/topics/aso Benefit-led headlines, AI versus designer workflows, localization checklists, and listing experiments for clearer store conversion. Use this hub to turn product truth into a repeatable creative system. - **Creative that converts** — Slides one through three do most of the conversion work. Lead with outcomes, keep typography consistent, and localize only after the core story works. - **Ship faster with AI composition** — StoreShots composes marketing frames around your real UI — you keep the product truth while AI handles headlines and scene art. - **Give every slide one job** — A slide can lead with an outcome, explain a workflow, show a differentiator, provide authentic proof, or add final context. Avoid stacking unrelated claims around a tiny phone. - **Localize after the core story works** — Translate the promise and headline hierarchy deliberately. Expanded text may need rewriting, not smaller type. Validate each locale at thumbnail size and keep the UI language honest. - **Use AI drafts with human review** — AI can accelerate repeated production, but you still verify claims, contrast, store policy, and whether the visible UI proves the headline. Taste and product accuracy remain your responsibility. - **Measure the message before the wallpaper** — When testing variants, change one meaningful idea at a time: the first-slide promise, the visible workflow, or the proof point. Record which message was tested and avoid claiming a conversion lift unless the experiment and sample support it. - **Build a reusable creative system** — Keep a small library of accepted headline patterns, background rules, device treatments, and localization notes. A documented system makes future AI generations easier to review and keeps different releases recognizably part of the same product. - **Turn feedback into a better brief** — If a headline is vague, the input may be vague too. Write down the exact user, action, and result that the screen proves. That product language improves both AI drafts and human-designed variants without relying on inflated claims. ### App mascot & GIF animation resource hub URL: https://storeshotsai.com/topics/mascot Transparent mascot GIFs for onboarding, variant trees, style presets, and export workflows for in-app brand characters. Learn how to keep one character coherent across static and animated assets. - **One character, many assets** — Generate a root mascot, branch look and pose variants, then export smooth transparent GIF loops from the same tree. - **Built for in-app motion** — Use wave, idle, celebrate, and custom-motion GIFs on welcome screens, empty states, and success moments — not just static marketing art. - **Branch from one approved base** — Generate the root character first, then branch poses, expressions, and looks from the chosen parent. A tree-based workflow helps preserve palette, silhouette, and personality. - **Budget the wallet across studios** — One credit covers a mascot base or variant and two credits cover a GIF animation. The same never-expire packs can also cover store slides and Mobile UI screens. - **Review assets in their real context** — Check transparent edges, timing, file weight, and readability against your app background. Treat generated characters as product assets that still need implementation review. - **Map motion to a product moment** — Use idle loops for waiting, wave for welcome, celebrate for success, and a focused gesture for guidance. Motion should clarify state or personality without blocking content, distracting from a task, or increasing load time unnecessarily. - **Keep a handoff record** — Export the chosen base, variant tree, and GIF files with names that match the product states where they appear. Check transparency and licensing, then test on light and dark surfaces before the asset reaches production. - **Use motion with restraint** — A mascot loop should support a moment, not compete with the primary action. Check timing, file weight, reduced-motion expectations, and whether the animation remains understandable when the app is busy or the network is slow. - **Connect the mascot to the product voice** — Pick expressions and poses that match the brand's tone and the state being explained. A celebratory loop belongs after success; a confused pose belongs near recovery guidance. Treat the mascot as part of UX, not only as decoration. - **Design for transparency** — Transparent assets need testing against the surfaces where they will appear. Check the outline on light and dark backgrounds, inspect the edges at the intended size, and ensure the motion remains legible without a colored card behind it. - **Name and export assets for the team** — Use names that describe state and motion, such as onboarding-wave or empty-state-idle. Keep the accepted base, variant relationship, dimensions, and intended placement together so an engineer can integrate the asset without reopening the entire generation history. - **Plan the asset set before animation** — Decide which static PNGs and GIF loops the product actually needs before generating every possible variant. A small set of consistent states—welcome, idle, success, and recovery—is easier to integrate, test, and maintain than an unstructured tree of near-duplicates. - **Validate motion with the whole interface** — A mascot should fit the rhythm of the screen around it. Check whether it overlaps buttons, competes with announcements, or loops forever beside a task that needs focus. Test the static fallback too, because some surfaces and accessibility settings will not play the GIF. - **Plan the asset set before animation** — Decide which static PNGs and GIF loops the product actually needs before generating every possible variant. A small set of consistent states—welcome, idle, success, and recovery—is easier to integrate, test, and maintain than an unstructured tree of near-duplicates. ### AI mobile UI & handoff resource hub URL: https://storeshotsai.com/topics/mobile-ui Design connected app screens from a prompt, then export HTML, React, React Native, and PNG renders for dev handoff. Use the flow to align product, design, and engineering before wiring production data. - **Design before you have screenshots** — Describe the product flow and optional references. StoreShots generates a coherent multi-screen UI on a canvas you can refine. - **Export for development** — Leave with HTML, React, and React Native code plus PNG renders — one credit per screen, same packs as listing screenshots. - **Write a brief with a user job** — Name the audience, goal, tone, key flow, and important states. A specific brief gives the generator enough product truth to propose connected screens instead of unrelated mockups. - **Review the flow, not only the hero** — Check transitions, repeated components, hierarchy, contrast, and tap targets. Revise the weak screen locally and compare PNG renders with the exported code before handoff. - **Move from UI exploration to store assets** — Generated UI is an engineering starting point, not a complete production app. Once real screens exist, use the App Store or Play Store workflow to create listing PNGs at native sizes. - **Plan states before polishing pixels** — A connected flow needs more than a home screen. Name loading, empty, error, edit, success, and confirmation states when they matter. Reviewing those transitions early exposes product decisions before they become expensive implementation work. - **Compare code and renders** — PNG renders show visual intent; HTML, React, and React Native exports show a handoff structure. Compare them, rename components, connect real data, add navigation, audit accessibility, and test device behavior before treating the export as ready to ship. - **Make the prompt reviewable** — Keep a short record of the product brief, reference images, chosen screens, and revisions. This gives designers and engineers a common reason for the hierarchy and makes it easier to regenerate one weak screen without losing the whole flow. - **Know when to switch workflows** — Mobile UI is for exploring structure before implementation. Once screens are real, store screenshot workflows create listing assets at native dimensions. The same credit wallet supports both, but the deliverables and review criteria are different. - **Make handoff conversations concrete** — A screen sequence gives product and engineering something specific to discuss: which state exists, what data it needs, how navigation should work, and where accessibility matters. Treat the exported UI as a shared artifact that accelerates decisions, then let engineering reshape it for the real architecture. - **Keep visual and technical review separate** — A polished render can still hide missing loading, error, permission, or offline states. Review visual hierarchy with the team, then review code structure, platform behavior, asset licensing, and tests. Both passes are required before a generated flow is ready for production work. - **Make handoff conversations concrete** — A screen sequence gives product and engineering something specific to discuss: which state exists, what data it needs, how navigation should work, and where accessibility matters. Treat the exported UI as a shared artifact that accelerates decisions, then let engineering reshape it for the real architecture. - **Keep visual and technical review separate** — A polished render can still hide missing loading, error, permission, or offline states. Review visual hierarchy with the team, then review code structure, platform behavior, asset licensing, and tests. Both passes are required before a generated flow is ready for production work. ## Guides ### App Store Screenshots That Increase Downloads in 2026: The Complete Guide URL: https://storeshotsai.com/blog/app-store-screenshots-increase-downloads-2026 · Updated: 2026-11-19 · Author: StoreShots AI Editorial Learn how high-converting App Store screenshots improve install rates in 2026 — first-slide strategy, benefit-driven copy, visual storytelling, and export-ready ASO workflows. When someone discovers your app in the App Store or Google Play, they decide in seconds — not minutes. Most visitors never read your full description, scroll through every review, or compare feature lists line by line. They scan the icon, glance at the rating, and swipe through your screenshot carousel. That carousel is your storefront window, and in 2026 it carries more conversion weight than ever as organic discovery gets noisier and paid acquisition costs climb. Developers routinely spend months shipping product and only an afternoon on listing visuals. The result is predictable: flat conversion rates, high bounce from search impressions, and wasted spend on traffic that never installs. Strong ASO screenshots explain value immediately, show real product proof, and build enough trust for a tap on Get. Weak ones send users to the next competitor before they understand what you built. This guide walks through the psychology, structure, copy, and production workflow behind App Store screenshots that actually increase downloads — including how an [app store screenshot generator](/app-store-screenshot-generator) like [StoreShots AI](/) compresses a multi-hour design process into minutes without sacrificing store-ready export quality. ### Why screenshots matter more than your feature list Think about your own behavior the last time you searched for an app. You probably opened three or four listings, skimmed the first screenshot of each, and installed the one that communicated an outcome you recognized. Apple and Google surface screenshots in search results, product page headers, and editorial placements — they are not decorative assets filed away after launch. Effective ASO screenshots do five jobs at once: they explain the core benefit, demonstrate that the app is real and maintained, differentiate you from template competitors, reduce anxiety about install size or complexity, and create enough emotional resonance that tapping Install feels obvious. Miss any one of those on slide one and you lose the visitor before slide two loads. Conversion data from ASO practitioners consistently shows that listing creative refreshes produce measurable install lifts when messaging aligns with user intent. Screenshots are the highest-leverage creative you control without changing your binary. ### The first screenshot is your hero — treat it like a billboard The first App Store screenshot appears largest in search and sets the narrative for every slide that follows. The most common mistake is opening with a generic dashboard, a settings screen, or a logo splash that tells the user nothing about why they should care. Your hero slide must answer one question in under three seconds: why should I install this app? For a fitness tracker, lead with "Track workouts and hit goals faster" above the screen where a user logs a completed session. For personal finance, "See where every dollar goes" above a clean spending breakdown. For language learning, "Learn Spanish in ten minutes a day" above a lesson in progress. The headline is the promise; the UI beneath is the proof. Keep the app name on slide one only. Repeating your brand on every frame wastes precious headline space and trains users to ignore your copy. Let the product speak through consistent visual language instead. ### Benefits beat features every time Internal feature names do not convert browsers into installers. "Task Management Module" describes your org chart; "Finish projects on time" describes the user's life getting easier. Every slide should translate a capability into an outcome the visitor already wants. Run this quick audit on your current set: read each headline aloud and ask whether a stranger would know what improves in their day. If the answer is no, rewrite before you touch gradients or device frames. AI copy suggestions from an [AI app screenshot maker](/) can accelerate drafting, but you still own the benefit hierarchy — machines suggest, you decide what matters most. Pair each benefit headline with UI that visibly delivers it. If the copy says "Split bills in one tap," show the tap target or completed split — not an unrelated profile page. Misalignment between words and pixels erodes trust faster than ugly colors. - Feature: AI suggestions → Benefit: "Get smarter recommendations instantly" - Feature: Analytics dashboard → Benefit: "Understand your growth at a glance" - Feature: Offline mode → Benefit: "Keep working without signal" - Feature: Widgets → Benefit: "See what matters from your Home Screen" ### Keep headline copy short and scannable Users scroll the carousel quickly, often on a small phone in bright sunlight. Headlines should land in roughly three to seven words; supporting subtext can stretch to eight or fifteen if contrast and size hierarchy stay readable at thumbnail scale. Compare these two approaches. Weak: "Our advanced productivity platform helps teams collaborate through a unified task management environment with real-time sync." Strong: "Collaborate with your team" with subtext "Assign tasks and finish projects faster." The second version survives cropping in App Store search results; the first becomes illegible noise. Write copy for the smallest surface your screenshot will appear on, not the full-resolution export. If it works as a thumbnail, it works everywhere else. [Create screenshots with StoreShots AI](https://storeshotsai.com/login?next=%2Fdashboard) ### Build a visual story across five to seven slides Apple allows up to ten iPhone screenshots per localization. High-converting indie and mid-size apps typically ship five to seven slides: enough arc to tell a story without exhausting scroll depth. Think of the sequence as a sales presentation, not a feature dump. A proven narrative order: (1) hero outcome, (2) primary workflow, (3) differentiator competitors hide, (4) depth or secondary persona use case, (5) trust signal, (6) optional social proof with verifiable numbers, (7) soft call to action about what happens right after install. You do not need all seven if a slide would repeat the same message. For deeper slide-order tactics, see our companion piece on [App Store screenshot order that converts](/blog/app-store-screenshot-order-that-converts). The order matters as much as individual frame polish. 1. Slide 1 — Hero outcome tied to daily-use UI 2. Slide 2 — Core workflow that delivers the outcome 3. Slide 3 — Differentiator presented as a headline, not a settings label 4. Slide 4 — Secondary module, integration, or persona-specific scenario 5. Slide 5 — Trust: ratings snippet, user count, security cue if authentic 6. Slide 6 — Social proof or comparison frame with real numbers only 7. Slide 7 — Soft CTA: free trial, no account required, instant value ### Consistency signals quality — chaos signals neglect Random background colors per slide, mixed typography, and inconsistent spacing make even a great app look like a weekend project. Premium listings share a visual system: one palette derived from your icon, one headline font weight, one spacing rhythm, one device frame style across the entire set. Consistency also speeds production. When you define backgrounds, type scale, and frame treatment once, updating screenshots after a release means swapping UI captures — not redesigning from scratch. That is exactly where template-driven [ASO screenshots](/) earn their keep for teams that ship often. Pull accent colors from your app icon so store visitors connect the listing to the home screen icon they will tap after install. Subtle repetition builds recognition without shouting your logo on every frame. ### Device frames: polish without hiding the product Device frames add realism, create structure around messy full-bleed UI, and help users instantly recognize that they are looking at a phone app — not a web dashboard screenshot accidentally uploaded. Used well, frames improve hierarchy by constraining the canvas. Avoid oversized bezels that shrink your actual interface into a postage stamp. The UI should remain the focal point; the frame is scaffolding. Match frame style to your brand tone: minimal chrome for productivity tools, bolder hardware cues for creative apps if that fits your category norms. [StoreShots AI](/) applies consistent device frames during generation so you do not manually align masks in Figma for every release. ### Export at the correct App Store screenshot size Incorrect dimensions cause rejected uploads, blurry upscales, or awkward letterboxing that breaks your carefully tuned layout. For Apple's 6.9-inch iPhone slot — the size class most teams standardize on in 2026, which App Store Connect scales down for smaller iPhones — export portrait screenshots at 1290 × 2796 pixels. Google Play phone screenshots use 1080 × 1920 portrait. If you ship on both stores, maintain one creative direction but export separate size classes rather than stretching a single PNG. Stretching destroys text legibility and makes your listing look amateurish next to competitors who export natively. StoreShots exports App Store at 1290×2796 and Play Store at 1080×1920 from the same project. See [how it works](/how-it-works) for the capture-to-export flow and our [App Store screenshot size and templates guide](/blog/app-store-screenshot-size-aso-templates-guide-2026) for dimension deep-dives. ### Localize screenshots — not just metadata Translating your title and description while leaving English screenshots is a common ASO gap. Users in non-English markets trust listings that speak their language end to end. Localized headlines alone can lift conversion in priority locales without changing your product binary. Localize marketing overlays you control: slide headlines, subtext, and callouts. When your app supports locale-specific UI, capture builds in those languages for authenticity. German strings run long; plan shorter headline variants or looser text boxes so layout does not break. Regenerate localized sets rather than pasting translated text in Photoshop — manual overlays shatter the moment you add a second language or update UI. Tools that regenerate copy per locale while locking layout save days on multilingual launches. [Create screenshots with StoreShots AI](https://storeshotsai.com/login?next=%2Fdashboard) ### Common screenshot mistakes that kill conversion Tiny unreadable text is the fastest way to waste a search impression. If you squint at arm's length and cannot read the headline, neither will users scrolling in a subway. Raw captures without context force visitors to reverse-engineer your value prop. Menus, empty states, and onboarding permission dialogs almost never belong in marketing carousels unless the headline explicitly sells that moment. Showing too many unrelated features on consecutive slides creates cognitive whiplash. Each slide should advance one clear idea. Poor contrast between text and background makes copy disappear on OLED screens turned to max brightness. Random slide ordering — proof before promise, or CTA before demonstration — confuses the narrative. Using competitor trademarks, unverifiable #1 claims, or income guarantees invites policy risk and refund churn. - Unreadable type at search thumbnail size - Headlines that do not match on-screen UI - English-only visuals in localized store listings - Upscaled low-resolution captures - Ten slides that repeat the same message - Logo splash as slide one with no user benefit ### Align screenshots with search intent and keywords ASO screenshots are not keyword stuffing canvases, but they should reflect the jobs users associate with your category. If you rank for "budget tracker," slide one should scream budgeting outcomes, not generic productivity. Match visual story to the queries and Apple Search Ads terms that already drive impressions. Your subtitle and keyword field still matter for indexation; screenshots matter for conversion after the impression. Together they compound: keywords bring visitors, screenshots close them. Refresh creative when you reposition or when competitor listings in your category raise the visual bar. Stale screenshots that show UI you redesigned two versions ago signal abandonment. ### Speed up production without cutting corners Traditional screenshot workflows chain disconnected tools: capture on device, import to Figma or Photoshop, write copy in a doc, add frames, resize for each store, export PNGs, upload to App Store Connect, repeat after every UI change. That path easily consumes half a day per release for solo developers and multiplies across locales. Modern [app store screenshot generator](/app-store-screenshot-generator) workflows collapse those steps. Upload raw captures, describe your app or audience, generate ASO headlines and styled layouts, chat-edit individual slides when UI shifts, and export store-sized PNGs in one session. Teams report going from hours to minutes for routine refresh cycles. Speed matters because screenshots are not one-and-done. Every meaningful UI update, pricing change, or seasonal campaign deserves creative that matches reality. If production is slow, teams skip updates — and conversion drifts down while the product improves. ### Measure, iterate, and run store experiments Apple Product Page Optimization and Google Play Store Listing Experiments let eligible accounts test alternate screenshot sets against baselines. Export variants at identical dimensions so tests isolate messaging, not aspect ratio noise. Watch install rate — installs divided by product page views — not vanity impressions alone. A beautiful set that attracts wrong-fit users increases uninstalls; a clear set may slightly reduce page views while lifting qualified installs. Pair screenshot tests with review sentiment and support tickets. If users say "I thought the app did X" and your hero slide implied X, fix copy before running another paid burst. ### Pre-flight checklist before you submit Before uploading to App Store Connect, confirm every slide at 1290 × 2796, PNG when gradients or type overlays are present, headlines aligned with visible UI, no policy-risk claims, and localized sets for priority markets. Organize filenames by locale and slide index so uploads stay sane. Our [store screenshot checklist](/blog/store-screenshot-checklist-before-submit) covers technical and policy gates in detail. Run it on every release, especially when reusing an old creative set after a major redesign. [Create screenshots with StoreShots AI](https://storeshotsai.com/login?next=%2Fdashboard) ### Putting it together: your 2026 screenshot playbook Great App Store screenshots are not art projects detached from metrics. They are compressed sales arguments: promise, proof, differentiation, trust, action. Lead with outcomes, keep copy brutally short, maintain visual consistency, export at 1290 × 2796 for Apple's 6.9-inch iPhone slot, localize for real markets, and refresh when the product moves. You already built something worth installing. Give it a storefront that communicates value as clearly as your onboarding flow — because most users will never see onboarding if the listing fails first. Ready to ship your next set? Start a project in [StoreShots AI](/), explore [pricing](/pricing) if you need higher export volume, and cross-reference [how to write App Store screenshot copy](/blog/how-to-write-app-store-screenshot-copy) for headline formulas that pair with this structure. #### How many App Store screenshots should I use in 2026? Five to seven strong slides outperform ten weak ones. Lead with your hero outcome, prove the core workflow, add differentiation and trust, then close with a soft CTA. Only fill all ten slots if each frame advances a distinct message. #### What App Store screenshot size should I export for iPhone? Export portrait iPhone screenshots at 1290 × 2796 pixels — an accepted size for Apple's largest iPhone screenshot category (iPhone with Dynamic Island, large display — the 6.9-inch slot); App Store Connect scales it down for smaller iPhones. StoreShots AI exports at this dimension by default so uploads pass technical validation without manual resizing. #### Do App Store screenshots really increase downloads? Yes, when they communicate clear benefits and match user intent. Listing creative is one of the few ASO levers you control without shipping a new binary. Teams that refresh screenshots with stronger outcome-driven messaging routinely see measurable install-rate lifts in store analytics and A/B tests. #### Should I show pricing on my first screenshot? Usually no. Slide one should sell the core outcome. Mention free tiers, trials, or pricing on a later slide or in the subtitle field — not at the expense of your hero promise. #### Can I use the same screenshots for Google Play? Reuse the same creative direction and copy arc, but export Play Store phone screenshots at 1080 × 1920 — not stretched from iOS assets. One project in StoreShots can export both size classes. #### How often should I update App Store screenshots? Refresh when UI, core value proposition, or brand identity changes materially — typically major releases or repositioning, not every patch. Stale UI in screenshots hurts trust even when the live app improved. #### Is an AI app screenshot maker good enough for production listings? For most indie and startup launches, yes — especially when you need speed, consistent frames, and store-ready exports. Enterprise teams with bespoke illustration needs may blend AI-generated bases with designer polish. See our [AI vs designers comparison](/blog/ai-app-screenshot-generator-vs-designers) for a full breakdown. Sources: - [Screenshot specifications](https://developer.apple.com/help/app-store-connect/reference/screenshot-specifications) — Apple App Store Connect Help - [App Store product page](https://developer.apple.com/app-store/product-page/) — Apple Developer ### Google Play Screenshot Size & Requirements 2026 (1080×1920) URL: https://storeshotsai.com/blog/play-store-screenshot-generator-complete-guide-2026 · Updated: 2026-11-19 · Author: StoreShots AI Editorial Google Play screenshot size and requirements for 2026: 9:16 1080×1920 phone sets, the 2.3:1 ratio limit, file rules, counts, feature graphics and ASO copy. Google Play is the world's largest app distribution surface — and its listing format differs materially from Apple's. Phone screenshots, a wide feature graphic, optional promo video, and short description all compete for attention on devices that vary wildly in screen size. Getting Play Store creative wrong does not just look unprofessional; it costs installs when users bounce to the next search result. A proper [play store screenshot generator](/play-store-screenshot-generator) workflow handles more than slapping text on captures. You need correct 1080 × 1920 portrait exports, a cohesive story across up to eight phone slides, a 1024 × 500 feature graphic that anchors the store page, and ASO copy that matches what users typed into search. This complete 2026 guide covers sizing, templates, messaging split between assets, localization, common rejection reasons, and how [StoreShots AI](/) generates [Google Play screenshot templates](/play-store-screenshot-generator) and export-ready PNGs alongside iOS sizes from one project. ### How Google Play uses screenshots in 2026 Play Store search and browse surfaces show your icon, title, rating, and often your first phone screenshot at thumbnail scale. On the full listing, a feature graphic may span the header while the screenshot carousel sits below — each asset plays a distinct role. Phone screenshots carry the detailed proof: outcomes, workflows, differentiation, trust. The feature graphic is a wide poster — brand mark plus one visual hook, not a six-line paragraph crammed into 1024 × 500 pixels. Teams that duplicate the same message in both places waste pixels. Teams that align the feature graphic promise with slide-one headline create continuity that reduces bounce. ### Play Store phone screenshot size: 1080 × 1920 Google Play's rules for phone screenshots: JPEG or 24-bit PNG with no alpha, up to 8 MB each, each side between 320 and 3,840 pixels, and the long side no more than 2.3 times the short side. You need 2–8 phone screenshots, and at least two across device types to publish. To be eligible for Play's recommendation surfaces, Google asks apps for at least four screenshots at 1080 px or more: 9:16 portrait (minimum 1080 × 1920) or 16:9 landscape (minimum 1920 × 1080). That is why most consumer apps standardize on portrait 1080 × 1920. Do not upscale small captures. Start from simulator or device screenshots at native resolution, then compose marketing layouts on a 1080 × 1920 canvas. Upscaling blurs UI and text — users notice immediately next to sharp competitors. The [StoreShots AI Play Store screenshot generator](/play-store-screenshot-generator) exports Play phone sets at 1080×1920 by default, parallel to App Store 1290×2796 exports from the same captures. See [how it works](/how-it-works) for the dual-export flow. - Portrait phone: 1080 × 1920 px (most common for consumer apps) - Up to eight phone screenshots per listing - Minimum two screenshots required for publication - PNG preferred when gradients or text overlays are present - JPEG acceptable for photo-heavy slides without sharp type edges ### Feature graphic requirements (1024 × 500) The feature graphic is a wide banner displayed prominently on your Play Store listing and in some promotional contexts. Required dimensions are 1024 × 500 pixels, PNG or JPEG, with no excessive text — Google may reject graphics that read like ad banners rather than brand visuals. Treat it as a movie poster: icon or wordmark, one visual metaphor, brand colors pulled from your app icon. Avoid critical detail near edges; safe margins help on varied crop contexts. Screenshots do the explanatory work; the feature graphic sets mood and recognition. If your slide-one headline promises "Budget in five minutes," the feature graphic should feel like the same product — not a unrelated stock photo. ### First screenshot strategy for Play Store search Your first phone screenshot appears largest in many Play surfaces. It must answer why install — same rule as iOS, different canvas. Lead with an outcome headline above UI showing the happy path, not a settings menu or splash screen. Android users often compare more listings per session; clarity beats cleverness. Short headlines, high contrast, real product UI. Category-specific proof helps: finance apps show numbers, fitness apps show progress, games show gameplay. Cross-read our [App Store conversion guide](/blog/app-store-screenshots-increase-downloads-2026) for narrative structure — the story arc transfers even when pixel dimensions differ. [Create screenshots with StoreShots AI](https://storeshotsai.com/login?next=%2Fdashboard) ### Building a Play Store screenshot sequence Google allows up to eight phone screenshots. Strong sets use five to seven with distinct messages. Structure mirrors iOS best practice: hero outcome, core workflow, differentiator, depth, trust, optional social proof, soft CTA. Android listings sometimes emphasize integrations (Google Sign-In, Wear OS, widgets) that iOS slides omit — use slide four or five for platform-specific value when it matters to your audience. Avoid portrait sets that are literally iOS frames dropped onto Play — use Android-appropriate device frames when your tool supports them so users see familiar hardware cues. 1. Slide 1 — Hero outcome with primary UI proof 2. Slide 2 — Core action that delivers the outcome 3. Slide 3 — Differentiator vs category alternatives 4. Slide 4 — Integrations, widgets, or Wear/TV if relevant 5. Slide 5 — Trust: ratings, security, editorial badges if authentic 6. Slide 6 — Social proof with verifiable metrics only 7. Slide 7 — Soft CTA: free, offline, no account, etc. 8. Slide 8 — Optional seasonal or promo frame if distinct ### Google Play screenshot templates that scale Templates are not laziness — they are consistency engines. A [Google Play screenshot template](/play-store-screenshot-generator) system defines background gradients, headline placement, device frame style, and spacing so every release updates UI captures without redesigning from zero. Good templates encode ASO lessons: headline safe zones that survive thumbnail crop, contrast ratios that work on OLED, margin rules that keep text off rounded device corners. Bad templates are generic Canva layouts with no store-size export discipline. StoreShots applies template logic during AI generation — you supply captures and positioning; the tool maintains structure across slides and locales. That is the difference between a template as PNG overlay and a template as production pipeline. ### ASO copy for Play Store screenshots Play Store short description and screenshot headlines should reinforce the same keywords users search — without keyword stuffing. If you target "habit tracker," slide one should visualise habit outcomes, not generic "productivity reimagined." [ASO screenshots](/) bridge discovery and conversion: keywords bring impressions from Google Play search; headlines close the install. Write for humans first, algorithms second. Keep headline length disciplined — roughly four to seven words per slide. Subtext can expand slightly if hierarchy stays clear. Read [how to write App Store screenshot copy](/blog/how-to-write-app-store-screenshot-copy); Play Store rules overlap heavily. ### Play Store vs App Store: what to reuse Reuse narrative order, benefit hierarchy, and brand colors across stores. Do not reuse the same PNG without re-exporting dimensions — 1290 × 2796 iOS assets stretched to 1080 × 1920 destroy type clarity. One project in an [AI app screenshot maker](/) should export both size classes from the same creative direction. Feature graphics are Play-only; Apple uses different header assets. See [Play Store vs App Store strategy](/blog/play-store-feature-graphic-and-screenshots) for asset split detail and [AI vs designers](/blog/ai-app-screenshot-generator-vs-designers) if you are choosing production workflow. - Reuse: story arc, headlines (with length tweaks), palette, capture selection - Re-export: never stretch; generate native 1080×1920 and 1290×2796 - Play-only: 1024×500 feature graphic - iOS-only: separate iPad classes if you support tablets ### Localization on Google Play Google Play Console supports per-locale listings. Translating description but not screenshots sends mixed trust signals. Regenerate headline copy per language while locking layout — German expansions break naive text boxes. When your app UI localizes, capture locale-specific builds for authenticity. Marketing overlays must match the language of the store listing user is viewing. Our [localization guide](/blog/localize-app-store-screenshots) covers multilingual workflows for both stores; the Play-specific upload paths differ but creative principles align. [Create screenshots with StoreShots AI](https://storeshotsai.com/login?next=%2Fdashboard) ### Using a play store screenshot generator end to end Step one: capture clean Android UI — emulator or device, light and dark if you market both, real data not embarrassing placeholders. Step two: upload to [StoreShots AI](/) and describe audience plus primary outcome. Step three: generate the carousel, reorder slides to match the sequence above, chat-edit any headline that misstates features. Step four: export 1080 × 1920 PNGs organized by slide index. Step five: upload to Play Console custom store listing, verify preview on phone and tablet contexts. Step six: after UI changes, replace only affected slides — do not re-pay production tax for unchanged frames. Check [pricing](/pricing) for credit models that fit your ship cadence. 1. Capture high-resolution Android screens 2. Upload and describe app value prop 3. Generate styled slides with ASO copy 4. Edit individual frames via chat 5. Export 1080×1920 PNG set 6. Upload to Play Console with feature graphic 7. Refresh slides when UI or messaging shifts ### Common Play Store screenshot mistakes Wrong aspect ratio or upscaled blurry UI is the top technical failure. Feature graphics packed with tiny text trigger rejections or poor crops. iOS device frames on Android listings confuse users expecting Pixel or Samsung cues. Showing permissions dialogs, empty states, or login walls without narrative context wastes slides. Unverifiable "#1 app" claims create policy risk. Mismatch between screenshot promise and in-app reality drives one-star reviews. - 1080×1920 ignored — stretched from iOS assets - Feature graphic used as a second screenshot with unreadable type - More than eight slides planned (Play max is eight phone) - No feature graphic when competitors all ship polished banners - Stale UI after major Material redesign ### Category-specific Play Store screenshot tactics Games should show gameplay by slide two — not logo splash or menu trees. Finance apps need legible numbers and trust cues early. Health and fitness categories benefit from outcome metrics users recognize (steps, calories, streaks) rather than abstract wellness language. Productivity apps face the noisiest competition; differentiation must appear on slide three or earlier. Utilities with narrow jobs — QR scanners, unit converters — should state the job in slide one with zero jargon. Match [Google Play screenshot templates](/play-store-screenshot-generator) to category norms without cloning competitors pixel-for-pixel. Users notice sameness; they reward clarity. ### Working with Play Console custom store listings Custom store listings let you target specific countries or campaigns with alternate screenshot sets while keeping a default global listing. Use them for localized seasonal campaigns — back-to-school, Ramadan, regional sports events — without overwriting your master creative worldwide. Each custom listing still demands correct 1080 × 1920 phone assets. Maintain a naming convention: default_slide3.png versus campaign_de_slide3.png. Chaos in Google Drive slows uploads and invites wrong-frame mistakes. When experiments end, promote winning variants to default and archive losers with notes on why they underperformed — institutional memory beats guessing next quarter. ### Promo video, tablets, and other asset classes Optional promo video can boost engagement when it shows real product motion in under thirty seconds — but weak video hurts more than no video. Many teams prioritize screenshot quality first, add video when production capacity allows. Tablet, Chromebook, Wear, and TV screenshots have separate size classes if you target those form factors. Consumer phone-first apps can defer tablet sets until tablet usage justifies the effort. Closed testing and production access for personal developer accounts may run parallel to creative work — polish listings while testers opt in on separate tracks. ### Testing and optimization on Google Play Store Listing Experiments on eligible accounts test alternate screenshot sets against control. Export variants at identical 1080 × 1920 so experiments isolate messaging. Monitor install conversion rate, not just impression volume. Seasonal refreshes — back to school, new year fitness, holiday shopping — can lift relevance when timed with category demand spikes. Keep a template system so seasonal swaps take hours, not weeks. ### Timing screenshot updates with release trains Screenshot refreshes should land in the same release train as the UI they depict — not a week later when users already post confused reviews. Build screenshot generation into your release checklist alongside metadata, privacy labels, and what's new text. For staged rollouts, prepare screenshots before phased release begins so the listing matches day-one experience for early adopters. If a feature flag hides UI from most users, do not market it in screenshots until it is broadly available. Parallel Android and iOS releases benefit from one creative session: generate both 1080×1920 and 1290×2796 exports, then upload to each console the same day to avoid cross-platform trust gaps. ### Pre-submit checklist for Play Console Confirm two to eight phone screenshots at 1080 × 1920, feature graphic at 1024 × 500 if used, headlines match visible UI, no policy-violating claims, localized assets for priority languages, filenames organized for upload sanity. Run the full [store screenshot checklist](/blog/store-screenshot-checklist-before-submit) — it covers Play and App Store gates. Preview listing on multiple Android devices if possible before hitting publish. [Create screenshots with StoreShots AI](https://storeshotsai.com/login?next=%2Fdashboard) ### Your Play Store creative playbook for 2026 Winning Google Play listings combine technically correct 1080 × 1920 phone screenshots, a restrained 1024 × 500 feature graphic, benefit-led ASO copy, and a narrative sequence that proves your app delivers. Templates and [play store screenshot generator](/play-store-screenshot-generator) tooling exist so you refresh that story every release — not once a year when someone finds time for Figma. Android competition is dense. Clarity, consistency, and speed of iteration separate listings that convert from listings that merely exist. Start your next Play Store project in [StoreShots AI](/), export native sizes, and align with our [App Store screenshot size guide](/blog/app-store-screenshot-size-aso-templates-guide-2026) if you ship both platforms. #### What size are Google Play phone screenshots in 2026? Portrait phone screenshots should be 1080 × 1920 pixels. This is the standard most consumer apps use. StoreShots AI exports Play Store sets at this dimension automatically. #### How many screenshots can I upload to Google Play? Up to eight phone screenshots per listing; minimum two required. Use five to seven strong slides rather than filling eight with redundant messages. #### What is a Play Store feature graphic? A 1024 × 500 px banner displayed on your store listing. It should show brand identity and one visual hook with minimal text — not replace phone screenshots for feature explanation. #### Can I use iOS screenshots on Google Play? Reuse creative direction and copy, but re-export at 1080×1920. Never stretch 1290×2796 iOS PNGs — text and UI blur. Use Android-appropriate device frames when possible. #### Does StoreShots AI generate Play Store and App Store sizes? Yes. Export Play Store at 1080×1920 and App Store at 1290×2796 from one project with the same captures and headline structure. #### Should I localize Play Store screenshots? Yes for priority markets. Localized headlines improve trust and conversion. Regenerate per locale rather than overlaying translated text manually on fixed layouts. #### PNG or JPEG for Play Store screenshots? PNG when you use gradients, transparency, or sharp text overlays. JPEG can work for photo-dominant slides without small type. #### How do Google Play screenshot templates help? Templates lock layout, spacing, and export dimensions so you swap UI captures after each release without redesigning. AI generators apply template discipline during creation and re-export. Sources: - [Add preview assets: screenshots and graphics](https://support.google.com/googleplay/android-developer/answer/9866151?hl=en) — Google Play Console Help - [Store listing experiments](https://support.google.com/googleplay/android-developer/answer/9793453?hl=en) — Google Play Console Help ### App Store Screenshot Sizes 2026: Every iPhone & iPad Dimension URL: https://storeshotsai.com/blog/app-store-screenshot-size-aso-templates-guide-2026 · Updated: 2026-11-19 · Author: StoreShots AI Editorial Every App Store screenshot size Apple accepts in 2026 — iPhone 6.9-inch (1320×2868, 1290×2796, 1260×2736), older iPhones and iPad 13-inch — plus which one to export. Upload the wrong PNG to App Store Connect and you lose an afternoon to rejection emails, blurry upscales, or awkward letterboxing that breaks every headline you tuned. Screenshot size is not a footnote in ASO — it is a technical gate that determines whether your creative ever reaches a user intact. Short answer: for iPhone, export portrait screenshots at one of the sizes Apple accepts for its largest category — iPhone with Dynamic Island (large display), the 6.9-inch slot: 1320 × 2868, 1290 × 2796 or 1260 × 2736 pixels. Apple asks you to provide the highest required resolution and App Store Connect scales it down for smaller iPhones. If your app runs on iPad, Apple also requires at least one 13-inch iPad screenshot (2064 × 2752 or 2048 × 2732 portrait). This guide lists every size Apple accepts as of November 2026, explains which set to export first, how template systems keep layout and safe zones consistent across releases and locales, and how to keep Google Play (1080 × 1920) in parity. An [App Store screenshot generator](/app-store-screenshot-generator) like StoreShots AI encodes the export size so you focus on the message, not pixel math. ### Why App Store screenshot size still trips up teams Apple groups iPhone screenshots into display categories — iPhone with Dynamic Island (large and medium display), iPhone with Face ID (large and medium display), and older Home Button models — and accepts only specific pixel sizes in each. App Store Connect checks exact pixels, so a file one pixel off is rejected, and teams that upload a smaller class and rely on scaling wonder why text looks soft in search results. Soft screenshots signal low quality next to crisp competitor listings. Users cannot articulate "that PNG was upscaled" — they just bounce. Correct size is table stakes before copy or color psychology enter the conversation. Modern workflows bake size into export presets. Manual designers must discipline themselves; AI generators should fail impossible exports rather than silently blur. ### Which iPhone size to export: the 6.9-inch slot Apple's largest iPhone category, iPhone with Dynamic Island (large display), accepts three portrait sizes: 1320 × 2868, 1290 × 2796 and 1260 × 2736 pixels. Apple's guidance is to provide screenshots for the highest required resolution; App Store Connect then scales them down for smaller device sizes when your UI is consistent across them. That is why most iPhone-first apps maintain one master set in this slot and only add smaller sets when their layout genuinely differs on smaller phones. StoreShots AI exports App Store iPhone screenshots at 1290 × 2796. Requirements change, so confirm in [Apple's screenshot specifications](https://developer.apple.com/help/app-store-connect/reference/screenshot-specifications) before each release. Portrait orientation dominates consumer categories: finance, health, productivity, social. Landscape sets matter for games and video apps — this guide focuses on portrait sets because that is what most App Store listings use. - 6.9-inch slot (iPhone with Dynamic Island, large display): 1320 × 2868, 1290 × 2796 or 1260 × 2736 px portrait - Up to ten iPhone screenshots per localization - PNG recommended for gradients and sharp marketing type - RGB color space; avoid unintended alpha issues on flat fills - No upscaling from smaller simulator captures ### Every other iPhone and iPad size Apple accepts Smaller categories accept their own exact sizes, and each falls back to scaled screenshots from a neighbouring category when you do not provide them. Upload a smaller set only when your layout differs on those phones; a mismatched file in the wrong slot is the most common cause of the "dimensions of one or more screenshots are wrong" error. iPad is not optional for universal apps: if your app runs on iPad, Apple requires at least one 13-inch iPad screenshot. Phone-only apps do not need an iPad set. StoreShots AI does not generate iPad screenshots, so tablet sets must come from your own design tool. - iPhone with Dynamic Island (medium display): 1206 × 2622 or 1179 × 2556 px - iPhone with Face ID (large display): 1284 × 2778 or 1242 × 2688 px (the former 6.5-inch slot) - iPhone with Face ID (medium display): 1170 × 2532, 1125 × 2436 or 1080 × 2340 px - iPhone with Home Button (large display): 1242 × 2208 px; (medium display): 750 × 1334 px - iPad 13-inch: 2064 × 2752 or 2048 × 2732 px portrait (2752 × 2064 or 2732 × 2048 landscape) — required if the app runs on iPad - Sizes as listed in Apple's App Store Connect screenshot specifications, checked 19 November 2026 ### Play Store parity: 1080 × 1920 Dual-store apps should export Google Play phone screenshots natively — Google recommends 9:16 portrait at a minimum of 1080 × 1920 — rather than stretching 1290 × 2796 iOS files. Play accepts a long side up to 2.3 times the short side, but stretching between ratios destroys headline legibility and UI sharpness. Use one creative direction, two native exports. [StoreShots AI](/) handles App Store 1290×2796 and Play Store 1080×1920 from the same project. See our [Play Store complete guide](/blog/play-store-screenshot-generator-complete-guide-2026) for feature graphic and Android-specific rules. Template systems should parameterize canvas size so the same headline hierarchy reflows for each store without manual resize layers. [Create screenshots with StoreShots AI](https://storeshotsai.com/login?next=%2Fdashboard) ### What ASO templates actually are An ASO template is not a single PNG overlay — it is a reusable ruleset: background treatment, headline box dimensions, font scale, device frame style, margin grid, and export preset. Templates encode lessons from hundreds of listings so each release swaps UI captures without redesigning layout from scratch. Good [Google Play screenshot templates](/play-store-screenshot-generator) and App Store equivalents define safe zones where text survives search thumbnail crop. They specify contrast minimums for OLED displays and spacing that keeps type off rounded device corners. Bad templates are generic stock layouts with no export discipline — pretty in a design tool, wrong dimensions at upload time. ### Building a template system for your app Start from brand constraints: primary accent from your icon, neutral background that does not fight UI screenshots, one headline weight and one subtext weight. Define slide master layers — background, device frame, headline, subtext, optional badge. Document export presets named explicitly: APP_STORE_1290x2796 and PLAY_STORE_1080x1920. Filename convention: locale_slideIndex_store.png. Version templates in git or your design system repo when humans touch them; AI generators version implicitly through project history. Limit template variants. One master with seasonal accent swaps beats five unrelated styles that fracture brand recognition across the carousel. 1. Extract palette from app icon and primary UI 2. Define type scale readable at thumbnail size 3. Set device frame style and margin grid 4. Create slide masters for hero vs proof vs trust frames 5. Encode export presets for iOS and Android 6. Test thumbnail legibility in App Store Connect preview 7. Lock template; swap captures per release ### Template-driven vs one-off design One-off design makes sense for a major rebrand once every few years. Template-driven production makes sense for every other Tuesday when you fixed onboarding and need slide two updated before the App Store review completes. Indie developers without designers should default to AI-generated template baselines via an [AI app screenshot maker](/). Enterprise teams may maintain Figma libraries mirroring the same rules — different tools, same principle. The cost of skipping templates is delayed releases and stale listings. Users see new features in-app while store screenshots show last quarter's UI — trust erodes. ### Headline safe zones and thumbnail cropping App Store search results crop screenshot corners. Headlines placed flush to the top edge may lose characters. Templates should inset marketing copy within safe margins tested at smallest preview size. Keep headlines to roughly four to seven words. Subtext can run longer if size hierarchy keeps primary message readable. Run the arm's-length squint test on every template revision. Pair with copy guidance in [how to write App Store screenshot copy](/blog/how-to-write-app-store-screenshot-copy) — template geometry and wording work together. ### Localization without breaking layout German and Finnish strings expand; Thai line breaking differs from English. Templates need flexible text boxes or per-locale regeneration — not fixed-width overlays that truncate translations. Regenerate [ASO screenshots](/) per locale with locked visual system and translated headlines. Manual Photoshop layers shatter when you add a third language or update UI. Our [localization guide](/blog/localize-app-store-screenshots) walks upload paths in App Store Connect and Play Console; creative rules are identical across stores. [Create screenshots with StoreShots AI](https://storeshotsai.com/login?next=%2Fdashboard) ### Using an app store screenshot generator with templates Upload high-resolution captures to [StoreShots AI](/). Describe audience and outcome; the system applies template-like consistency — frames, backgrounds, headline placement — and exports at 1290×2796. Switch export target to Play Store for 1080×1920 without rebuilding slides. Chat-edit individual slides when UI changes: replace capture, tweak headline, re-export. Unchanged slides should not require manual rework. That is template workflow behavior even when you never open a design file. Read [how it works](/how-it-works) for capture tips — garbage inputs break even great templates. ### PNG vs JPEG for App Store uploads Apple accepts PNG and JPEG for screenshots. PNG preserves sharp text edges and gradients when marketing overlays sit above UI captures. JPEG can introduce compression artifacts on small type — avoid it when headlines are part of the image. File size limits are generous for screenshot counts; prefer quality over aggressive JPEG compression. Flat UI-heavy slides compress well as PNG; photo backgrounds may justify JPEG if type is minimal. ### Connecting templates to ASO keyword strategy Templates do not replace keyword research — they display the outcomes of that research visually. If you rank for "invoice scanner," template slide one should headline scanning outcomes above scanner UI, not generic "work smarter." Keywords index in title, subtitle, and keyword field; screenshots convert the impression. Align template copy with highest-intent terms without stuffing every slide with comma-separated keywords. Refresh template copy when ASO strategy shifts — new keyword clusters deserve new hero messaging, not just metadata edits. ### Quality control before App Store Connect upload Verify each PNG is exactly 1290 × 2796, RGB, readable at thumbnail, headlines truthful vs visible UI, no policy-risk claims, localized sets for priority territories, filenames organized by locale and index. Use Connect's preview on multiple device sizes. Compare against [store screenshot checklist](/blog/store-screenshot-checklist-before-submit) for cross-store gates. Keep a rollback folder of previous sets when testing radical template changes — store experiments need baselines to beat. - Pixel dimensions match spec — no off-by-two exports - No accidental transparency halos on backgrounds - Device frames consistent across slides - Captures reflect current shipping build - Localized sets match localized metadata language ### Simulator vs device captures for sharp exports iOS Simulator exports at 1x can look soft when blown to marketing layouts. Prefer device screenshots or simulator captures at the native resolution of your target class before compositing on a 1290 × 2796 canvas. Status bar time, battery, and carrier details should look realistic or be consistently clean — mismatched status bars across slides feel accidental. Some teams use marketing mode tools; others capture with a staged 9:41 time for Apple-esque polish. Dark mode and light mode: pick the theme that matches your template background. Mixing dark UI on light marketing backgrounds without intentional contrast planning creates muddy frames. ### iPad and Apple Watch assets — scope wisely iPad screenshots use their own dimensions (13-inch: 2064 × 2752 or 2048 × 2732 portrait). If your app runs on iPad, Apple requires at least one 13-inch iPad screenshot, so a universal app cannot skip them; the only way to defer iPad creative is to ship iPhone-only. If iPad is core — design tools, pro workflows — budget separate template masters. Apple Watch and Apple TV assets have their own classes; most apps skip until those surfaces drive meaningful installs. Phone-first template discipline keeps scope manageable for small teams. ### A/B testing template variants Apple Product Page Optimization tests alternate screenshot sets. Export variants at identical 1290 × 2796 so experiments isolate messaging or color — not aspect ratio. Change one variable per test: hero headline, background hue, or slide order. Winning variants become the new template default. Losing variants inform what not to repeat. Document results so the next designer or AI prompt inherits institutional knowledge. ### When to redesign templates vs swap captures Swap captures only when UI changes but brand and positioning stay stable — same template, new screens. Redesign templates when you rebrand, reposition, enter new category, or competitor listings leapfrog your visual quality bar. Major redesigns happen rarely; capture swaps happen often. Build process for the common case, not the once-a-year rebrand. [Create screenshots with StoreShots AI](https://storeshotsai.com/login?next=%2Fdashboard) ### Common size and template mistakes Exporting at 1242 × 2688 or other legacy sizes then upscaling to 1290 × 2796 creates blur. Using one iOS PNG stretched to Play Store 1080 × 1920 wrecks typography. Mixing portrait and landscape slides without category reason confuses carousel flow. Templates with trendy thin gray text fail accessibility and sunlight readability. Ten slides of identical layout with only headline swaps waste scroll depth — vary composition while keeping system consistency. ### Accessibility and readability in template design ASO templates must prioritize readable contrast — WCAG-minded contrast ratios help sunlight readability and reduce eye strain during quick store scans. Light gray marketing text on pastel backgrounds fails in real-world conditions even if it looks elegant in a design critique. Font sizes in templates should assume the smallest preview context, not the full-resolution export viewed on a monitor. Test on a physical phone at arm's length before approving a new template version. Accessibility also means honest representation: do not template-blur UI to hide unfinished features. Clear screenshots reduce support load and refund requests from misled installers. ### Maintaining template libraries across a team When multiple people touch listing creative, centralize the template source of truth — one Figma library, one StoreShots project, or one documented export folder in shared drive. Forking templates per teammate invites off-brand colors and inconsistent frame styles in the same carousel. Version templates semantically: template_v3_rebrand, not final_new_2. Changelog what changed — new headline font, adjusted safe zone, darker background — so future editors understand constraints. Quarterly template audits catch drift: are we still using last year's icon colors? Does slide five still reflect a feature we deprecated? Audits take an hour; stale listings cost installs all quarter. ### 2026 template checklist summary Standardize App Store iPhone exports on one 6.9-inch size such as 1290 × 2796 portrait, and add a 13-inch iPad set if your app runs on iPad. Pair with Play Store 1080 × 1920 from the same creative system. Build or generate templates that lock layout while allowing capture and copy swaps. Localize by regenerating headlines, not stretching English PNGs. Test thumbnails before submit. Correct size plus coherent templates plus benefit-led copy equals [ASO screenshots](/) that earn installs instead of embarrassing your product. Start a sized export in [StoreShots AI](/), review [pricing](/pricing), and read [App Store screenshots that increase downloads](/blog/app-store-screenshots-increase-downloads-2026) for narrative structure that fills your template frames. #### What is the App Store screenshot size for iPhone in 2026? Export portrait screenshots for Apple's largest iPhone category (iPhone with Dynamic Island, large display — the 6.9-inch slot) at 1320 × 2868, 1290 × 2796 or 1260 × 2736 pixels. App Store Connect scales the highest-resolution set down for smaller iPhones. StoreShots AI exports App Store screenshots at 1290 × 2796. #### Can I upload one screenshot size for all iPhones? Usually yes for iPhone: Apple asks for the highest required resolution and scales it down for smaller devices when your UI is consistent across them, so one 6.9-inch set (for example 1290 × 2796) covers most apps. iPad is separate — if your app runs on iPad, Apple requires at least one 13-inch iPad screenshot. Check Apple's current specifications before each release. #### What are ASO screenshot templates? Reusable layout systems defining backgrounds, type scale, device frames, safe zones, and export presets. They let you update UI captures each release without redesigning from scratch — whether maintained in Figma or generated by AI. #### How do templates work with localization? Regenerate headline copy per locale while locking visual layout. Flexible text regions accommodate longer translations. Avoid fixed-width English overlays pasted into other languages. #### Should App Store and Play Store templates match? Match brand colors, story order, and headline hierarchy. Export separate native sizes — 1290×2796 for App Store, 1080×1920 for Play Store — never stretch one store's PNG to fit the other. #### PNG or JPEG for 1290×2796 exports? PNG for slides with marketing text or gradients. JPEG only when slides are photo-heavy without small type that compression would harm. #### Does StoreShots AI handle template consistency? Yes. Generation applies consistent frames, backgrounds, and headline placement across slides and exports at store-correct dimensions. Chat-edit individual slides without losing system consistency. Sources: - [Screenshot specifications](https://developer.apple.com/help/app-store-connect/reference/screenshot-specifications) — Apple App Store Connect Help - [App Store product page](https://developer.apple.com/app-store/product-page/) — Apple Developer ### App Store Screenshot A/B Testing: A Practical Guide URL: https://storeshotsai.com/blog/app-store-screenshot-ab-testing-guide · Updated: 2026-11-19 · Author: StoreShots AI Editorial App store screenshot A/B testing with Apple PPO, custom product pages and Play experiments, plus a hypothesis framework so each test teaches you something. App store screenshot A/B testing means showing different screenshot sets to randomly split store visitors and comparing how many install. On iOS you use Product Page Optimization (up to three treatments against your original); on Google Play you use store listing experiments (up to three variants against your current listing). Change one variable per test. Both tools are built into App Store Connect and Play Console at no extra cost, yet many screenshot tests teach nothing: they change five things at once, stop after three days, or never collect enough traffic to conclude anything. This guide covers what each platform actually lets you test, how to write a hypothesis worth running, what small apps should do when significance is out of reach, and a test log you can copy into your own notes. ### What can you A/B test on app store screenshots? (Quick reference) Before planning a test, know the boundaries of each tool. These are the facts that decide what is testable and what is not. - Apple Product Page Optimization (PPO) tests the app icon, screenshots and app preview videos on your default product page. - PPO allows up to three treatments against the original, and a test can run for up to 90 days. - PPO does not test text metadata: app name, subtitle, description and keywords stay the same for every visitor. - Apple custom product pages are alternate product pages with their own screenshots, app previews and promotional text, each with a unique URL. Apple raised the limit from 35 to 70; confirm the current cap in App Store Connect. - Google Play store listing experiments test the icon, feature graphic, screenshots and, in localized experiments, short and full descriptions. - Play experiments allow up to three variants against your current listing. - Every Apple treatment still follows screenshot specs: up to 10 screenshots per device size per localization, PNG or JPEG, no transparency. - Every Play variant still follows Play specs: 2–8 phone screenshots, JPEG or 24-bit PNG without alpha, long side no more than 2.3 times the short side. ### How does Apple Product Page Optimization work? In App Store Connect you create a test, choose one to three treatments, decide what share of your product page traffic enters the test, and pick which localizations it covers. Each treatment is an alternate set of screenshots, app previews or icon. Visitors who reach your default product page are randomly assigned to the original or one of the treatments, and App Store Connect reports impressions, conversion rate and how each treatment performs against the original, along with an indication of how confident that comparison is. A few constraints shape your plan. Treatments go through App Review before the test can start. Alternate icons have to ship inside the app binary, so icon tests take release planning; screenshot tests do not. You run one test at a time, it can last up to 90 days, and you should read Apple's notes on what happens to a running test when you publish a new app version so a release does not cut your test short. The biggest limitation: PPO only tests visual assets. If you want to test messaging, the message has to live inside the screenshot image, as the headline on the slide. That is one reason screenshot headlines deserve real copywriting effort; our guide on [how to write app store screenshot copy](/blog/how-to-write-app-store-screenshot-copy) covers the craft. Results tell you which set converted better, not why, so the reason has to come from a well-framed hypothesis. - Decide the single variable before you open App Store Connect. - Keep every slide except the tested one identical between original and treatment. - Give the test a larger traffic share if your product page gets modest traffic. - Commit to a minimum run of one full week so weekday and weekend visitors are both represented. - Write the decision rule down before results arrive. ### Custom product pages: screenshot sets for specific audiences Custom product pages are segmentation, not a randomized A/B test. Each page gets its own screenshots, app previews and promotional text plus a unique URL, and you send specific traffic to it: an Apple Search Ads ad variation, a social campaign, a newsletter link or a partner promotion. App Store Connect reports performance per page, so you can see which page converts its own traffic best, but because each page receives different visitors, the comparison is not a controlled experiment. Where custom product pages shine is message-to-audience fit. Hypothetically, a habit tracker running one campaign aimed at runners and another aimed at students could build two pages: one whose first slide shows a running streak, the other showing study sessions. Same app, same UI, different first impression. Apple has also added options to associate keywords with custom product pages so they can surface in search; check App Store Connect for current availability and rules. A practical sequence: use custom product pages to learn which message resonates with a segment, then bring the strongest message back to your default page as a PPO treatment to confirm it works on general traffic. If you localize, the same thinking applies per market; see [localizing App Store screenshots](/blog/localize-app-store-screenshots). ### How do Google Play store listing experiments work? In Play Console, store listing experiments come in two types. Default graphics experiments test graphics on your default store listing. Localized experiments target specific languages and can test text (short and full description) as well as graphics. Either way, you run up to three variants against your current listing and choose what share of visitors sees the experiment. Play Console asks you to choose a target metric, typically first-time installers or retained first-time installers (people who installed and kept the app for at least a day), plus settings such as the confidence level and the minimum detectable effect. Play Console then estimates how many visitors and how much time the experiment needs. Exact options and defaults change, so check the current Play Console Help before you configure. Prefer retained first-time installers for screenshot tests when you can. A set that over-promises can lift raw installs while people uninstall within a day; retention-weighted metrics guard against rewarding misleading creative. Also remember that Play screenshots are a 2–8 phone image set with different behavior on the listing than iOS, so do not assume an iOS winner transfers unchanged. Our [Play Store screenshot generator](/play-store-screenshot-generator) page explains the Android export side. ### A hypothesis framework: one variable per screenshot test Write every test as one sentence: “If we change [variable] on [slide] from [A] to [B], [metric] will improve because [evidence].” Evidence can be review language, support tickets, the search terms that bring visitors in, or a gap you see across competing listings. A test without a “because” can still pick a winner, but it will not tell you what to do next. Change one variable per test. If treatment B has a new headline and a new hero screen, a win cannot be attributed to either. Start with the first slide, because on iOS the first few portrait screenshots appear directly in search results, so it reaches the most visitors. For deciding what belongs in each position, see [the screenshot order that converts](/blog/app-store-screenshot-order-that-converts). - First-slide headline: outcome wording versus feature wording, with the same visual underneath. - First-slide visual: which real app screen is the hero, with the same headline. - Slide order: move your strongest differentiator from slide four to slide two. - Background style: flat brand color versus gradient versus a panoramic background that connects slides. - Localized copy: a direct translation versus a headline rewritten for that market. ### Sample size reality: what if your app is too small to test? Conversion tests need volume, and this is where most indie apps get honest bad news. Detecting a small difference in conversion rate typically requires thousands of product page visitors per variant. The math is unforgiving: halving the effect size you want to detect roughly quadruples the sample you need. An app with a few hundred product page views a week can run a test for the full 90 days and still end inconclusive. That is not an execution failure; it is what the data can support. Inconclusive is information. It tells you the two sets do not differ by a large amount, so you can ship whichever version you prefer for brand or clarity reasons and move on. If you need direction sooner, combine the following tactics. - Test bigger swings: a completely different first-slide concept, not a reworded adjective. - Run one treatment instead of three so traffic splits two ways, not four. - Allocate a larger share of traffic to the test. - Run on whichever store gives you more product page traffic. - Concentrate paid traffic on a custom product page to evaluate one message. - Run qualitative five-second tests: show 5–10 people from your audience the first three slides for five seconds, then ask what the app does and who it is for. ### How to produce screenshot variants without a design sprint For small teams the real bottleneck is often production, not statistics. Rebuilding a whole set in a design tool for every hypothesis means you test less. In StoreShots you upload 3–10 real screenshots from your app, the AI maps each screen to a purpose, headline, subtext and visual theme, and you generate the pack. To create a treatment, chat-revise only the slide under test, for example “rewrite the first headline around time saved instead of features.” A slide revision costs 1 credit and re-exporting is free, so control and treatment come from the same project with every other slide identical. Because your uploaded UI stays the source, treatments show the real app rather than a redrawn approximation, which keeps tests honest. Be clear about scope: the [App Store screenshot generator](/app-store-screenshot-generator) exports iPhone PNGs at 1290×2796 and Google Play phone PNGs at 1080×1920. It does not generate iPad screenshots, Play feature graphics or app preview videos, so produce those separately if your test includes them. Credits come in one-time packs that never expire; see [pricing](/pricing). [Create screenshot variants with StoreShots](https://storeshotsai.com/login?next=%2Fdashboard) ### Screenshot A/B test log template Tests compound only if you remember what you learned. Copy these fields into a spreadsheet or doc and fill one row per test. - Test ID and platform (for example iOS-PPO-03 or Play-LOC-DE-01). - Start date, planned end date and actual end date. - Hypothesis sentence: if we change X to Y, metric improves because Z. - The single variable tested and the slide numbers affected. - Control and treatment export file names or ZIP references. - Traffic allocation and the localizations or languages included. - Target metric and the decision rule, written before launch. - Visitors or impressions per arm when the test ended. - Outcome: treatment won, original won, or inconclusive, with the confidence the console reported. - External events during the test: app releases, featuring, campaigns, holidays. - Decision taken and the date it was applied. - What you learned and the next hypothesis it suggests. ### Reading results and rolling out the winner Discipline at the end matters as much as setup. Treat these steps as a checklist before you apply anything. 1. Do not stop the test the first day a treatment looks ahead; early leads often shrink. 2. Check the confidence the console reports against the decision rule you wrote before launch. 3. Look for confounders such as a release, featuring or a paid campaign spike during the test window. 4. Apply the winning treatment or variant to your default listing from the console. 5. Log the result, then run the next single-variable test, ideally building on the winner. 6. Re-test periodically, because seasons, competitors and your own app change over time. ### Where to find ideas for your next screenshot test The best hypotheses usually come from a pattern you have not tried yet: an outcome headline instead of a feature label, a before/after slide, a panoramic background. Our breakdown of [12 reusable app store screenshot patterns](/blog/app-store-screenshot-examples-patterns) gives you a menu of distinct concepts that make good treatments against your current set. Start with one first-slide test, run it long enough to mean something, log it, and repeat. A steady habit of small, well-framed tests will teach you more about your audience than a single big redesign. #### Can you A/B test App Store screenshots? Yes, Apple's Product Page Optimization lets you test up to three alternate screenshot sets against your original. Visitors to your default product page are split randomly, and App Store Connect reports conversion for each treatment. Treatments need App Review approval, and a test can run for up to 90 days. #### How long should a screenshot A/B test run? Run it at least one full week and until the console reports a confident result or your planned end date arrives. A full week captures weekday and weekend behavior. Apple tests can last up to 90 days; low-traffic apps may need most of that window and can still end inconclusive. #### Can I test my app name or subtitle with Product Page Optimization? No, Product Page Optimization only tests the app icon, screenshots and app preview videos. Your name, subtitle, description and keywords stay the same for all visitors. To test messaging on iOS, put the message in the screenshot headline itself and test that slide as a treatment. #### What is the difference between product page optimization and custom product pages? Product page optimization is a randomized test on your default page, while custom product pages are separate pages for specific traffic. Custom pages have unique URLs you use in Apple Search Ads or campaigns. Because each page gets different visitors, comparing them shows audience fit, not a controlled test result. #### Which metric should I use for Google Play store listing experiments? Retained first-time installers is usually the safer choice for screenshot tests. It counts people who installed and kept the app for at least a day, so it penalizes creative that over-promises. First-time installers alone can reward a set that lifts installs while increasing quick uninstalls. #### Is screenshot A/B testing worth it for an app with little traffic? It can be, but only for large differences, and you should expect inconclusive results. Test one bold variant instead of three, give the test more traffic, and supplement with five-second tests where real users describe what your first slides communicate. Treat inconclusive as “no big difference” and move on. #### Can StoreShots create screenshot variants for testing? Yes, you can generate a pack from real screenshots and chat-revise a single slide to create a treatment. Each slide revision costs 1 credit and re-exporting is free. StoreShots exports iPhone 1290×2796 and Play phone 1080×1920 PNGs, not iPad screenshots, feature graphics or preview videos. Sources: - [Product page optimization](https://developer.apple.com/app-store/product-page-optimization/) — Apple Developer - [Custom product pages](https://developer.apple.com/app-store/custom-product-pages/) — Apple Developer - [Add preview assets: screenshots and graphics](https://support.google.com/googleplay/android-developer/answer/9866151?hl=en) — Google Play Console Help - [Store listing experiments](https://support.google.com/googleplay/android-developer/answer/9793453?hl=en) — Google Play Console Help ### App Screenshot Design Best Practices for 2026 URL: https://storeshotsai.com/blog/app-screenshot-design-best-practices · Updated: 2026-11-19 · Author: StoreShots AI Editorial App screenshot design best practices: hierarchy, thumbnail-legible type, contrast, backgrounds, device frames and safe areas, so your listing looks premium. The core app screenshot design best practices are: make the first three slides carry your strongest story, give each slide one clear hierarchy (headline, then UI), use type large enough to read at thumbnail size, keep strong contrast, pull colors from your icon, and apply one consistent background, frame and layout system across every slide. Design is what makes good copy and good UI readable in the few seconds a shopper spends on your listing. You do not need an agency to get it right; you need a small set of rules applied consistently. This guide covers hierarchy, legibility, color and backgrounds, device frames, safe areas, dark mode, localization, Apple's guidelines on what not to do, and a pre-export checklist you can run before every upload. ### Why do the first three screenshots matter most? In App Store search results, only the first few screenshots are visible next to your icon and title, typically three portrait slides on iPhone. Many people decide whether to tap from that strip alone. On your product page the carousel shows more, but attention still falls off quickly after the opening slides. Design the first three as a unit. They should share one background treatment, one headline style and one frame style so they read as a single panel, and together they should communicate what the app does, how it works and why it is different. Put your clearest, most visually distinctive screen first; a settings list or login screen in position one wastes the most valuable pixels you have. Our guide to [screenshot order that converts](/blog/app-store-screenshot-order-that-converts) covers sequencing in detail. ### How to build visual hierarchy on each slide Every slide needs an obvious reading order. In almost every effective app store screenshot design, that order is headline first, then the UI that proves it, then optional subtext. If a viewer's eye lands on a decorative shape or a tiny badge first, the hierarchy is broken. Size and position do most of the work. Put the headline in the top third, set it at least twice the size of any subtext, and let the device or UI occupy the remaining space as the dominant visual element. Use one accent color for emphasis rather than three. Copy is half of hierarchy, so pair this with our guide on [writing App Store screenshot copy](/blog/how-to-write-app-store-screenshot-copy). - One focal point per slide: the headline or the key UI moment, not both competing - Headline in the top third, consistently placed across all slides - Subtext clearly smaller and lighter, or omitted entirely - Device mockup centered or aligned to a consistent grid line - Crop or zoom into the important part of the UI when the full screen is too dense to read - Avoid callout arrows, stickers and badges unless they point to something essential ### Type size, contrast and accessibility at thumbnail size Your slides are exported at full resolution (1290×2796 for the main iPhone size, 1080×1920 as a common Google Play size), but they are judged at thumbnail size. Headline type that looks generous in your design tool can be unreadable in search results. A useful starting point is a headline cap height of roughly 4–6% of the slide's height, then verify by viewing the export at about 20% scale on a real phone. Contrast matters more at small sizes. Aim for at least the WCAG 4.5:1 contrast ratio between headline text and its background, and higher for thin or light font weights. Bold or semibold weights survive downscaling better than light ones. Avoid placing text over photos or busy gradients unless you add a solid or blurred backing. - Use a bold or semibold weight for headlines; avoid hairline and light weights - Check headline contrast against WCAG's 4.5:1 guidance with any contrast checker - Do not rely on color alone to convey meaning; pair color with a label or icon - Keep line length short; two lines is a practical maximum for headlines - Test in grayscale: if the hierarchy disappears, contrast is too low - Respect users with low vision by never shrinking text to fit more words ### Choosing colors and screenshot backgrounds Start from your brand: pull one primary and one accent color from your app icon or main button color. When the screenshots echo the icon, the listing reads as one product and users can connect it to the app on their home screen later. Keep the palette to two or three colors plus neutrals. For the screenshot background, soft gradients or subtle textures usually look more intentional than flat gray, but the background must never compete with the UI. Panoramic backgrounds, where one continuous image or gradient flows across several slides, can make the first three slides feel like a single banner. They are worth the effort only if each slide still works on its own, because Google Play and some App Store layouts show slides individually and users can land mid-carousel. - Gradients: two adjacent hues from your brand palette; avoid harsh rainbow blends - Solid backgrounds: fine for minimal brands, but add depth with a shadow on the device - Panoramic: align seams to the exact slide width and never split a headline or device across a seam - Photography: use only when it reinforces context (travel, food, fitness) and keep text off busy areas - Category contrast: look at the top results for your keywords and choose a background that stands out from them [Generate a consistent screenshot set](https://storeshotsai.com/app-store-screenshot-generator) ### Device frame mockup vs frameless screenshots A device frame mockup signals "this is a real phone app" and gives the UI a clear edge against the background. It works well for most consumer apps, especially when the background is colorful. The trade-off is space: a frame shrinks the visible UI, which can hurt dense screens. Frameless designs (the UI as a rounded card, or a zoomed crop of a key element) give more room to the interface and feel modern. They suit apps where the UI itself is the selling point, and games, which usually show full-bleed gameplay. Whichever you choose, use it on every slide. Mixing framed and frameless slides is one of the quickest ways to make a listing look unfinished. Also avoid showing a specific non-current device model that dates your listing, and do not show an iPhone frame in your Google Play screenshots. ### Safe areas, cropping and app screenshot layout Keep headlines and important UI away from the slide edges. Leave a margin of roughly 5–8% of the slide width on each side so nothing feels cramped in the carousel and nothing is lost if a surface rounds corners or crops slightly. Keep the same margins on every slide so headlines line up when slides sit side by side. Clean up your captures before they go into the layout. Use realistic but tidy demo data, a full battery and a neutral time in the status bar; on iOS, the Simulator's status bar override (xcrun simctl status_bar) makes this repeatable. Make sure the right export sizes go into the right slots: see our [App Store screenshot size guide](/blog/app-store-screenshot-size-aso-templates-guide-2026) and the [Google Play size requirements](/blog/play-store-screenshot-generator-complete-guide-2026). - Side margins around 5–8% of slide width; top margin above the headline at least as large - Never let a device frame or UI run into the headline area - Crop into the meaningful part of long screens instead of shrinking the whole screen - Use a consistent grid: same headline baseline and device position on every slide - No personal data, real customer names or placeholder "lorem ipsum" in demo content ### Consistency system, dark mode and localization space Treat your store listing design as a template, not a series of one-off posters. Define the font, sizes, colors, background treatment, frame style, corner radius, shadow and margins once, then reuse them every release. A template is what lets you swap in new UI captures after an update without redesigning the set. If your app supports dark mode, decide deliberately which appearance to show. A dark UI on a dark background can disappear at thumbnail size, so add contrast with a lighter background or a glow. Some teams dedicate one slide to dark mode as a feature. For localization, leave headline space for languages that run longer than English, and do not shrink type per locale; adjust line breaks instead. Our [screenshot localization guide](/blog/localize-app-store-screenshots) covers the full workflow. - Lock one type scale, one frame style, one corner radius and one shadow for all slides - Store the system as a template so updates only replace UI captures and copy - Dark UI on dark backgrounds needs extra edge contrast - Design headline areas with spare room for longer translations - Localize UI captures too, so the headline language matches the app language ### What not to do: Apple's guidelines and misleading screenshots Apple's App Review Guidelines say screenshots should show the app in use, not merely title art, a login page or a splash screen. Metadata, including screenshots, must accurately reflect the app's core experience. Google Play's policies similarly prohibit misleading store listing content. Beyond rejection risk, a listing that oversells creates disappointed users and poor reviews. Design choices can mislead even when the UI is real. Mockups of features that are not shipped, edited UI that the app cannot produce, or fake system notifications all cross the line. Keep the polish in the presentation layer (background, frame, type) and keep the UI honest. - Do not use splash screens, login screens or logo-only slides as your screenshots - Do not show features that are not in the shipped version - Do not imitate system UI, alerts or Apple and Google badges in a misleading way - Do not add unverifiable claims like "#1 app" or invented ratings - Do not use transparent PNGs; Apple and Google Play both reject images with alpha ### Quick reference: screenshot design specs and rules These are the facts and defaults worth keeping beside your design file. Apple and Google update requirements, so confirm current specifications in App Store Connect and Play Console before you upload. - Apple: up to 10 screenshots per device size per localization; PNG or JPEG, no transparency - Apple 6.9-inch iPhone slot accepts 1320×2868, 1290×2796 and 1260×2736 portrait - Apple requires a 13-inch iPad set (2064×2752 or 2048×2732) if your app runs on iPad - Google Play: 2–8 phone screenshots; JPEG or 24-bit PNG without alpha; 1080×1920 portrait recommended - Google Play: long side no more than 2.3 times the short side; 320px minimum, 3840px maximum per side; 9:16 at 1080×1920 or larger recommended - Google Play also requires a 1024×500 feature graphic, designed separately from screenshots - Design rule of thumb: 3–7 word headlines, bold weight, 4.5:1 contrast or better, 5–8% side margins ### Pre-export checklist for app store screenshot design Run this list on the actual exported files, viewed on a phone, before uploading. For a broader submission check covering metadata and sizes, use our [store screenshot checklist](/blog/store-screenshot-checklist-before-submit). If you would rather start from a consistent system than build one, StoreShots AI takes 3–10 real screenshots of your app, applies one visual theme with headlines across the pack, and exports App Store PNGs at 1290×2796 and Google Play PNGs at 1080×1920 in a ZIP. It does not create iPad sets, feature graphics or preview videos, so plan those separately. Credits are one-time packs with no subscription; see [pricing](/pricing). 1. The first three slides tell the core story on their own 2. Every headline is readable at about 20% scale on a phone 3. Headline contrast meets 4.5:1 or better on every slide 4. Colors echo the app icon; palette limited to two or three colors plus neutrals 5. Same font, frame style, margins and headline position on every slide 6. No text or UI touches the slide edges; panoramic seams line up 7. Status bars are clean and demo data is realistic and private 8. Every screen shows the shipped app in use, with no misleading mockups 9. Each locale's headlines fit without shrinking type, and UI language matches 10. Files are the correct pixel size, PNG or JPEG, with no alpha channel #### What are the most important app screenshot design best practices? Prioritize the first three slides, give each slide a clear headline-then-UI hierarchy, and keep type readable at thumbnail size. Then apply one consistent system of colors, background, frame and margins across every slide, and make sure every screen shows the real app in use. #### Should I use device frames in App Store screenshots? Device frames are a good default for most consumer apps, but they are optional. Frames make the UI read as a phone app; frameless layouts give more space to dense interfaces. Choose one approach and use it on every slide rather than mixing styles. #### What background works best for app screenshots? A soft gradient or subtle texture built from your app icon's colors works for most apps. The background should support the UI, not compete with it. Choose colors that stand out from competitors in your category and keep contrast high behind headlines. #### How big should text be on app store screenshots? Make headline text large enough to read when the slide is shown as a search-result thumbnail. A starting point is a cap height around 4–6% of slide height in a bold weight, then confirm by viewing the export at about 20% scale on a phone. #### Can App Store screenshots show features that are not built yet? No, screenshots should show the app as it actually works. Apple's App Review Guidelines say screenshots should show the app in use and metadata must reflect the core experience. Showing unreleased features risks rejection and disappointed users who leave poor reviews. #### Should screenshots use light or dark mode? Use whichever appearance makes your UI clearest and matches most users, usually light mode. If dark mode is a selling point, dedicate one slide to it. Dark UI on a dark background needs extra contrast, such as a lighter backdrop, so it does not disappear at thumbnail size. Sources: - [Screenshot specifications](https://developer.apple.com/help/app-store-connect/reference/screenshot-specifications) — Apple App Store Connect Help - [App Store product page](https://developer.apple.com/app-store/product-page/) — Apple Developer - [App Review Guidelines](https://developer.apple.com/app-store/review/guidelines/) — Apple Developer - [Add preview assets: screenshots and graphics](https://support.google.com/googleplay/android-developer/answer/9866151?hl=en) — Google Play Console Help ### Play Store vs App Store Screenshots: What to Share or Split URL: https://storeshotsai.com/blog/play-store-vs-app-store-screenshot-strategy · Updated: 2026-11-19 · Author: StoreShots AI Editorial Play Store vs App Store screenshots compared: sizes, counts, ratio rules, display and UI conventions, plus what to share or split to ship both listings faster. Play Store vs App Store screenshots differ in size, count, and ratio rules: Apple's 6.9-inch iPhone slot accepts 1290×2796 and up to 10 screenshots, while Google Play takes 2–8 phone screenshots with a long side no more than 2.3 times the short side, and recommends 9:16 portrait at 1080×1920 or larger. Share the story and headlines; split frames, captures, and export sizes. Most cross-platform teams lose time in one of two ways. Either they maintain two completely separate design files that drift apart every release, or they upload one set everywhere and end up with cropped headlines, an iPhone frame on Google Play, or a rejected upload. This guide shows where the stores genuinely differ, where they do not, and a workflow that keeps one narrative with two native exports. ### Play Store vs App Store screenshot specs side by side Start with the hard constraints, because they decide what you can reuse at all. The numbers below come from Apple's screenshot specifications and Google Play Console Help. Both stores update requirements, so confirm in App Store Connect and Play Console before a release. For a deeper single-store breakdown see the [App Store screenshot size guide](/blog/app-store-screenshot-size-aso-templates-guide-2026) and the [Google Play screenshot size & requirements guide](/blog/play-store-screenshot-generator-complete-guide-2026). - Screenshot count — App Store: up to 10 per device size per localization. Google Play: 2–8 phone screenshots. - Main phone size — App Store: the 6.9-inch iPhone slot accepts 1320×2868, 1290×2796 or 1260×2736 portrait. Google Play: 1080×1920 portrait (9:16) is the common recommendation. - Older iPhone slot — App Store: the 6.5-inch slot accepts 1284×2778 and 1242×2688. - Ratio rule — Google Play: each side between 320 px and 3840 px, and the long side no more than 2.3× the short side; 9:16 portrait (minimum 1080×1920) is recommended. App Store: fixed pixel dimensions per slot rather than a ratio range. - Formats — App Store: PNG or JPEG, no transparency. Google Play: JPEG or 24-bit PNG, no alpha. - Tablet — App Store: if your app runs on iPad, a 13-inch iPad set (2064×2752 or 2048×2732) is required. Google Play: tablet screenshots are separate, optional-but-recommended assets. - Header asset — Google Play: a 1024×500 feature graphic is required. App Store: no equivalent banner. - Video — App Store: app preview videos uploaded per device size, which can appear before screenshots. Google Play: a promo video added as a YouTube URL. ### Why you cannot upload the same file to both stores The quiet trap is the ratio. A 1290×2796 image has a long side about 2.17× its short side. That is inside Google Play's 2.3× limit, so Play will accept the file, but it is not the 9:16 portrait format Google recommends (minimum 1080×1920) for its recommendation surfaces, and it still shows iPhone UI on an Android listing. Going the other way, a 1080×1920 image is not one of the pixel sizes Apple accepts for the iPhone slots, so App Store Connect will not take it. Even if you squeeze one into the other's dimensions, the composition breaks. The iOS frame is taller and narrower, so a layout tuned for it either gets letterboxed or loses vertical space for the headline when converted to 9:16. Stretching pixels makes UI text soft, which shows up immediately next to sharp competitor listings. Export native masters for each store instead; if you are already fighting upload errors, the [store screenshot checklist](/blog/store-screenshot-checklist-before-submit) covers the common rejections. ### How each store displays screenshots in search and on the product page On the App Store, search results for an app without an app preview typically show the first few portrait screenshots right under the name and icon. That makes your first three frames a search-results asset, not just product-page decoration. Treat them as a mini-pitch that reads at thumbnail size, and see [App Store screenshot order that converts](/blog/app-store-screenshot-order-that-converts) for sequencing. On Google Play, the layout varies more by device, query, and listing. Search results often lean on the icon, title, and rating, with screenshots or video surfacing in some placements. On the product page, the promo video or feature graphic can occupy the top of the listing, with the screenshot carousel beneath. The practical consequence: on Play, the feature graphic and the first two screenshots share the job of the first impression, so they need to agree visually. Both stores show screenshots in a horizontal carousel that many visitors only partly scroll. Front-load the outcome on both, regardless of how many total frames you upload. ### Audience and UI conventions: Android vs iOS Android and iOS users recognise their own platform at a glance: navigation patterns, status bars, system sheets, back behaviour, and device silhouettes. A Google Play listing that shows an iPhone frame, a Dynamic Island, or iOS-style share sheets reads as a port at best and careless at worst. Use Android captures and a neutral or Android-style device frame on Play, and iPhone captures and frames on the App Store. Policy points the same direction. Google Play's metadata policy prohibits misleading store listing content, and its preview asset guidance asks that screenshots represent the actual in-app experience. Showing another platform's UI, or features that only exist on iOS, risks confusing users and inviting a review issue. Apple's guidelines likewise expect screenshots to show the app in use. Never capture a screen on one platform and present it as the other. Audience mix can differ too. If your Android users skew toward different regions or price sensitivity, the same headline can land differently. That is a messaging test, not a reason to rebuild the whole set. ### What to keep shared across both stores The expensive part of screenshots is thinking: which outcome leads, which proof follows, what each headline says. That work is platform-neutral, so do it once. Most of the time you can reuse screenshots for both stores at the story level while still exporting different files. - The narrative order: hero outcome, then proof, then depth features, then trust or social proof - Headline and subtext copy (adjust only where a platform-specific feature differs) - Brand colours, typography, and background treatment - Localization plan and translated strings - The underlying feature list each frame demonstrates ### What to split per store Split anything that is physically tied to a platform or a store's format. This list is where most of the per-store effort belongs. - Device frames: iPhone frames on the App Store; Android or frameless on Google Play - UI captures: real screens from the iOS build and the Android build respectively - Aspect ratio and export size: 1290×2796 (or another accepted 6.9-inch size) vs 1080×1920 - Feature graphic: Google Play only, 1024×500, designed as its own banner - Video: app preview on iOS vs a YouTube promo video on Play - Screenshot count: up to 10 on iOS vs 2–8 on Play, so trim the weakest frames for Play - Platform-only features: widgets, watch apps, or integrations that exist on one OS ### Decision table: reuse or split? Use this as a quick reference when planning a release. Each line reads: asset — decision — reason. - Story and slide order — Share — the user's job does not change between platforms - Headlines and subtext — Share, with edits for platform-only features — copy is the costliest part to rewrite - Background and brand style — Share — keeps the brand recognisable across stores - Device frame — Split — an iPhone frame on Google Play misrepresents the app - In-app captures — Split — each store should show its own platform's real UI - Export size and ratio — Split — 1290×2796 passes Play's 2.3:1 limit but is not the recommended 9:16; 1080×1920 is not an accepted iPhone size - Feature graphic — Play only — required 1024×500 banner with no iOS equivalent - Video — Split — app previews and Play promo videos have different formats and hosting - Screenshot count — Split — trim to 8 or fewer for Play ### Testing screenshots on each store Both stores let you test creative natively, but the tools differ. On the App Store, Product Page Optimization lets you test up to three treatments against your original product page, varying icons, screenshots, and app previews, with tests running for up to 90 days. On Google Play, store listing experiments can test the icon, feature graphic, screenshots, and short or full description, with up to three variants against the current listing, and localized experiments for specific languages. Because the stores are tested separately, a winner on one is a hypothesis for the other, not a proven result. A headline that wins on Google Play is worth trying in a PPO treatment, but audience and layout differences mean it may not transfer. The [App Store screenshot A/B testing guide](/blog/app-store-screenshot-ab-testing-guide) covers test design and how long to wait before calling a result. ### A one-project workflow for both stores with StoreShots The goal is one creative direction and two native outputs without maintaining two design files. In [StoreShots AI](/play-store-screenshot-generator), the uploaded captures stay the source of truth; the AI plans purposes, headlines, and themes around them rather than redrawing your UI. 1. Capture 3–10 real screens from the iOS build and, separately, from the Android build 2. Write down the shared story: hero outcome, two or three proof frames, then depth 3. Create a project with the iOS captures and preview the hero frame before generating 4. Generate the App Store pack and export PNGs at 1290×2796 as a ZIP 5. Repeat with the Android captures and export the Google Play pack at 1080×1920 6. Align headlines across both packs, using chat revisions on individual slides where they drifted 7. Design the 1024×500 feature graphic separately; StoreShots does not generate feature graphics, iPad sets, Android tablet sizes, or app preview videos 8. Upload, then plan PPO and store listing experiments from the same headline hypotheses [Generate App Store and Play Store sets](https://storeshotsai.com/login?next=%2Fdashboard) ### Quick reference: Play Store vs App Store screenshots If you only remember a handful of facts, make them these. For cost planning, credits are one-time packs that never expire; see [pricing](/pricing). - App Store: up to 10 screenshots per device size per localization; Google Play: 2–8 phone screenshots - 1290×2796 is accepted in Apple's 6.9-inch slot; 1080×1920 is the common Play phone size - Google Play accepts a long side up to 2.3× the short side but recommends 9:16, so tall iPhone masters are not the best fit - Neither store accepts transparency in screenshots - Google Play requires a 1024×500 feature graphic; the App Store has no equivalent - Do not show iPhone frames or iOS UI on Google Play - Share story and copy; split frames, captures, sizes, and the feature graphic - Test with PPO on iOS and store listing experiments on Play, separately #### Can I use the same screenshots for the App Store and Google Play? You can reuse the story and headlines, but you should not reuse the same files. A 1290×2796 iPhone screenshot fits within Google Play's 2.3:1 limit but misses the recommended 9:16 format and shows iOS UI, and 1080×1920 is not an accepted iPhone size. Export native sets per store and swap in each platform's own UI captures and device frames. #### What size should Android vs iOS screenshots be? Use 1080×1920 portrait for Google Play phones and 1290×2796 (or another accepted 6.9-inch size) for the App Store. Google Play allows any size between 320 and 3840 pixels per side with the long side at most 2.3 times the short side, while Apple specifies exact pixel sizes per device slot. Check App Store Connect before each release, since Apple updates its specifications. #### How many screenshots does each store allow? The App Store allows up to 10 screenshots per device size per localization, and Google Play allows 2–8 phone screenshots. If your iOS set has ten frames, cut the two weakest for Google Play rather than cramming two features into one frame. Front-load the strongest outcome on both, because many visitors never scroll the full carousel. #### Is it a problem to show an iPhone in Google Play screenshots? Yes, avoid it. An iPhone frame or iOS interface on Google Play misrepresents what Android users will get, and Google Play's metadata policy prohibits misleading listing content. Use real Android captures with a neutral or Android-style frame. The same applies in reverse: show iOS screens and iPhone frames on the App Store. #### Does the App Store have a feature graphic like Google Play? No, the 1024×500 feature graphic is a Google Play requirement with no App Store equivalent. On the App Store, the first screenshots or an app preview video carry the first impression instead. Design the feature graphic as its own banner that matches your first two Play screenshots, rather than cropping a screenshot to fit. #### Should I A/B test screenshots on both stores? Yes, but treat each store's result separately. Apple's Product Page Optimization tests up to three treatments for up to 90 days, and Google Play store listing experiments test up to three variants against the current listing. A winner on one store is a strong hypothesis for the other, not a guaranteed result, because audiences and layouts differ. Sources: - [Screenshot specifications](https://developer.apple.com/help/app-store-connect/reference/screenshot-specifications) — Apple App Store Connect Help - [Product page optimization](https://developer.apple.com/app-store/product-page-optimization/) — Apple Developer - [Add preview assets: screenshots and graphics](https://support.google.com/googleplay/android-developer/answer/9866151?hl=en) — Google Play Console Help - [Store listing experiments](https://support.google.com/googleplay/android-developer/answer/9793453?hl=en) — Google Play Console Help ### App Store Screenshot Wrong Dimensions Error: How to Fix It URL: https://storeshotsai.com/blog/fix-app-store-screenshot-wrong-dimensions-error · Updated: 2026-11-10 · Author: StoreShots AI Editorial Seeing “The dimensions of one or more screenshots are wrong” in App Store Connect? Find the cause, check pixel sizes, and upload a set that passes first time. “The dimensions of one or more screenshots are wrong” means App Store Connect found an image whose exact pixel width and height do not match any size accepted for that device slot. Fix it by checking each file’s real pixel size, re-exporting at an accepted size such as 1290×2796 for the 6.9-inch iPhone slot, and removing any transparency. The error is frustrating because App Store Connect does not tell you which file failed or why. In practice it almost always comes down to a short list of causes: the wrong slot, a file that is one pixel off, a design tool exporting at the wrong scale, a rotated canvas, or an alpha channel. This guide walks through each one, shows how to check pixel sizes on macOS and Windows, and gives you a repeatable fix flow so the next upload goes through on the first try. ### What does “the dimensions of one or more screenshots are wrong” mean? Each screenshot slot in App Store Connect (the 6.9-inch iPhone display, the 6.5-inch display, the 13-inch iPad and so on) has a fixed list of accepted pixel sizes. When you drag files in, App Store Connect reads the pixel dimensions stored in each image and compares them to that list. There is no tolerance: 1290×2795 fails just as hard as 800×600, and App Store Connect will not crop or resize for you. Two things the check does not care about: how big the file looks on your screen and the DPI or “resolution” metadata some editors write. A 1290×2796 PNG saved at 72 DPI and one saved at 300 DPI are identical as far as Apple is concerned. Only the pixel grid counts, plus the format rules (PNG or JPEG, no transparency). If you are new to the size landscape, our [App Store screenshot size guide](/blog/app-store-screenshot-size-aso-templates-guide-2026) explains every display class in more depth. This article stays focused on getting a rejected upload accepted. ### Accepted App Store screenshot sizes: quick reference These are the sizes most iPhone and iPad apps need in 2026, based on Apple’s screenshot specifications. Apple updates the list when new hardware ships, so confirm against App Store Connect Help before a major release. - 6.9-inch iPhone slot (portrait): 1320×2868, 1290×2796 or 1260×2736 px - 6.9-inch iPhone slot (landscape): the same sizes with width and height swapped, e.g. 2796×1290 - 6.5-inch iPhone slot (portrait): 1284×2778 or 1242×2688 px - 13-inch iPad slot (portrait): 2064×2752 or 2048×2732 px, required if your app runs on iPad - Formats: PNG or JPEG only, RGB, no transparency or alpha channel - Quantity: 1 to 10 screenshots per device size per localization - No tolerance: a single pixel over or under fails the whole upload ### The most common causes of the wrong dimensions error Work through these in order. The slot and pixel-size causes are the quickest to rule out; the alpha channel issue tends to take longest to spot because the image looks perfect. - **Wrong slot (6.9 vs 6.5 inch).** A 1284×2778 file is valid, but only in the 6.5-inch slot. Dropping it into the 6.9-inch slot, or dropping iPhone files into the iPad tab, triggers the error. - **Off-by-one pixel.** Manual crops, a canvas set to 1290×2797, or a frame with a fractional height that rounds up on export all produce files that are one pixel off. - **@1x or @2x export scale.** Figma and Sketch iPhone frames are often 430×932 points. Exported at 1x you get 430×932, at 2x you get 860×1864. You need 3x to reach 1290×2796. - **Landscape vs portrait mix-up.** A canvas that was rotated, or an export that swapped width and height, produces 2796×1290 when you meant a portrait shot. Make sure orientation is intentional. - **Alpha channel or transparency.** PNGs exported with transparency enabled, even if every pixel is opaque, can be rejected. Rounded-corner device frames on a transparent canvas are the usual culprit. - **Wrong format or color mode.** WebP, HEIC, TIFF or CMYK files are not accepted. Save as an RGB PNG or JPEG. - **Window screenshots instead of device captures.** Grabbing the Simulator window with a system screenshot shortcut captures the window at your display’s scale, often with a bezel, instead of the device’s native resolution. - **Missing iPad set.** If your app supports iPad, App Store Connect requires 13-inch iPad screenshots. That shows up as a missing-screenshots blocker rather than this exact message, but it often surfaces in the same submission. ### How to check a screenshot’s exact pixel size on Mac and Windows Never trust the filename or the artboard name. Check the file itself, ideally all files at once, before you open App Store Connect. On macOS, open the image in Preview and choose Tools > Show Inspector. The General tab lists the pixel dimensions. For a whole folder, use Terminal: sips -g pixelWidth -g pixelHeight *.png prints the width and height of every PNG, and sips -g hasAlpha *.png tells you which files still carry an alpha channel. That pair of commands is the fastest App Store screenshot size checker you already have installed. On Windows, right-click the file, choose Properties, then open the Details tab. Under Image you will see Dimensions (for example 1290 x 2796) and Bit depth. A bit depth of 32 on a PNG usually means it includes an alpha channel; 24 means plain RGB. In File Explorer you can also add a Dimensions column in Details view to scan a folder quickly. ### Step-by-step: fix a rejected App Store Connect screenshot upload Follow this flow whenever an upload fails. It takes a few minutes and avoids the trial-and-error loop of re-dragging files into the browser. 1. Note which tab and slot you were uploading to (iPhone 6.9-inch, iPhone 6.5-inch or iPad 13-inch). 2. Run a size check on every file in the batch with sips or Windows Properties and list any file that does not match the accepted sizes for that slot. 3. Check orientation: portrait files should be taller than they are wide. Fix any swapped width and height at the source, not by rotating the final PNG. 4. Check for alpha with sips -g hasAlpha or the Windows bit depth, and flatten any file that has it (see the next section). 5. Re-export failing files from your design tool at the correct scale (3x for a 430×932 point frame) or with the canvas set to exact pixels. Avoid stretching an image from one aspect ratio to another; crop or rebuild the layout instead. 6. Confirm the format is PNG or JPEG in RGB, then re-run the size and alpha checks on the new files. 7. Upload the batch to the correct slot again. If it still fails, upload files one by one to find the single bad file. ### How to remove the alpha channel from an App Store screenshot Transparency is the sneakiest cause because the screenshot looks finished. The fix is to flatten the image onto a solid background and save it without an alpha channel. On macOS, the quickest route is converting to JPEG, which cannot hold transparency: sips -s format jpeg input.png --out output.jpg. If you prefer to keep PNG, open the file in Preview, choose File > Export, pick PNG and untick the Alpha checkbox. If you have ImageMagick installed, magick input.png -background white -alpha remove -alpha off output.png flattens onto white and drops the channel. In Figma, make sure the exported frame has a solid fill rather than a transparent background, especially if your device frame has rounded corners. In Canva or similar tools, avoid the transparent-background export option. After exporting, run the alpha check again before uploading. ### 6.9-inch vs 6.5-inch screenshot slot: which one do you need? Apple treats the 6.9-inch iPhone display as the primary iPhone screenshot set, and it can scale your largest set down for smaller iPhone displays. For most apps, one great 6.9-inch set at 1290×2796 is enough; App Store Connect shows which slots are required for your app, so check there rather than assuming. The mix-up usually happens when an older template or a 6.5-inch simulator produces 1284×2778 or 1242×2688 files. Those are valid sizes, but only for the 6.5-inch slot. Either upload them there or re-export at a 6.9-inch size. The aspect ratios are close but not identical, so stretching 1284×2778 to 1290×2796 will slightly distort your UI and headline text. If your app runs on iPad, plan a separate 13-inch iPad set at 2064×2752 or 2048×2732. iPhone screenshots cannot be reused there, and tablet layouts usually need their own composition. The [screenshot checklist before submitting](/blog/store-screenshot-checklist-before-submit) covers these device requirements alongside copy and localization checks. ### In-app purchase review screenshots and other uploads that fail In-app purchases and subscriptions have their own review screenshot field, separate from your product page screenshots. It is only seen by App Review, but it still has to meet Apple’s image requirements. The safest approach is to use an unedited device or Simulator capture of the purchase screen, saved as PNG or JPEG without transparency, and check App Store Connect Help for the current requirement if it is rejected. Custom product pages and Product Page Optimization treatments use the same screenshot slots and size rules as your main product page. If a set passes on the default page, the same files will pass there too. ### Prevent the error: build exact sizes into your export The long-term fix is to stop producing screenshots at arbitrary sizes. Set up your design file with canvases at exact pixel sizes (or point frames with a locked 3x export), keep a separate preset for iPad if you need it, and run the sips check as part of your release checklist. If you would rather not manage export settings at all, [StoreShots AI](/app-store-screenshot-generator) exports App Store iPhone screenshots as PNGs at exactly 1290×2796 with no alpha, ready for the 6.9-inch slot, from the real app screenshots you upload. It does not generate iPad screenshots or app preview videos, so iPad apps still need a separate tablet set. You can see finished packs on the [sample page](/sample) and compare credit packs on [pricing](/pricing). Once the sizes are right, spend your time on what actually moves installs: the [order of your screenshots](/blog/app-store-screenshot-order-that-converts) and the headline on each slide. [Export exact 1290×2796 App Store screenshots](https://storeshotsai.com/app-store-screenshot-generator) #### Why does App Store Connect say the dimensions of one or more screenshots are wrong? At least one file’s exact pixel size does not match the accepted sizes for the slot you uploaded to. Common reasons are using a 6.5-inch file in the 6.9-inch slot, an export that is one pixel off, the wrong export scale in Figma, or swapped width and height. Check every file with Preview’s Inspector or sips before re-uploading. #### What size should App Store screenshots be in 2026? For iPhone, use a 6.9-inch size: 1320×2868, 1290×2796 or 1260×2736 pixels in portrait. The 6.5-inch slot accepts 1284×2778 or 1242×2688, and iPad apps need a 13-inch set at 2064×2752 or 2048×2732. Apple updates these specifications, so confirm in App Store Connect Help before you export a new set. #### Can App Store screenshots have a transparent background? No, App Store screenshots must not contain transparency or an alpha channel. Flatten the image onto a solid background and export it as PNG without alpha, or convert it to JPEG with sips -s format jpeg. Rounded device frames on a transparent canvas are the most common way an alpha channel slips into an otherwise correct file. #### How do I check a screenshot’s pixel dimensions on a Mac? Open the image in Preview and choose Tools > Show Inspector to see its pixel width and height. For a whole folder, run sips -g pixelWidth -g pixelHeight *.png in Terminal, and add sips -g hasAlpha *.png to find files that still contain an alpha channel. Both tools are built into macOS, so no extra software is needed. #### Can I upload 6.5-inch screenshots to the 6.9-inch slot? No, 6.5-inch sizes such as 1284×2778 are only accepted in the 6.5-inch slot. Upload them there, or re-export your designs at a 6.9-inch size like 1290×2796. Avoid stretching one to the other, because the aspect ratios differ slightly and your UI and text will look distorted on the product page. #### Does StoreShots AI export screenshots at the right size for App Store Connect? Yes, StoreShots AI exports App Store iPhone screenshots as 1290×2796 PNGs without transparency, which fit the 6.9-inch slot. It builds them from real app screenshots you upload and delivers a ZIP. It does not create iPad screenshots or app preview videos, so apps that support iPad still need a separate 13-inch set. Sources: - [Screenshot specifications](https://developer.apple.com/help/app-store-connect/reference/screenshot-specifications) — Apple App Store Connect Help - [App Store product page](https://developer.apple.com/app-store/product-page/) — Apple Developer - [Product Page Optimization](https://developer.apple.com/app-store/product-page-optimization/) — Apple Developer ### How to Make App Store Screenshots: Step-by-Step (2026) URL: https://storeshotsai.com/blog/how-to-make-app-store-screenshots · Updated: 2026-11-10 · Author: StoreShots AI Editorial How to make App Store screenshots step by step: pick sizes, capture clean screens, plan the story, design, export and upload a set that wins more installs. To make App Store screenshots, capture clean screens from your app at a 6.9-inch iPhone size such as 1290×2796, plan a 5–8 slide story that leads with your strongest benefit, add a short headline to each slide, place the screens on a consistent background, then export PNGs without transparency and upload them in App Store Connect. That is the whole process in one sentence. The rest of this tutorial breaks it into eight practical steps, with the exact Simulator commands for clean captures, a slide-planning template, headline rules, and an honest comparison of the three ways to produce the final images: designing by hand, using templates, or using an AI generator. It is written for indie developers and small launch teams who want a professional set without a dedicated designer. ### Step 1: Decide which App Store screenshot sizes you need Before you open a design tool, decide which device slots you will fill. Most iPhone-only apps need just one set at a 6.9-inch size, because Apple can scale your largest iPhone set down for smaller displays. If your app runs on iPad, you also need a 13-inch iPad set. App Store Connect shows which slots are required for your app, and Apple updates the specifications as new devices ship, so confirm there before exporting. - 6.9-inch iPhone (portrait): 1320×2868, 1290×2796 or 1260×2736 px - 6.5-inch iPhone (portrait): 1284×2778 or 1242×2688 px - 13-inch iPad (portrait): 2064×2752 or 2048×2732 px, required if your app runs on iPad - Up to 10 screenshots per device size per localization - PNG or JPEG, RGB, no transparency or alpha channel - The first few screenshots show in search results, so they carry most of the weight ### Step 2: Capture clean, real screens from your app Your screenshots should show your real app, not a mock-up of features that do not exist yet. Apple’s guidelines expect screenshots to reflect the app experience, and real UI builds trust with people deciding whether to download. The iOS Simulator is the easiest way to get captures at native resolution. Boot a large iPhone simulator (a current Pro Max or Plus model captures at one of the accepted 6.9-inch sizes), then clean up the status bar so every screenshot shows the same time, full battery and full signal: xcrun simctl status_bar booted override --time 9:41 --batteryLevel 100 --cellularBars 4. Capture each screen with xcrun simctl io booted screenshot home.png, changing the filename each time. When you are done, xcrun simctl status_bar booted clear restores the normal status bar. Avoid grabbing the Simulator window with a system screenshot shortcut: that captures the window at your display’s scale, often with the bezel, instead of the device’s native pixels. If you capture on a physical iPhone instead, tidy the status bar by hand (charged battery, Wi-Fi on, no notifications). - Fill every screen with realistic, friendly demo data, not lorem ipsum or test accounts - Hide debug banners, feature flags and developer menus - Use the same appearance (light or dark) across the whole set unless contrast is the point - Capture more screens than you need, then pick the strongest 5–8 - Check sizes afterwards with sips -g pixelWidth -g pixelHeight *.png on a Mac ### Step 3: Plan a 5–8 slide screenshot story People skim screenshots in a couple of seconds, often seeing only the first two or three in search results. Treat the set as a story with a clear order rather than a tour of every tab. A simple structure that works for most apps: 1. Slide 1, the hook: your single biggest benefit and the screen that proves it. 2. Slide 2, the core action: what users do most often, shown in progress. 3. Slides 3–5, supporting features: one feature per slide, each tied to an outcome. 4. Slide 6, trust or differentiation: privacy, offline use, sync, or what makes you different. 5. Slides 7–8, optional extras: customization, widgets, integrations or a closing call to action. ### Step 4: Write a headline for every slide Headlines do most of the selling. Each one should state a single benefit in a few words, readable at thumbnail size. Lead with the outcome the user gets, not the feature name: for example, a budgeting app might write “See where every dollar goes” rather than “Category analytics.” Keep headlines short enough to sit on two lines, use the same tone across the set, and make sure the screen underneath actually shows what the headline promises. Optional subtext can add one supporting detail. For formulas and before-and-after examples, see our guide on [how to write App Store screenshot copy](/blog/how-to-write-app-store-screenshot-copy). ### Step 5: Design the slides: frames, backgrounds and type Good App Store screenshot design is mostly consistency. Pick one layout system and repeat it: headline at the top, the app screen below it, the same margins on every slide. - **Device frames:** optional. A frame makes the image read as a phone at small sizes; a frameless, slightly enlarged screen gives more room to the UI. Choose one approach and keep it. - **Backgrounds:** use your brand colors or a soft gradient that contrasts with your UI. Avoid busy photos behind text. - **Typography:** one bold, highly legible typeface for headlines and a lighter weight for subtext. Large sizes, high contrast. - **Safe margins:** keep text away from the edges and corners so nothing feels cramped when Apple shows the image with rounded corners. - **Continuity:** panoramic backgrounds that flow across slides can encourage swiping, but every slide must still make sense on its own. - **Transparency:** export on a solid background. Transparent corners around a device frame are a common cause of upload errors. ### Three ways to make App Store screenshots, compared honestly **By hand in Figma or Canva.** You get full creative control and can match an existing brand system exactly. The trade-off is effort: you set up exact canvas sizes, export at the right scale (a 430×932 point frame needs a 3x export to reach 1290×2796), and redo every slide by hand whenever the UI, copy or language changes. It suits teams with design skills and time, or apps with a strict brand guide. **Template tools.** A screenshot template gives you a ready layout and handles device frames and sizes, which is faster than starting from a blank canvas. You still write every headline yourself, and because many apps use the same templates, results can look generic unless you customize colors and type. **An AI generator.** An [app store screenshot maker](/app-store-screenshot-generator) like StoreShots AI takes 3–10 real screenshots of your app, suggests a purpose, headline, subtext and visual theme for each one, shows a preview hero frame, then generates the full pack. You revise individual slides in chat and download a ZIP of 1290×2796 PNGs. Your uploaded UI stays the source, so it does not redraw your app. It is usually the fastest route to a finished first set; you trade some fine-grained control for speed, and it does not produce iPad screenshots or app preview videos, so iPad apps still need a separate tablet set. Many teams combine routes: generate a strong first draft with AI, then fine-tune a slide by hand if the brand demands it. For a deeper look at the trade-offs, read [AI app screenshot generator vs designers](/blog/ai-app-screenshot-generator-vs-designers) or browse finished [sample packs](/sample). [Make your App Store screenshots](https://storeshotsai.com/app-store-screenshot-generator) ### Step 6: Export and QA before you upload A five-minute check here saves a rejected upload and a resubmission later. Run through this list with the final files, not the design file. - Every file is an accepted size for its slot (for example exactly 1290×2796) - PNG or JPEG, RGB, no alpha channel (sips -g hasAlpha *.png shows true or false) - Files are numbered in the order you want them to appear - Headlines are legible when the image is viewed at thumbnail size on a phone - No typos, placeholder text, real customer data or prices that may change - The UI shown matches the build you are submitting - Localized sets have translated headlines that fit without truncation ### Step 7: Upload your screenshots to App Store Connect In App Store Connect, open your app, select the iOS version you are preparing, and scroll to Previews and Screenshots. Choose the device tab (iPhone 6.9-inch first, then iPad if required), drag in your files, and drag thumbnails to reorder them. Repeat for each localization you support. If you see “The dimensions of one or more screenshots are wrong,” a file does not match the slot’s accepted sizes or contains transparency. Our [guide to fixing the wrong dimensions error](/blog/fix-app-store-screenshot-wrong-dimensions-error) walks through every cause. Screenshots are tied to an app version, so plan to update them alongside a release, and use [the full pre-submit checklist](/blog/store-screenshot-checklist-before-submit) before you hit submit. ### Step 8: Iterate with tests and custom product pages Your first set is a hypothesis. Apple’s Product Page Optimization lets you test up to three alternative treatments of your icon, screenshots and app previews against your original product page, with tests running for up to 90 days. Change one meaningful thing at a time, such as the first slide’s headline or the screen you lead with, so you can tell what made the difference. Custom product pages let you build alternative versions of your product page with different screenshots for specific audiences or ad campaigns; check Apple’s current limit on how many you can create. Each page reuses the same size rules, so a well-organized source file makes variants quick to produce. With StoreShots, re-exporting work you have already generated is free, and credits never expire, which suits this kind of gradual iteration. Our [A/B testing guide for App Store screenshots](/blog/app-store-screenshot-ab-testing-guide) covers test design in more detail. #### How do I make App Store screenshots? Capture clean screens from your app, plan a 5–8 slide story, add a short benefit headline to each slide, and place the screens on a consistent background. Export PNGs at an accepted size such as 1290×2796 without transparency, then upload them in App Store Connect under Previews and Screenshots for each device size and localization. #### What size should I make App Store screenshots? Make iPhone screenshots at a 6.9-inch size: 1320×2868, 1290×2796 or 1260×2736 pixels in portrait. Apple can scale that set down for smaller iPhones. If your app runs on iPad, you also need a 13-inch iPad set at 2064×2752 or 2048×2732. Confirm the current list in App Store Connect Help before exporting. #### How many App Store screenshots should I upload? Upload between 5 and 8 screenshots for most apps, even though Apple allows up to 10 per device size per localization. The first few appear in search results and do most of the work, so put your strongest benefit first. Extra slides only help if each one shows a distinct, meaningful feature. #### How do I get a clean 9:41 status bar in Simulator screenshots? Run xcrun simctl status_bar booted override --time 9:41 --batteryLevel 100 --cellularBars 4 before capturing. Then take each screenshot with xcrun simctl io booted screenshot filename.png, which saves at the device’s native resolution. When you are finished, run xcrun simctl status_bar booted clear to restore the normal status bar. #### Can I make App Store screenshots without a designer? Yes, many indie developers make their own App Store screenshots with Figma or Canva, a template tool, or an AI generator. The key skills are choosing the right screens, writing short benefit headlines and keeping layout consistent. An AI app store screenshot maker can draft headlines and layouts for you, which you then review and refine. #### Does StoreShots AI make iPad App Store screenshots? No, StoreShots AI exports iPhone App Store screenshots at 1290×2796 and Google Play phone screenshots at 1080×1920, but not iPad sets. It builds them from 3–10 real app screenshots you upload and lets you revise individual slides in chat. If your app supports iPad, plan a separate 13-inch iPad set with another tool. Sources: - [Screenshot specifications](https://developer.apple.com/help/app-store-connect/reference/screenshot-specifications) — Apple App Store Connect Help - [App Store product page](https://developer.apple.com/app-store/product-page/) — Apple Developer - [Product Page Optimization](https://developer.apple.com/app-store/product-page-optimization/) — Apple Developer - [Custom product pages](https://developer.apple.com/app-store/custom-product-pages/) — Apple Developer ### App Store Screenshot Examples: 12 Reusable Patterns URL: https://storeshotsai.com/blog/app-store-screenshot-examples-patterns · Updated: 2026-11-10 · Author: StoreShots AI Editorial App store screenshot examples as 12 reusable patterns, with when each works, which app categories suit it and the pitfalls, so you can plan a set that converts. The most useful app store screenshot examples are not individual listings to copy but reusable patterns: an outcome headline over a hero screen, a before/after slide, a panoramic background, a feature grid closer. Pick two or three patterns that fit your category, apply them to your real app UI, and keep one message per slide. Copying another app's screenshots rarely works, because their layout was built around their UI, their audience and their brand. Patterns transfer. Below are 12 patterns with what each is, when it works, which kinds of apps suit it and where it goes wrong. The category examples are hypothetical illustrations, not descriptions of real listings. ### 12 app store screenshot patterns at a glance Use this list as a menu. Most strong sets combine one opening pattern, one or two story patterns and one closing pattern. - Outcome headline + hero screen: the result the user gets, over the screen that delivers it. - Single-feature zoom: one UI element enlarged with a callout. - Mascot-led slide: a character introduces or reacts to the app. - Panoramic connected background: one continuous image spanning several slides. - Onboarding-to-result story: slides follow the user path from start to payoff. - Before/after: the messy state next to the organized state. - Comparison to the manual way: the old method versus your app. - Social proof slide: real ratings, press or usage data, only if verifiable. - Persona slide: a slide speaking to one specific user type. - Localized headline: copy rewritten for a market, not just translated. - Dark-mode showcase: a slide that shows the app in its dark appearance. - Feature grid closer: a final slide summarizing secondary features. ### Opening patterns: winning the first slide **1. Outcome headline + hero screen.** A short headline states the result (“Know where every dollar went”) above the single app screen that delivers it. It works for almost any app whose value can be shown on one screen, and it is the safest default first slide. A budgeting app might pair the headline with its monthly overview. Pitfall: writing a feature label (“Smart categories”) instead of an outcome, or choosing a busy screen that is unreadable at thumbnail size. Our guide to [writing App Store screenshot copy](/blog/how-to-write-app-store-screenshot-copy) covers outcome wording. **2. Single-feature zoom (callout).** One UI element, such as a chart, a button or a timer, is enlarged beyond the device frame with an arrow or highlight. It works when your differentiator is a small detail that disappears at full-screen scale. A sleep app might zoom into its sleep-stage graph. Pitfall: zooming so far that the element loses context, or blurring it by upscaling a low-resolution capture. **3. Mascot-led slide.** A character greets the visitor, points at the UI or reacts to progress. It works for apps with a playful, consistent brand voice, such as kids' learning, habit building or casual games. Pitfall: a mascot that covers the UI or appears only once, which reads as decoration rather than identity. If you do not have one yet, the [AI mascot generator](/ai-mascot-generator) can create a consistent character to use across slides. ### Story patterns: connecting slides into a sequence **4. Panoramic connected background.** One continuous illustration or gradient runs across several slides, so the set reads as a single strip when scrolled. It works well for design-led brands and for nudging visitors to swipe. A travel planner might run a route line across three slides. Pitfall: key elements landing on slide edges, and the set falling apart when you later reorder or test individual slides. **5. Onboarding-to-result story.** Slides follow the real user path: set a goal, take the core action, see the result. It suits apps with a clear flow, such as a language app moving from picking a level to finishing a lesson to seeing a streak. Pitfall: spending the opening slides on setup screens nobody cares about; lead with the result and tell the story after. **6. Before/after.** A messy or painful state sits next to the organized result, either split on one slide or across two. It works for organizers, photo editors, scanners and cleanup utilities. A receipt scanner might show a crumpled receipt beside a tidy expense entry. Pitfall: an exaggerated “after” that your app cannot actually produce, which invites bad reviews. **7. Comparison to the manual way.** The slide contrasts the old method (spreadsheets, paper notes, five separate apps) with your app doing it in one place. It works when your audience already solves the problem manually. A shift-scheduling app might contrast a group chat thread with its schedule view. Pitfall: naming or depicting competitor products; compare against a method, not a brand. ### Trust and audience patterns: who it is for and why to believe it **8. Social proof slide (only with real data).** A slide shows a verifiable rating, a real press mention or genuine usage numbers. It works once you actually have that evidence. Pitfall: invented or unverifiable claims. Store policies restrict misleading metadata, and Google Play guidance discourages ranking-style claims such as “#1” or “best” in graphics, so check current policy and keep receipts for anything you state. **9. Persona slide.** One slide speaks to a specific user: “For freelancers who invoice on the go.” It works for apps with two or three distinct audiences, such as a note app serving students and researchers. Pitfall: listing so many personas that the set no longer says who the app is for. Persona slides also make good custom product page variants. **10. Localized headline.** The headline is rewritten for a market's phrasing and priorities instead of translated word for word, while the UI capture is in the same language. It works for any app with meaningful non-English traffic. Pitfall: shipping translated headlines over English UI, or text that overflows in longer languages. See [localizing App Store screenshots](/blog/localize-app-store-screenshots) for the workflow. ### Closing and showcase patterns: finishing the set **11. Dark-mode showcase.** One slide shows the app in its dark appearance, often with a darker background. It works for apps used at night or for long sessions, such as readers, developer tools, sleep or focus apps. Pitfall: using it as an early slide when most users will see the light theme, or dark slides that turn muddy next to light ones. **12. Feature grid closer.** The final slide lists four to six secondary features with icons or small crops. It works for apps with breadth, such as utilities and productivity suites, catching visitors who scroll to the end. Pitfall: leading with a grid. Grids are scannable but rarely persuasive, so they belong at the end. [Build a screenshot set from your real app](https://storeshotsai.com/login?next=%2Fdashboard) ### Which screenshot patterns fit your app category? Category shapes expectations. These pairings are starting points, not rules; your own audience research and testing should override them. - Fitness: outcome headline over a progress screen, onboarding-to-result story, dark-mode showcase for workout timers. - Finance: outcome headline, before/after (scattered accounts to one overview), comparison to spreadsheets; social proof only if verifiable. - Productivity: single-feature zoom on the core interaction, comparison to the manual way, feature grid closer. - Games: panoramic connected background, mascot-led slides, clear gameplay moments in place of UI explanation. - Education: mascot-led opener, onboarding-to-result story (level to lesson to streak), persona slides for learners and parents. - Utilities: before/after, single-feature zoom, feature grid closer for breadth. ### How to combine patterns into a 6–8 slide set A pattern only works in context. Plan the whole sequence before designing a single slide; [the screenshot order that converts](/blog/app-store-screenshot-order-that-converts) goes deeper on slide positions. 1. Pick one opening pattern for slide one: usually outcome headline + hero screen. 2. Use slides two and three for your strongest differentiator, often a zoom or before/after. 3. Add one story or trust pattern in the middle: onboarding-to-result, persona or real social proof. 4. Add a dark-mode or localized variant only where it serves your audience. 5. Close with a feature grid if the app has breadth worth summarizing. 6. Check every slide at thumbnail size and remove any second message. ### Mistakes that break any screenshot pattern Patterns fail in predictable ways, and usually not because the pattern was wrong. Most broken sets share the same handful of execution problems, regardless of category. Run through this checklist before you export, and again whenever you add a slide or a new localization. The common thread is respect for the visitor's attention. Someone scrolling search results gives your listing a second or two, often at thumbnail size, before deciding whether to open the product page. A pattern earns its place only if it makes the message faster to understand at that size. - Two messages on one slide: a headline and a subhead that each make a different claim. - Headlines too small to read in search results, especially on slides one to three. - Mixing three or more background styles so the set looks like several apps. - Mockup UI that does not match the shipped app, which sets up disappointment after install. - Stretching one export to fit both stores instead of producing native 1290×2796 and 1080×1920 files. - Claims you cannot back up, including ratings, user counts or “award-winning” labels. - Ignoring dark or light context: a dark slide among light ones should look deliberate, not accidental. ### Generated examples: StoreShots sample packs If you want to see several of these patterns applied to complete sets, browse the [StoreShots sample packs](/sample). They are generated demonstrations of the workflow, not customer case studies, and they show how outcome headlines, themes and slide order come together at export size. To build your own, StoreShots takes 3–10 real screenshots from your app, maps each screen to a purpose, headline, subtext and visual theme, and exports App Store iPhone PNGs at 1290×2796 and Google Play phone PNGs at 1080×1920. Your uploaded UI stays the source; it does not redraw your app. It does not create iPad sets or Play feature graphics, so plan those separately. When you are unsure which pattern to lead with, test it: our [app store screenshot A/B testing guide](/blog/app-store-screenshot-ab-testing-guide) shows how to run patterns against each other. #### What are the best app store screenshot examples to follow? The best examples to follow are patterns, not specific listings. Outcome headline over a hero screen, single-feature zoom, before/after and a feature grid closer adapt to most apps. Apply them to your own real UI and audience instead of copying another app's layout, which was designed around different screens. #### What should the first app store screenshot show? The first screenshot should show the main outcome your app delivers, on the screen that delivers it. A short outcome headline plus one readable hero screen is the safest default, because the first slides appear in search results and must make sense at thumbnail size. #### How many patterns should one screenshot set use? Most strong sets use three or four patterns across six to eight slides. Typically that is one opening pattern, one or two story or trust patterns in the middle and a closing pattern. Using more makes the set feel inconsistent, and each slide should still carry only one message. #### Are panoramic connected backgrounds worth the effort? Panoramic backgrounds are worth it for design-led brands and games, but they add maintenance cost. They encourage swiping and look cohesive, yet any reorder, localization or A/B test can break the continuity. Keep key elements away from slide edges so individual slides still work alone. #### Can I put ratings or awards in my screenshots? Only if the claim is real, current and verifiable. Store policies restrict misleading metadata, and Google Play guidance discourages ranking-style claims such as “#1” or “best” in graphics. Check the current Apple and Google policies, and avoid invented numbers or testimonials entirely. #### Are the StoreShots sample packs real customer screenshots? No, the StoreShots sample packs are generated demonstrations of the workflow, not customer case studies. They show how patterns like outcome headlines and consistent visual themes look in complete, export-sized sets. Your own pack is built from the real screenshots you upload. Sources: - [Screenshot specifications](https://developer.apple.com/help/app-store-connect/reference/screenshot-specifications) — Apple App Store Connect Help - [App Store product page](https://developer.apple.com/app-store/product-page/) — Apple Developer - [Add preview assets: screenshots and graphics](https://support.google.com/googleplay/android-developer/answer/9866151?hl=en) — Google Play Console Help ### How to Write App Store Screenshot Copy (40+ Examples) URL: https://storeshotsai.com/blog/how-to-write-app-store-screenshot-copy · Updated: 2026-11-10 · Author: StoreShots AI Editorial Write app store screenshot copy that converts: headline formulas, 3–7 word length rules, 48 caption examples, and rewrites that make every slide clear. Good App Store screenshot copy is a short headline, usually 3–7 words, that states one benefit per slide and matches the UI shown beneath it. Lead with a verb or outcome, keep it legible at thumbnail size, add optional subtext only when it adds proof, and order slides so the first three tell the core story. Screenshot captions are billboard copy, not body text. Most people decide from the first few slides in search results or a quick swipe on your product page, so every word has to earn its place. This guide gives you headline formulas, length rules, 48 illustrative caption examples by category, a slide-by-slide narrative, keyword and localization notes, and before/after rewrites you can apply to your own [App Store screenshots](/app-store-screenshot-generator) today. ### How long should App Store screenshot captions be? Aim for roughly 3–7 words in the headline. That is not an Apple rule; it is a legibility rule. In search results your screenshot is rendered at a fraction of its 1290×2796 export size, and a seven-word headline set large enough to read at that scale already fills two lines on a portrait slide. Past that, type has to shrink and the caption turns into texture. A practical test: export the slide, scale it to about 20% on your monitor (roughly the size of a search-result thumbnail on a phone), and read it from arm's length. If you squint, cut words or increase the type size. Do the test on a real phone too, because contrast and font weight behave differently on a bright OLED screen than on a desktop monitor. For more on type scale and contrast, see our [app screenshot design best practices](/blog/app-screenshot-design-best-practices). - Headline: about 3–7 words, one or two lines, one idea - Subtext: optional, about 6–12 words, one line where possible - One benefit per slide; never stack two claims with an ampersand - Front-load the meaning: the first two or three words should carry the benefit - Apple accepts up to 10 screenshots per device size per localization; Google Play accepts 2–8 phone screenshots - Only the first few slides show in App Store search results, so slides 1–3 carry most of the message - Legibility check: readable at roughly 20% scale on a phone held at arm's length ### Which headline formulas work for screenshot captions? Formulas are scaffolding, not scripts. Use them to get a first draft quickly, then rewrite until the headline sounds like your product and describes exactly what the screen below it shows. Four formulas cover most slides. Verb + outcome is the default because it describes a result the user gets, not a feature you built. Number + benefit works when you have a real, defensible number about the product itself (steps, minutes, categories), never an invented usage statistic. Problem → solution names a pain your audience recognises and resolves it in the same line. "Without X" removes the objection that stops people installing, such as spreadsheets, sign-up walls or ads, but only use it if the claim is true for the app as shipped. - Verb + outcome: "Track every expense automatically" / "Plan trips in minutes" - Number + benefit: "3 taps to log a workout" / "Every bill in one view" (use only numbers you can prove) - Problem → solution: "Forgot a bill? Get reminded first" / "Messy notes, instantly organized" - "Without X": "Budget without spreadsheets" / "Meditate without the jargon" - Bonus, possessive framing: "Your week, finally planned" works well for hero slides ### Screenshot headline examples by category (48 illustrative captions) The examples below are illustrative drafts written for hypothetical apps, not copy taken from real listings. Use them to see the formulas in action, then replace generic nouns with the specific thing your screen shows. A caption only works if the UI underneath proves it. - Finance: "Track spending in one tap" · "See where your money goes" · "Budget without spreadsheets" · "Every account in one view" · "Never miss a bill again" · "Save automatically each payday" - Fitness: "Log a workout in seconds" · "Your plan adapts as you improve" · "Train at home, no equipment" · "See your progress every week" · "Short workouts that fit lunch" · "Stay on track with streaks" - Productivity: "Plan your week in minutes" · "Turn notes into tasks" · "Focus on what matters today" · "Every project, one calm board" · "Capture ideas before they vanish" · "Meetings, summarized for you" - Education: "Learn Spanish in 10-minute lessons" · "Practice speaking out loud" · "Flashcards that know what you forget" · "Study offline, anywhere" · "Track every subject's progress" · "Explanations, step by step" - Travel: "Plan trips in minutes" · "Your itinerary, always offline" · "Every booking in one place" · "Find hidden local spots" · "Split trip costs without awkwardness" · "Packing lists that build themselves" - Wellness: "Wind down in five minutes" · "Meditate without the jargon" · "Sleep sounds for every night" · "Notice your mood patterns" · "Breathe through stressful moments" · "A gentle daily check-in" - Utilities: "Scan documents to clean PDFs" · "Free up storage in one tap" · "Find any file instantly" · "Convert units without ads" · "Back up photos automatically" · "Your passwords, safely in one place" - Games: "Build your kingdom, brick by brick" · "Play daily puzzles in minutes" · "Challenge friends in real time" · "Unlock 12 unique worlds" · "Collect, upgrade, and battle" · "Relax with no timers" ### How to write subtext that supports the headline Subtext is optional. Many strong sets use headlines only. Add a second line when it supplies something the headline cannot: a concrete detail, a qualifier that keeps the claim honest, or proof the screen does what the headline says. If the subtext merely restates the headline in more words, delete it. Set subtext noticeably smaller and lighter than the headline so the hierarchy reads instantly, and never let it carry the main benefit. People scanning thumbnails will read the headline and skip everything else. - Keep it to one line where possible, roughly 6–12 words - Add specificity: "Syncs with your bank in under a minute" under "Every account in one view" - Add honesty: qualifiers like "on supported devices" or "with Pro" belong here, not in fine print - Do not repeat the headline's verb or noun - No feature lists separated by commas; that is a description, not a caption - Never place subtext over busy UI where it loses contrast ### Slide-by-slide narrative: what each caption should do A screenshot set is a sequence, not a gallery. Each caption should advance one story: what the app does for me, how it works, why it is better, and why I can trust it. The first three slides do most of the work because they are the ones visible without scrolling in many App Store search layouts, so put your strongest benefit first. Our guide to [screenshot order that converts](/blog/app-store-screenshot-order-that-converts) goes deeper on sequencing. If you have more than five slides, keep extending the pattern with secondary features ranked by how often users ask for them. Weak slides at positions 8–10 rarely hurt, but weak slides at positions 1–3 cost installs. 1. Hero: the primary outcome in one line ("Track spending in one tap"), over your best screen 2. Core action: show the main workflow and name the result ("Log any expense in seconds") 3. Differentiator: the feature competitors lack or do worse ("Bills sorted before they're due") 4. Depth: a secondary feature users value ("Shared budgets for couples") 5. Trust or reassurance: privacy, offline access, ratings or awards you can verify, never invented numbers 6. Close: what happens next or who it is for ("Built for freelancers with irregular income") [Draft captions from your real screens](https://storeshotsai.com/login?next=%2Fdashboard) ### Do keywords in screenshot captions help ASO? Possibly, but treat it as a secondary effect. Apple has said screenshot captions can help the App Store understand your app, which implies it can read text from your screenshots. Apple has not published how, or how much, caption text affects ranking. Your title, subtitle and keyword field remain the documented places for search terms. The safe approach: write for people first, and where it is natural, use the same words your audience searches for. If users search "budget planner", a caption like "Your budget planner, finally simple" serves both readers. Never keyword-stuff. A caption such as "Budget Tracker Expense App Money Manager" is unreadable, looks spammy next to competitors, and risks review issues under Apple's metadata guidelines. On Google Play, screenshots are not a documented ranking input; your title and descriptions are. See the [ASO topic hub](/topics/aso) for the wider keyword picture. ### How to localize App Store screenshot copy Translate meaning, not words. A punchy English verb + outcome headline can become long or awkward when translated literally. Give translators the intent of each slide ("hero: saves time on budgeting") and the character budget, and let them write a native headline rather than a word-for-word copy. Plan for text expansion: German and French often run longer than English, while Japanese and Chinese are shorter but may need larger type for legibility. Leave room in the layout instead of shrinking the font per locale. Our [screenshot localization guide](/blog/localize-app-store-screenshots) covers prioritising markets and keeping visuals consistent. - Localize screenshots that show UI text, not only the captions, so the app and headline match - Re-check line breaks in every locale; awkward breaks are the most common localization bug - Adapt examples: currency, date formats, names and units in demo data - Avoid idioms and wordplay that do not survive translation - Have a native speaker read the final exported slides, not just the spreadsheet ### Before and after: screenshot caption rewrites Most weak captions fail in one of a few predictable ways: they name a feature instead of a benefit, they are too long to read at thumbnail size, or they promise something the screen does not show. These hypothetical rewrites show the fix pattern. - Before: "Dashboard" → After: "See your whole month at a glance" (feature label to outcome) - Before: "Powerful AI-driven task management platform" → After: "Turn notes into tasks" (jargon to a concrete action) - Before: "Track workouts, meals, sleep, water and more" → After: "Log a workout in seconds" (list to one idea) - Before: "The best meditation app" → After: "Wind down in five minutes" (unprovable claim to specific benefit) - Before: "Welcome to TripPlanner" → After: "Plan trips in minutes" (app name to promise) - Before: "Don't waste money on subscriptions you forget" → After: "Spot forgotten subscriptions" (long negative to short positive) - Before: "Expense Budget Money Tracker App" → After: "Budget without spreadsheets" (keyword stuffing to human copy) ### Common App Store screenshot copy mistakes Run your draft set past this list before you export. Most of these are fast to fix and visible the moment you look at the slides at search-result size. - Repeating the app name on every slide; your icon and title already say it - Generic feature labels ("Settings", "Profile", "Dashboard") instead of benefits - Captions that do not match the UI beneath them, which breaks trust instantly - Two ideas per headline joined with "and" or an ampersand - Tiny type that disappears on a phone in search results - Invented statistics or "#1" claims you cannot back up - Mentioning prices or promotions that will go stale or differ by region - Inconsistent tone: playful on slide 1, corporate on slide 4 - Copy written once in English and pasted into every locale unchanged ### How StoreShots drafts screenshot headlines from your real screens Writing captions is faster when you start from a draft grounded in what your app actually shows. In [StoreShots AI](/how-it-works), you upload 3–10 real screenshots from one app. The AI maps each screen to a purpose in the narrative (hero, core action, differentiator and so on), then drafts a headline, subtext and visual theme for each. Your uploaded UI stays the source; it does not redraw your app. You preview a hero frame first, generate the full pack, and then edit: rewrite any headline yourself or chat-revise a single slide ("make this shorter", "lead with the offline benefit"). Treat the AI copy as a first draft and apply the rules above before you export. Exports are App Store iPhone PNGs at 1290×2796 and Google Play phone PNGs at 1080×1920, delivered as a ZIP. StoreShots does not produce iPad screenshots, Play feature graphics or app preview videos, so plan those separately. Pricing is one-time credit packs with no subscription; see [pricing](/pricing) or browse a sample pack first. #### How many words should an App Store screenshot headline have? Aim for roughly 3–7 words. That keeps the headline to one or two lines at a type size that stays readable when the screenshot is shown as a small thumbnail in search results. If you need more words, the slide is probably trying to say two things. #### Should every App Store screenshot have a caption? Most screenshots benefit from a short caption that explains the benefit of the screen shown. Games with strong visual art sometimes use fewer captions, but for utility, finance, health and productivity apps, uncaptioned UI rarely explains itself at thumbnail size. #### Do screenshot captions affect App Store search ranking? Apple has said screenshot captions can help the App Store understand your app, but it has not published how much they affect ranking. Write for people first, use natural search terms where they fit, and keep keywords in your title, subtitle and keyword field. #### What is the best headline formula for the first screenshot? Verb + outcome is the most reliable formula for the hero slide. It states the main result the user gets, such as "Plan your week in minutes", and pairs naturally with your strongest screen. Test alternatives with Apple's Product Page Optimization once you have traffic. #### Should I translate screenshot copy word for word? No, localize the meaning instead of translating literally. Give translators each slide's intent and a length budget so they can write a native headline, then check line breaks and demo data in the exported slides for every locale before you upload. #### Can AI write App Store screenshot copy? Yes, AI can produce useful first drafts, especially when it works from your real screens. StoreShots AI drafts a headline and subtext per uploaded screen; you should still edit each one for accuracy, tone and length before exporting your final set. Sources: - [Screenshot specifications](https://developer.apple.com/help/app-store-connect/reference/screenshot-specifications) — Apple App Store Connect Help - [App Store product page](https://developer.apple.com/app-store/product-page/) — Apple Developer - [Product Page Optimization](https://developer.apple.com/app-store/product-page-optimization/) — Apple Developer - [App Review Guidelines](https://developer.apple.com/app-store/review/guidelines/) — Apple Developer ### AI Screenshot Workflow: Real Captures to a Store ZIP URL: https://storeshotsai.com/blog/ai-app-screenshot-workflow · Updated: 2026-11-10 · Author: StoreShots AI Editorial Honest AI app screenshot generator workflow: prep real captures, preview, generate, review, revise and export, with credit math so you ship store sets faster. To generate App Store screenshots with AI, upload 3–10 real captures from one app, let the AI map each screen to a purpose, headline, and theme, preview the hero frame, generate the full set, revise individual slides by chat, and export a ZIP at 1290×2796 for iPhone or 1080×1920 for Google Play. That is the short version. The longer version is about the decisions around each step: which captures to feed in, what to check before you pay for a full set, where the AI is reliably good, and where a human still has to own the result. This guide walks through the whole AI app screenshot generator workflow using StoreShots AI, including a worked example with honest credit math. ### Step 1: Prepare inputs the AI can actually use Output quality is capped by input quality. The AI does not redraw your interface; your uploaded UI stays the source and is placed into frames and layouts. So a cluttered capture produces a cluttered slide, however good the headline is. Collect 3–10 clean screenshots from one app and one platform. Use realistic demo data (believable names, plausible balances, no lorem ipsum), hide debug banners, and clear notification clutter from the status bar. Capture the screens that prove your core outcome rather than every screen you have. If you need help choosing them, [how to make App Store screenshots](/blog/how-to-make-app-store-screenshots) covers capture planning in depth. - 3–10 real captures from the same app and platform build - A one-paragraph app description: what it does and for whom - Target audience in plain words (e.g. freelancers paid irregularly) - Tone: calm, playful, premium, direct, or similar - Any claims you can and cannot make (e.g. no 'bank-level security' unless true) ### Step 2: What the AI does with your captures Once uploaded, the AI does the planning work a designer or marketer would usually do in a first pass. It reads each capture, decides what job that screen should do in the set (hero outcome, proof, feature depth, trust), drafts a headline and subtext for it, and picks a visual theme that suits your app's colours and category. Read this plan as a draft brief, not a finished answer. The most common fix is ordering: the AI may lead with a feature screen when your strongest outcome is actually on screen three. Reorder before spending more credits. [App Store screenshot order that converts](/blog/app-store-screenshot-order-that-converts) explains why the first frames matter most. ### Step 3: Preview the hero frame before generating Before committing to a full set, preview the hero frame. A wizard preview costs 0.5 credit and shows you the theme, typography, frame, and headline treatment on your most important slide. If the direction is wrong here, it will be wrong on every slide, so this is the cheapest place to catch it. Ask three questions of the preview. Is the headline legible at thumbnail size? Does the background compete with the UI? Does it look like your brand, or like a template? If any answer is no, adjust and preview again rather than generating six slides you will revise later. ### Step 4: Generate the full pack Generating costs 1 credit per final slide, so a six-slide set is six credits. Generate only the slides you intend to ship; extra frames you will discard are wasted credits. On the App Store you can upload up to 10 screenshots per device size per localization, and on Google Play 2–8 phone screenshots, but most apps tell a tighter story in five to seven. StoreShots exports App Store iPhone PNGs at 1290×2796 and Google Play phone PNGs at 1080×1920. It does not generate iPad screenshots, Android tablet sizes, the Play feature graphic, or app preview videos, so plan those separately if your listing needs them. [Start an AI screenshot project](https://storeshotsai.com/login?next=%2Fdashboard) ### Step 5: Review checklist before you revise anything Review the whole set side by side before touching individual slides. Fixing one slide at a time without seeing the set tends to create inconsistency. Use a fixed checklist so the review is fast and repeatable. - Every headline is true for the current build, with no features you have not shipped - Headlines read at thumbnail size and are not truncated or crowded - The first two or three slides carry the main outcome on their own - The UI in each frame is the real screen the headline describes - Tone and terminology match your app and website - No two slides say the same thing in different words - Brand colours look right, not merely close - No sensitive or personal data visible in captures ### Step 6: Chat-revise single slides, then export When one slide is off, revise that slide only by describing the change in chat: shorten the headline, swap the emphasis, calm the background. Each slide chat revision costs 1 credit, and the rest of the set stays as it was. Be specific; 'make it better' produces a different slide, while 'cut the headline to four words that mention weekly limits' produces the slide you wanted. When the set passes your checklist, export it as a ZIP of PNGs. Re-exporting work you have already generated is free, so downloading again after a later revision does not cost extra. Before uploading, run a final pre-submit check to catch dimension and format issues. ### Localization: one story, per-locale packs Localized screenshots are where an automated screenshot maker saves the most repetitive work, and also where carelessness shows most. Capture screens from the localized build so the in-app text matches the headline language; an English UI under a German headline looks unfinished. Treat each locale as its own pack built from the same story. Let the AI draft headlines in the target language or paste in copy from your translator, then have a native speaker check every headline before export. Budget credits per locale: each generated slide in each language is a slide. The [localization guide](/blog/localize-app-store-screenshots) covers which markets to prioritise first. ### Where humans must stay in the loop AI drafts; you publish. Three areas cannot be delegated. First, claims accuracy: the AI writes persuasive copy from what it sees and what you tell it, and it can overstate. Any number, comparison, or 'first'/'best' claim needs a human who knows it is true. Second, brand: the AI picks a reasonable theme, but only you know whether it fits your positioning. Third, legal and compliance: health, finance, and kids' apps carry rules about what can be promised, and store review guidelines prohibit misleading listings. Where AI is weak is predictable. It does not know your competitors' listings or your conversion data. It can produce headlines that sound generic in crowded categories. It cannot fix a weak capture or a confusing UI. And it has no view of which slide converts better; for that you need Product Page Optimization on iOS or store listing experiments on Google Play, covered in the [A/B testing guide](/blog/app-store-screenshot-ab-testing-guide). ### Worked example: a hypothetical budgeting app Here is a clearly hypothetical example. A small team ships a budgeting app for freelancers with irregular income. They upload seven captures from the iOS build: home dashboard, income forecast, category budgets, a bill reminder, a weekly spending summary, savings goals, and settings. Tone: calm and reassuring. Audience: freelancers who dread month-end. The AI drops settings as low value and proposes the six-slide plan below. The team moves the forecast ahead of the dashboard because predicting income is the real differentiator, then previews the hero frame once. - Slide 1 — Income forecast: 'Know next month before it starts' - Slide 2 — Home dashboard: 'Every account, one calm view' - Slide 3 — Category budgets: 'Budgets that flex with your income' - Slide 4 — Bill reminders: 'Never miss a bill again' - Slide 5 — Weekly summary: 'See where the week went' - Slide 6 — Savings goals: 'Save for taxes without thinking' ### Credit math for the example In review, the team flags slide 4: 'Never miss a bill again' is a promise the app cannot guarantee, so they revise it to 'Bill reminders before they are due'. Slide 5's background competes with the chart, so they ask for a calmer one. That is two chat revisions. Total: one preview at 0.5, six slides at 1 each, and two revisions at 1 each, which comes to 0.5 + 6 + 2 = 8.5 credits. Re-exporting the final ZIP costs nothing. On the Starter pack ($10 for 50 credits) that leaves room for a Google Play version from Android captures and a second language. Credits are one-time and never expire, with no subscription; see [pricing](/pricing) for current packs. - Hero preview: 0.5 credit - Six generated slides: 6 credits - Two slide chat revisions: 2 credits - ZIP export and re-export: free - Total for one store, one language: 8.5 credits ### When to use a designer instead An AI screenshot generator for the App Store is the right tool when you ship often, need both stores, work in several languages, and want predictable cost. A designer is the better call when you are defining a new visual brand, need custom illustration or a mascot-led campaign, or want screenshots tied to a wider marketing campaign. Many teams use both: a designer sets the direction once, and AI handles release-by-release production. The full trade-off is in [AI app screenshot generator vs designers](/blog/ai-app-screenshot-generator-vs-designers). If you do not have screens yet, this workflow is the wrong starting point. The [AI mobile UI generator](/ai-mobile-ui-generator) designs screens from a prompt with HTML, React, and React Native export as an engineering starting point; screenshots come later, from the real build. #### How do I generate App Store screenshots with AI? Upload 3–10 real captures from your app, review the AI's plan for each screen, preview the hero frame, then generate the full set. Revise individual slides by chat, check every headline for accuracy, and export a ZIP of PNGs at 1290×2796 for iPhone or 1080×1920 for Google Play before uploading to the store. #### Does the AI redraw my app's interface? No, your uploaded screenshots stay the source of the UI shown in each slide. The AI adds layout, device frames, backgrounds, headlines, and subtext around your real captures. That keeps the listing accurate to the shipped app, but it also means messy captures produce messy slides, so clean up demo data first. #### How many credits does a typical screenshot set cost? A six-slide set starts at 6.5 credits and grows only with revisions. Generation is 1 credit per final slide, a hero preview is 0.5 credit, and each slide chat revision is 1 credit. One preview, six slides, and two revisions total 8.5 credits. Re-exporting work you already generated is free, and credits never expire. #### Can AI write my screenshot headlines? Yes, it drafts a headline and subtext for each screen based on its purpose, but a human should approve every line. AI copy can be generic in crowded categories or overstate what the app does. Check claims, numbers, and tone against your real product before export, and see the copywriting guide for patterns that work. #### Can StoreShots make iPad screenshots or a Play feature graphic? No, StoreShots exports iPhone screenshots at 1290×2796 and Google Play phone screenshots at 1080×1920 only. It does not generate iPad sets, Android tablet sizes, the 1024×500 Play feature graphic, or app preview videos. If your iOS app runs on iPad, Apple requires a 13-inch iPad set, so plan that separately. #### Is an AI screenshot generator better than hiring a designer? It depends on the job: AI is better for fast, repeatable, multi-store and multi-language production, while designers are better for creating a new visual brand or custom illustration. Many small teams have a designer set direction once and use AI for each release, which keeps cost predictable without losing brand quality. Sources: - [Screenshot specifications](https://developer.apple.com/help/app-store-connect/reference/screenshot-specifications) — Apple App Store Connect Help - [Add preview assets: screenshots and graphics](https://support.google.com/googleplay/android-developer/answer/9866151?hl=en) — Google Play Console Help - [Product page optimization](https://developer.apple.com/app-store/product-page-optimization/) — Apple Developer ### StoreShots AI vs. storeshots.org: two different products URL: https://storeshotsai.com/blog/storeshots-ai-vs-storeshots-org · Updated: 2026-09-20 · Author: StoreShots AI Editorial No: StoreShots AI at storeshotsai.com and the open-source project at storeshots.org are unrelated products with different makers, workflows, and pricing models. **No.** StoreShots AI at [storeshotsai.com](https://storeshotsai.com) and the project at [storeshots.org](https://storeshots.org) are not the same product. They have similar names, but different makers, domains, workflows, and commercial models. StoreShots AI is a hosted creative studio made by ClyroLabs. It creates App Store and Play Store listing packs from real app screens, designs connected Mobile UI with HTML, React, and React Native export, and creates mascot assets from one credit wallet. storeshots.org is an unrelated open-source project. It is not a free edition of StoreShots AI and is not affiliated with ClyroLabs. [Compare StoreShots AI credit packs](https://storeshotsai.com/pricing) ### The difference at a glance Use the domain as the first identity check. Do not copy pricing, support details, or feature claims from one product to the other. - StoreShots AI: storeshotsai.com, made by ClyroLabs, hosted AI studio, one-time credit packs. - storeshots.org: separate open-source project; consult its own repository, license, deployment instructions, and feature list. - StoreShots AI listing exports: App Store 1290×2796 and Play phone 1080×1920. - StoreShots AI credit facts: $10 for 50 credits or $18 for 100 credits; credits never expire. - TestMyApps is a related ClyroLabs closed-testing product, not either StoreShots product. ### What StoreShots AI does The hosted workflow starts with real iOS or Android captures. StoreShots keeps those captures as the UI source and composes the surrounding marketing art, device framing, ASO headlines, and export canvas around them. It does not redraw the product UI. If the app does not have usable screens yet, Mobile UI can generate a connected flow from a prompt and export HTML, React, React Native, and PNG renders as engineering starting points. Mascot Studio adds base PNGs, variants, and transparent GIF loops. - 1 credit = one store slide, Mobile UI screen, mascot base, or mascot variant. - 2 credits = one mascot GIF animation. - Re-export of approved work is free. - StoreShots AI creates assets; it does not submit listings or guarantee ranking. ### What this page does not claim about storeshots.org storeshots.org is a separate open-source project at its own official domain. Its own README, license, deployment instructions, and current feature list are the source of truth. This page does not import StoreShots AI pricing or describe the open-source project's current implementation beyond that identity distinction. Practical rule: use storeshots.org documentation for that project and storeshotsai.com for the ClyroLabs hosted product. ### Which link fits the job? Choose StoreShots AI for hosted listing packs, prompt-based Mobile UI, mascot assets, and a credit wallet that does not expire. Choose storeshots.org when you specifically want to evaluate the unrelated open-source project on its own terms. For Google Play closed testing and managed testers, use [TestMyApps](https://testmyapps.app). It is a related ClyroLabs product, not a StoreShots feature. 1. Hosted AI store packs, prompt UI, or mascot assets → StoreShots AI. 2. Open-source, self-hosted, or BYOK evaluation → storeshots.org documentation. 3. Google Play closed testing → TestMyApps. #### Are StoreShots AI and storeshots.org the same product? No. StoreShots AI is the hosted ClyroLabs product at storeshotsai.com. storeshots.org is a separate, unrelated open-source project. #### Who makes StoreShots AI? StoreShots AI is made by ClyroLabs. The product support email is clyrolabs@gmail.com. #### What does StoreShots AI cost? Starter is $10 for 50 credits and Studio is $18 for 100 credits. Credits never expire; see the official [pricing page](/pricing). #### Is there a free open-source StoreShots AI edition at storeshots.org? No. Do not treat storeshots.org as a free edition of StoreShots AI. They are separate products with separate domains and ownership. Sources: - [StoreShots AI](https://storeshotsai.com) — ClyroLabs - [StoreShots AI pricing](https://storeshotsai.com/pricing) — ClyroLabs - [storeshots.org](https://storeshots.org) — Official project site ### StoreShots vs. AppScreens: which screenshot workflow fits? URL: https://storeshotsai.com/blog/storeshots-vs-appscreens · Updated: 2026-09-20 · Author: StoreShots AI Editorial Compare StoreShots AI and AppScreens by input, editing, device coverage, localization, upload, pricing, and the type of launch each workflow suits. StoreShots AI and AppScreens both help turn app UI captures into store listing creatives, but they optimize for different launch shapes. StoreShots is a hosted AI creative studio with one-time credits plus Mobile UI and mascot workflows. AppScreens is a visual designer with templates, responsive device exports, paid localization, and direct store-upload features. This comparison uses first-party pages checked on September 20, 2026. Unknowns are marked as not publicly specified rather than guessed. ### At-a-glance fit - StoreShots AI: real screens → AI-assisted story, headlines, device framing, 1290×2796 App Store or 1080×1920 Play exports, ordered ZIP. - AppScreens: raw UI or blank canvas → templates, responsive multi-device designs, localization, and paid direct upload paths. - StoreShots includes HTML, React, React Native Mobile UI export and mascot PNG/GIF workflows; AppScreens does not publicly document those as product features. - AppScreens documents broader device and locale coverage; StoreShots focuses on the supported phone exports above and does not promise automatic localization. ### Workflow and output StoreShots starts from product truth: upload the screens you already ship, describe the audience and outcome, then revise individual slides before exporting. Uploaded UI remains the source inside the frame; the service composes backgrounds, typography, framing, and copy around it. AppScreens is better understood as a designer and template system. Its public materials describe placing raw app screenshots in device frames, a template library, a blank canvas, responsive exports across iPhone, iPad, Android, and other presets, plus AI captions and restyling on paid tiers. Neither workflow removes the need to check the final files against current Apple and Google requirements. StoreShots does not submit listings; AppScreens paid plans advertise App Store Connect and Google Play upload paths. ### Pricing: credits versus subscription StoreShots sells one-time packs: Starter is $10 for 50 credits and Studio is $18 for 100 credits. One credit covers one store slide, Mobile UI screen, mascot base, or mascot variant; a mascot GIF uses two credits. Credits never expire and approved-work re-export is free. AppScreens publishes a free tier and annual Pro and Scale plans. The pricing page checked for this article lists Free at $0, Pro at $99/year, and Scale at $180/year. Pro lists up to 10 languages; Scale lists 80+ locales and larger project limits. Confirm taxes and current checkout totals before purchase. - Choose credits for a bursty indie launch or mixed listing/UI/mascot work. - Choose a subscription when you maintain many locales, device sizes, and recurring listing variants. - These units are not directly equivalent; compare the workload you actually need. ### When to choose each Pick StoreShots AI when you want one wallet for listing packs, prompt-based Mobile UI, and mascot assets; you want credits that do not expire; or your target outputs are 1290×2796 and 1080×1920 with manual upload. Evaluate AppScreens when multi-locale responsive exports, iPad coverage, templates, or one-click store upload matter more than code export and mixed creative units. For a small phone set, either can work. Compare the [StoreShots samples](/sample) and confirm the other product's current limits before committing. [Compare current StoreShots packs](https://storeshotsai.com/pricing) #### Is StoreShots an AppScreens alternative? Yes, for teams comparing screenshot generators. StoreShots is strongest for AI-assisted packs plus Mobile UI and mascot assets; AppScreens is stronger for multi-locale, multi-device design and direct upload. #### Which tool exports React Native? StoreShots AI documents HTML, React, and React Native export through its [AI mobile UI generator](/ai-mobile-ui-generator). AppScreens' public materials reviewed for this comparison do not document React Native export. #### Does StoreShots support Play feature graphics? No. StoreShots currently supports Play phone screenshots at 1080×1920, not a dedicated 1024×500 feature-graphic generator. #### Do StoreShots credits expire? No. StoreShots credits never expire and approved-work re-export is free. Sources: - [AppScreens pricing](https://appscreens.com/pricing) — AppScreens - [AppScreens App Store screenshot generator](https://appscreens.com/app-store-screenshot-generator) — AppScreens - [Can I use AppScreens for free?](https://help.appscreens.com/getting-started/can-i-use-appscreens-for-free) — AppScreens Help - [AI captions in AppScreens](https://help.appscreens.com/design-and-customize/how-do-i-use-ai-to-generate-captions) — AppScreens Help ### StoreShots vs. ScreenshotWhale: compare the workflow, not the hype URL: https://storeshotsai.com/blog/storeshots-vs-screenshotwhale · Updated: 2026-09-20 · Author: StoreShots AI Editorial Compare StoreShots AI and ScreenshotWhale by inputs, store sizes, editing, localization, feature graphics, exports, pricing, and launch fit. Choose StoreShots AI when you want one hosted wallet for store screenshot packs, prompt-based Mobile UI with HTML/React/React Native, and mascot assets. Choose ScreenshotWhale when you want a template-and-editor workflow with broader device exports, paid translation, and a dedicated Google Play 1024×500 feature-graphic generator. Both products can help indie developers ship listing creatives. The better choice depends on whether your bottleneck is a mixed creative launch or a multi-size, feature-graphic-heavy store workflow. Facts below were checked on September 20, 2026. ### The practical difference - StoreShots AI: real screen captures, AI story and copy, per-slide revisions, 1290×2796 App Store and 1080×1920 Play phone PNGs, ordered ZIP. - ScreenshotWhale: raw captures, templates or AI-designed layouts, drag-and-drop editing, 22 marketed device sizes, locale-organized ZIP exports. - StoreShots: one-time Starter $10/50 or Studio $18/100 credits; credits never expire. - ScreenshotWhale: free tier, monthly plans, a 30-day Launch Pack, and a separate 1024×500 feature-graphic flow. ### Phone screenshots are not feature graphics StoreShots' Play output is a phone screenshot at 1080×1920. ScreenshotWhale also documents a dedicated 1024×500 Play feature-graphic canvas. These assets have different jobs: screenshots explain the product in a carousel, while the feature graphic acts as a wide store banner or promo-video cover. Do not stretch a 1080×1920 screenshot into a 1024×500 feature graphic. If your launch needs both, StoreShots covers the phone set and you need another feature-graphic workflow; ScreenshotWhale can cover both in one product. ### Editing, localization, and export StoreShots is optimized for a fast, product-truth-first path: upload real screens, generate a coherent narrative, revise weak slides, and export the supported phone sizes. It does not promise automatic localization, and it does not redraw uploaded UI. ScreenshotWhale documents a drag-and-drop editor, templates, brand controls, automatic device sizing, PNG/JPEG exports, and paid AI translation. Its public pages also describe high-resolution and commercial-license features on paid plans. Confirm current language counts and export limits at checkout. Neither product is a substitute for store policy review. StoreShots does not submit listings; ScreenshotWhale's public materials emphasize export for App Store Connect and Fastlane, while direct console API upload is not publicly specified in the sources checked. ### Pricing and best fit StoreShots uses one-time credits: Starter is $10 for 50 and Studio is $18 for 100. One credit covers one store slide, UI screen, mascot base, or mascot variant; a mascot GIF uses two credits; approved-work re-export is free. ScreenshotWhale's pricing checked for this article lists Free, Solo at $9.99/month, Studio at $19.99/month, Agency at $29.99/month, a $14.90 Launch Pack for 30 days, and single templates from $4.99. Annual billing is presented as roughly ten months of monthly pricing. - Choose StoreShots for a bursty launch, mixed UI/mascot work, and never-expire credits. - Choose ScreenshotWhale when feature graphics, multi-size exports, paid translation, or a template-first editor are requirements. - Either works for a small phone set you will upload manually; compare the specific deliverables before buying. [See StoreShots samples and pricing](https://storeshotsai.com/pricing) #### Is StoreShots a ScreenshotWhale alternative? Yes. StoreShots is strongest for AI-assisted packs plus Mobile UI and mascot assets on one-time credits; ScreenshotWhale is stronger when multi-device export, paid localization, and a Play feature graphic are required. #### Does StoreShots make Play feature graphics? No, not currently. StoreShots exports Play phone screenshots at 1080×1920; ScreenshotWhale documents a separate 1024×500 feature-graphic generator. #### Which tool exports React Native? StoreShots AI, through its [AI mobile UI generator](/ai-mobile-ui-generator). ScreenshotWhale's public materials reviewed here focus on store screenshot and feature-graphic design. #### What does ScreenshotWhale cost? The checked public pricing lists Free, Solo $9.99/month, Studio $19.99/month, Agency $29.99/month, Launch Pack $14.90 for 30 days, and templates from $4.99. Verify current checkout totals before purchase. Sources: - [ScreenshotWhale](https://screenshotwhale.com/) — ScreenshotWhale - [ScreenshotWhale pricing](https://screenshotwhale.com/pricing) — ScreenshotWhale - [App Store screenshot generator](https://screenshotwhale.com/app-store-screenshot-generator) — ScreenshotWhale - [Google Play feature graphic](https://screenshotwhale.com/feature-graphic-google-play) — ScreenshotWhale ### Best AI app store screenshot generators in 2026 URL: https://storeshotsai.com/blog/best-ai-app-store-screenshot-generators-2026 · Updated: 2026-09-20 · Author: StoreShots AI Editorial A factual 2026 comparison of StoreShots AI, AppLaunchFlow, AppScreens, ScreenshotWhale, AppScreenshotStudio and storeshots.org by workflow, output and price. There is no universal best AI app store screenshot generator. The right choice depends on whether you need a hosted multi-studio wallet, a full launch workspace, localization and direct upload, a Play feature graphic, an agent-friendly API, or an open-source BYOK workflow. This roundup compares six options searched by indie developers in 2026. It uses public product pages checked on September 20, 2026. Where a competitor does not clearly document a feature, this article says not publicly specified instead of treating absence as proof. ### Quick picks by launch job - AI multi-studio (screens + UI + mascot) → [StoreShots AI](https://storeshotsai.com). One wallet for listing packs, Mobile UI code export, and mascot assets. - Full launch workspace (screens + ASO + video) → [AppLaunchFlow](https://www.applaunchflow.com). Broader launch assets and publishing workflow. - Localization-heavy or direct upload → [AppScreens](https://appscreens.com). Template/canvas workflow with paid localization and upload paths. - One-off launch with a Play feature graphic → [ScreenshotWhale](https://screenshotwhale.com). Screenshots plus a dedicated 1024×500 flow. - Chat or agent-driven iteration → [AppScreenshotStudio](https://appscreenshotstudio.com). Chat-first workflow with REST/MCP features on paid tiers. - Free OSS, self-host, or BYOK → [storeshots.org](https://storeshots.org). Unrelated to StoreShots AI; evaluate its own license and docs. ### StoreShots AI StoreShots AI is a hosted ClyroLabs creative studio. Upload real product screens for listing art; the service maps the story, adds ASO-oriented headlines and surrounding composition, and exports App Store 1290×2796 or Play phone 1080×1920 PNGs in an ordered ZIP. The uploaded UI remains the source; StoreShots does not redraw it. The same wallet covers Mobile UI exports in HTML, React, React Native, and PNG, plus mascot base/variant PNGs and GIF loops. Starter is $10 for 50 credits and Studio is $18 for 100 credits; credits never expire. - Best for: a bursty indie launch needing screenshots plus UI/code or mascot assets. - Limits: no dedicated Play 1024×500 feature graphic, no listing submission, and no automatic localization promise. ### How the other tools differ - AppLaunchFlow: an AI-assisted launch workspace for screenshots, ASO copy, promo video, icons, mockups, localization, and related assets. The checked pricing listed a free preview, €9 Launch Pass for seven days, and €15/month or €99/year Unlimited. - AppScreens: templates or blank canvas with responsive multi-device exports, paid localization, AI captions/restyling, and direct App Store Connect/Google Play upload paths. Checked annual pricing listed Free, Pro $99/year, and Scale $180/year. - ScreenshotWhale: AI or template screenshot creation, marketed 22 device sizes, paid translation, and a dedicated 1024×500 Play feature graphic. Checked pricing listed Free, Solo $9.99/month, Studio $19.99/month, Agency $29.99/month, and a $14.90 Launch Pack. - AppScreenshotStudio: chat-first screenshot generation with canvas editing and REST/MCP features on Growth/Pro. Public pricing and credit details varied between pages, so confirm checkout. - storeshots.org: an unrelated AGPL-3.0 browser project with BYOK/self-host positioning. Use its official repository and license as the source of truth; do not attribute its features or pricing to StoreShots AI. ### How to choose without overbuying 1. Start with the input: existing product screens point to a screenshot workflow; no usable screens points to Mobile UI or a prompt-first tool. 2. Confirm output: phone screenshots, tablet sizes, and Play feature graphics are different deliverables. 3. Calculate total cost: compare a five-slide launch, the number of locales, revisions, and how often the listing changes. 4. Check handoff: decide whether you need manual upload, direct store upload, code export, REST/MCP, or self-hosting. 5. Review the final files and claims yourself. No generator removes store-policy, accessibility, or product-truth checks. [Start with StoreShots samples and pricing](https://storeshotsai.com/pricing) #### What is the best AI app store screenshot generator in 2026? It depends on the job: StoreShots for screenshots plus Mobile UI and mascots, AppLaunchFlow for broader launch assets, AppScreens for localization/upload, ScreenshotWhale for feature graphics, AppScreenshotStudio for chat/MCP, and storeshots.org for open-source/BYOK control. #### What sizes does StoreShots export? App Store phone listings at 1290×2796 and Play phone screenshots at 1080×1920. StoreShots does not currently generate a dedicated 1024×500 Play feature graphic. #### Does StoreShots export React Native? Yes. Its Mobile UI workflow exports HTML, React, React Native, and PNG renders as engineering starting points. #### Do StoreShots credits expire? No. Starter is $10 for 50 credits and Studio is $18 for 100 credits; credits never expire. #### Is StoreShots AI the same as storeshots.org? No. StoreShots AI is the hosted ClyroLabs product at storeshotsai.com. storeshots.org is an unrelated open-source project; read the dedicated [disambiguation guide](/blog/storeshots-ai-vs-storeshots-org). Sources: - [AppLaunchFlow](https://www.applaunchflow.com/) — AppLaunchFlow - [AppScreens](https://appscreens.com/) — AppScreens - [ScreenshotWhale](https://screenshotwhale.com/) — ScreenshotWhale - [AppScreenshotStudio](https://appscreenshotstudio.com/) — AppScreenshotStudio - [storeshots.org](https://storeshots.org/) — Official project site - [StoreShots AI pricing](https://storeshotsai.com/pricing) — ClyroLabs ### App mascot GIFs for onboarding: transparent loops that feel on-brand URL: https://storeshotsai.com/blog/app-mascot-gif-onboarding-guide · Updated: 2026-09-14 · Author: StoreShots AI Editorial Use AI-generated mascot GIFs on welcome screens, empty states, and success moments. StoreShots Mascot Studio branches variants and exports transparent animation loops. Onboarding is where users decide whether your app feels human or generic. A mascot GIF on the welcome screen, an idle loop while content loads, or a celebrate animation after a first task can make the product feel finished without hiring an illustrator for every state. StoreShots Mascot Studio generates a root character, branches outfit and pose variants on a visual tree, and exports transparent GIF loops you can drop straight into iOS, Android, or React Native projects. [Create a mascot](https://storeshotsai.com/ai-mascot-generator) ### Where mascot GIFs work best in mobile apps - Welcome and onboarding carousels — wave or point animations guide the first action - Empty states — idle loops keep the screen alive while there is no data yet - Success and completion — celebrate GIFs after signup, purchase, or task done - Loading and waiting — subtle bounce or idle motion instead of a static spinner - Marketing site hero — same transparent GIFs work outside the app ### Keep one parent, branch everything else The biggest mistake with mascots is generating unrelated images for every screen. In Mascot Studio, you select a node in the tree — root or a variant — and new variants or animations branch from that exact image. Colors, outfit, and line weight stay locked while you change pose, expression, or outfit. Export base PNGs and GIF loops individually, or download a ZIP with every asset for your design system folder. [See generated mascot samples](https://storeshotsai.com/sample#mascot-samples) #### What file format are mascot animations? StoreShots exports mascot animations as transparent GIF loops — ready for in-app onboarding, empty states, and marketing pages. #### Can I animate a variant instead of the root mascot? Yes. Select any variant node in the mascot tree, then generate a GIF. The animation uses that variant's look as the reference frame. Sources: - [Screenshot specifications](https://developer.apple.com/help/app-store-connect/reference/screenshot-specifications) — Apple App Store Connect Help - [App Store product page](https://developer.apple.com/app-store/product-page/) — Apple Developer - [Add preview assets: screenshots and graphics](https://support.google.com/googleplay/android-developer/answer/9866151?hl=en) — Google Play Console Help - [Store listing experiments](https://support.google.com/googleplay/android-developer/answer/9793453?hl=en) — Google Play Console Help ### Refresh Play Store screenshots after launch to lift listing performance URL: https://storeshotsai.com/blog/refresh-play-store-screenshots-after-launch · Updated: 2026-08-18 · Author: StoreShots AI Editorial Stale Play Store screenshots and empty ratings cost installs after launch. Refresh listing visuals with StoreShots, then add public reviews on TestMyApps. Closed testing gets an affected personal account to production. After the app is public, listing performance is a different job. Shoppers still decide from screenshots and stars. If the carousel shows an old onboarding flow, or the page has no ratings, they leave. StoreShots AI is the screenshot service for that live listing. TestMyApps is our other service for the same app — closed testing first, then public reviews and ratings once you are live. Use both. Do not treat launch day as the last time the store page changes. [Generate Play Store screenshots](https://storeshotsai.com/play-store-screenshot-generator) ### What listing performance actually means Play Console reports impressions, store listing conversion, and uninstalls. Screenshots sit in the first decision: the search result and the product page header. Reviews sit in the second: whether the page feels trusted enough to install. Refreshing screenshots after a UI change, a new core flow, or a positioning shift is the highest-leverage creative update you control without shipping a new binary. Pair that with public ratings if the listing is still empty. - Update slides whose UI no longer matches the production build - Keep slide one as the outcome, not a leftover beta headline - Export Play Store phone size at 1080 × 1920 — do not stretch App Store frames - Then add public reviews on TestMyApps if stars are missing ### Workflow with StoreShots AI and TestMyApps Capture the current production screens. Generate a Play Store pack in StoreShots AI, chat-edit any slide that drifted, and export. Upload in Play Console. If the listing is live and still has no public social proof, open TestMyApps Reviews & Ratings and submit the listing URL. Do not re-apply for production access just because you ran another closed test after launch. That gate is done. Listing performance is screenshots plus reviews. [Play Store reviews for live listings](https://testmyapps.app/play-store-reviews-and-ratings) #### Should I refresh screenshots if the app is already live? Yes, whenever the production UI, core outcome, or brand has changed. Stale screenshots suppress listing conversion even when the binary is better. #### Is TestMyApps a separate company? No. TestMyApps is our other service for your app. StoreShots AI handles listing visuals. TestMyApps handles closed testing and live-listing reviews. Sources: - [Add preview assets: screenshots and graphics](https://support.google.com/googleplay/android-developer/answer/9866151?hl=en) — Google Play Console Help - [Store listing experiments](https://support.google.com/googleplay/android-developer/answer/9793453?hl=en) — Google Play Console Help ### Export AI Mobile UI to HTML, React and React Native Code URL: https://storeshotsai.com/blog/ai-mobile-ui-ux-generator-html-react-react-native · Updated: 2026-08-13 · Author: StoreShots AI Editorial Design a multi-screen mobile app UI from one prompt, then export HTML, React, and React Native code plus high-fidelity renders — without starting in Figma. Most teams still split product design and engineering: a Figma file for screens, a separate repo for HTML or React Native, and a third pass to make the two match. An [AI mobile UI generator](/ai-mobile-ui-generator) collapses that loop. You describe the product, get a connected screen plan, and leave with development-ready code — HTML, React, and React Native — plus high-fidelity renders of every screen. [StoreShots AI](/) now ships that Mobile UI/UX studio beside store screenshot generation. The same credit wallet powers listing packs and app screens, so a launch team can design the product UI and the store listing without switching tools. ### What an AI mobile UI/UX generator should produce A useful generator is not a single pretty mockup. It is a small product: home, detail, checkout, profile, and the states between them. StoreShots Mobile UI plans those screens together, then generates each one on a live canvas so the visual language stays consistent. The export is what makes it usable for development. Each screen can download as: - A high-fidelity PNG render for reviews and store planning - HTML and CSS for a web or hybrid prototype - React components for a web app or Next.js shell - React Native code for iOS and Android implementation - A ZIP with images plus all three code targets ### HTML, React, and React Native from the same screens Engineering teams rarely want only a picture. They want a starting point that already encodes spacing, type, and component structure. Generating [React Native UI](/ai-mobile-ui-generator) alongside HTML and React means a designer, a web engineer, and a mobile engineer can work from one source instead of three redraws. Treat the export as a strong first draft. You will still wire data, navigation, and auth. You will not start from an empty ScrollView and a moodboard. ### How StoreShots Mobile UI/UX works Open the workspace, choose Mobile UI/UX, and describe the app in one short brief — for example a wellness booking product with discovery, class details, and checkout. Optional reference images help lock color and photography. StoreShots plans the screen set, opens the canvas, and lets you edit names and briefs before generation. Credits are the same packs used for store screenshots: one credit per generated UI screen. Re-export of approved screens does not consume extra credits. See [pricing](/pricing) and live [samples](/sample). 1. Write a product brief (and optional visual references) 2. Review the connected screen plan 3. Generate screens on the live canvas 4. Revise individual screens in chat 5. Export HTML, React, React Native, and PNG as a ZIP [Design a mobile UI](https://storeshotsai.com/login?next=%2Fdashboard%3Fmode%3Dui) ### When to use Mobile UI vs store screenshots Use Mobile UI/UX when the app is not built yet, or when you need a multi-screen flow for engineering. Use StoreShots listing generation when you already have real in-app captures and need App Store 1290×2796 or Play Store 1080×1920 PNGs with ASO copy. Many teams do both: design the UI, implement it, capture the real screens, then generate the store listing from those captures. One studio, one credit wallet. #### Does StoreShots AI generate React Native code? Yes. Mobile UI/UX projects export HTML, React, and React Native for each generated screen, plus PNG renders, in a ZIP. #### Is Mobile UI included in the same credit packs as store screenshots? Yes. Starter is $10 for 50 credits and Studio is $18 for 100 credits. One credit generates one Mobile UI screen or one store screenshot slide. #### Can I edit one screen without regenerating the whole app? Yes. Chat-revise a single screen on the canvas. Other screens stay as they are. Sources: - [React Native](https://reactnative.dev/) — Meta Open Source - [React](https://react.dev/) — Meta Open Source ### How to Design a Mobile App UI from a Prompt in 2026 URL: https://storeshotsai.com/blog/design-mobile-app-ui-from-prompt-2026 · Updated: 2026-08-13 · Author: StoreShots AI Editorial A practical workflow for AI mobile UX: write a brief, plan connected screens, generate on a canvas, then export HTML, React, and React Native for development. A prompt is not a substitute for product thinking. It is a faster way to get a first vertical slice on screen. In 2026 the useful pattern is: one brief, a connected screen plan, generate, then export code your engineers can actually open. This guide walks through that path in [StoreShots AI Mobile UI/UX](/ai-mobile-ui-generator) — the same workspace that also generates App Store and Play Store screenshots once you have real captures. ### Write a brief that names the jobs Weak prompts name a vibe. Strong prompts name jobs: who uses the app, what they do first, and which three to eight screens matter. Example: “Design a calm wellness booking app with discovery, class details, checkout, and upcoming bookings.” Add constraints that affect layout: light or dark appearance, language, and optional reference photos. StoreShots uses those to keep the visual direction stable across the pack. - Name the product and the primary user - List the screens in the order people move through them - Call out must-have actions (book, pay, message, track) - Attach up to three visual references if you have a brand look ### Review the screen plan before you spend credits Generation should not surprise you with a random set of pretty but disconnected frames. StoreShots plans the pack first — names and briefs per screen — so you can rename “Screen 3” to “Checkout” and fix the story before any credit is charged for renders. Edit the plan until it matches a real user path. Then generate. That is cheaper than regenerating a whole app because slide two was actually a settings dump. ### Generate, revise one screen, export the ZIP Each generated screen lands on a live canvas. If checkout feels too heavy, chat-revise that screen only. Home and detail stay put. When the flow is right, export a ZIP: PNG renders for stakeholders, plus HTML, React, and React Native for development. See the companion article on [AI mobile UI generators and code export](/blog/ai-mobile-ui-ux-generator-html-react-react-native). [Start a Mobile UI project](https://storeshotsai.com/login?next=%2Fdashboard%3Fmode%3Dui) ### After UI: listing screenshots from real captures Once the app exists, switch to StoreShots listing mode. Upload the real iOS or Android screens and generate App Store 1290×2796 and Play Store 1080×1920 packs with ASO headlines. That is a different job from UI generation — and it is the same product. Browse [sample packs](/sample), then [pricing](/pricing). Credits never expire. #### How many screens should I generate from one prompt? Three, five, or eight connected screens is the usual range. Start with the path a new user actually takes, not every settings page. #### Do I need Figma if I use an AI mobile UX generator? Not for the first slice. You may still use Figma later for brand systems. StoreShots gives you canvas UI plus HTML, React, and React Native so engineering can start immediately. Sources: - [React Native](https://reactnative.dev/) — Meta Open Source - [React](https://react.dev/) — Meta Open Source ### AI vs Designers for App Store Screenshots: Which Wins in 2026? URL: https://storeshotsai.com/blog/ai-app-screenshot-generator-vs-designers · Updated: 2026-05-25 · Author: StoreShots AI Editorial Compare AI app screenshot makers and traditional designer workflows — cost, speed, quality, and when to use a hybrid approach for App Store and Play Store listings. Creating app store screenshots used to mean a binary choice: hire a designer and wait days for revisions, or block off an afternoon in Figma hoping your typography instincts are better than they were last launch. In 2026 a third path is mainstream — [AI app screenshot maker](/) tools that ingest raw captures and output styled, copy-enriched, export-ready listing sets in minutes. The question is no longer whether AI can produce screenshots. It clearly can. The better question is where AI beats human designers, where designers still win, and how smart teams combine both without overspending or shipping generic creative that fails conversion. This comparison walks through real workflows, costs, quality trade-offs, and decision criteria so you can pick the right approach for your next App Store and Play Store refresh — including when [StoreShots AI](/) fits as your primary [app store screenshot generator](/app-store-screenshot-generator) versus when to bring in a specialist. ### The traditional designer workflow A typical agency or freelance engagement starts with a brief: audience, key features, brand guidelines, competitor references, and store targets. The designer requests high-resolution captures or a TestFlight build, writes headline concepts, explores layout directions, presents two or three routes, incorporates feedback, prepares device frames and backgrounds, exports at 1290 × 2796 for iOS and 1080 × 1920 for Android, and delivers organized PNGs. Quality can be excellent — custom illustration, nuanced art direction, and brand storytelling that no template reproduces. The constraints are time and money. First-time projects often run one to three weeks calendar time and hundreds to thousands of dollars depending on scope and revision rounds. Every UI update restarts the clock. Changed a tab bar? New onboarding? Pricing restructure? You are back in revision emails. Teams that ship fortnightly feel this pain acutely. 1. Capture app screens on device or simulator 2. Write marketing copy in a separate doc 3. Explore layouts in Figma, Sketch, or Photoshop 4. Apply backgrounds, device frames, and type systems 5. Resize and export per store size class 6. Upload to App Store Connect and Play Console 7. Repeat after every material product change ### Where manual workflows break down Time consumption is the obvious tax. Even skilled designers spend hours on alignment, export variants, and locale adjustments. Founders doing it themselves often lose a full day per platform per language. Design skill gaps matter too. Not every developer understands visual hierarchy, contrast for OLED screens, or how much copy survives App Store search thumbnails. Bad typography and cluttered slides hurt conversion even when the underlying app is strong. Cost compounds with frequency. A one-time $800 screenshot pack feels reasonable; paying that quarterly because your product evolves quickly does not. Freelance scope creep — "just one more slide" — adds up silently. - Manual resizing introduces blur and inconsistent margins - Copy and layout live in separate files that drift apart - Localization requires duplicate Figma files or fragile text overlays - Version control for PNG exports is often "final_v7_REAL.png" - Handoff delays block release trains waiting on creative ### How AI screenshot generators work Modern [AI app screenshot maker](/) platforms accept uploaded captures or simulator exports, analyze UI structure and app category context, and generate headline copy aligned with ASO best practices. They apply consistent backgrounds, device frames, and spacing, then export at store-required dimensions without manual math. [StoreShots AI](/) follows this pattern: upload screens, describe your audience or value prop, generate a full carousel, chat-edit individual slides when messaging or UI shifts, and download App Store 1290×2796 or Play Store 1080×1920 PNGs from one project. Re-export after edits does not require rebuilding from scratch. AI excels at repeatable production tasks — sizing, frame alignment, copy drafts, maintaining visual consistency across five to eight slides. It does not automatically replace strategic brand positioning or bespoke illustration unless you guide it carefully. ### AI advantages: speed, cost, and iteration Speed is the headline benefit. Workflows that took hours or days compress to minutes. Solo developers can refresh listings the same day they ship a feature — critical when launch windows and Apple feature submissions have hard deadlines. Cost is lower and more predictable. Subscription or credit-based [pricing](/pricing) for an [app store screenshot generator](/app-store-screenshot-generator) typically runs orders of magnitude below repeated freelance engagements, especially when you iterate often. Iteration friction drops. Need a new headline on slide three? Regenerate or chat-edit one slide instead of reopening a multi-layer Figma file. Localization becomes regenerating copy per locale rather than hand-placing translated strings. [Create screenshots with StoreShots AI](https://storeshotsai.com/login?next=%2Fdashboard) ### Side-by-side comparison Use this table as a starting point — your category, brand maturity, and release frequency tilt the answer. - Time to first export — AI: minutes to an hour; Designer: days to weeks - Cost per refresh — AI: low subscription or credits; Designer: hundreds+ per cycle - Custom illustration — AI: limited unless combined with designer assets; Designer: strong - Brand system complexity — AI: good for template-driven consistency; Designer: best for net-new identity - Store export accuracy — AI: native 1290×2796 and 1080×1920; Designer: depends on discipline - Localization scale — AI: regenerate headlines quickly; Designer: linear cost per locale - UI update churn — AI: chat-edit single slides; Designer: revision rounds - Conversion copy drafting — AI: strong first drafts; Designer: strong if ASO-aware ### When designers still win AI does not replace every creative need. Large enterprise rebrands with custom illustration systems, 3D mascots, or campaign-specific storytelling still benefit from senior art direction. If your marketing depends on unique visual language that competitors cannot mimic with the same tool, invest in humans for the concept phase. Highly regulated categories sometimes require legal review of every visual claim — designers embedded in your compliance workflow may integrate smoother than AI-first drafts, though AI can still accelerate exploration. Billboard-style launch campaigns that extend far beyond store carousels — TV, out-of-home, paid social — need unified systems designers build holistically. Store screenshots become one output of a broader brand package. - Net-new brand identity from scratch - Custom character illustration and mascots - Multi-channel campaign creative beyond store listings - Complex photo compositing or 3D renders - Stakeholder workshops to define positioning before pixels ### When AI is the smarter default Indie developers, bootstrapped startups, and teams without in-house design should default to AI for routine [ASO screenshots](/). You get store-ready output without learning Figma or negotiating rush fees. High ship frequency makes AI nearly mandatory. If you release every two weeks, manual screenshot production becomes a bottleneck that guarantees stale listings. Multi-locale apps gain disproportionate value. Regenerating localized headline sets beats maintaining twelve Figma variants. Pair with our [localization guide](/blog/localize-app-store-screenshots) for workflow detail. Play Store and App Store parity from one tool matters when you maintain both listings. A [play store screenshot generator](/play-store-screenshot-generator) that exports 1080×1920 alongside iOS sizes eliminates an entire class of resize bugs. ### The hybrid workflow most teams should use The emerging best practice is not AI instead of designers — it is AI then refine. Generate a complete baseline set with an [AI app screenshot maker](/), validate slide order against [conversion principles](/blog/app-store-screenshots-increase-downloads-2026), chat-edit headlines for brand voice, and optionally hand one or two hero frames to a designer for illustration overlays. Designers shift from production labor to art direction: picking the winning AI variant, adjusting accent colors to match an updated icon, or adding a campaign badge. Production exports still flow through the generator for correct dimensions. This hybrid cuts calendar time by fifty to eighty percent while preserving brand where it matters. Enterprise teams use the same pattern — AI for velocity, humans for differentiation on slide one. [Create screenshots with StoreShots AI](https://storeshotsai.com/login?next=%2Fdashboard) ### Quality concerns — and how to address them Skeptics worry AI output looks generic. That risk is real if you accept the first generation blindly. Mitigate by feeding quality captures, specifying audience and tone, locking a cohesive background system, and editing copy so it reflects your positioning not category boilerplate. Another concern is inaccurate UI representation. AI cannot show features you have not built — you supply captures. Always verify that every slide reflects shipping product; policy and refund issues follow misleading frames. Typography and contrast still deserve a human glance. Run the squint test at thumbnail size before upload. If headlines fail, shorten them — AI gives drafts, you enforce standards. ### Cost modeling for a year of releases Imagine twelve releases per year needing screenshot touch-ups. Freelance at $600 per refresh totals $7,200 annually before rush fees or localization. An AI platform at typical [pricing](/pricing) tiers often lands under a tenth of that with unlimited re-export on edited slides. Designer spend is not wasted — redirect savings toward one strategic brand refresh or paid UA tests on alternate screenshot variants. Economic efficiency is about allocation, not eliminating design budgets entirely. Opportunity cost matters too. Founder hours spent in Figma are hours not spent on product, support, or distribution. AI buys back focus. ### Store export requirements both approaches must hit Regardless of who — or what — produces your creative, technical gates are identical. App Store 6.9-inch iPhone portraits at 1290 × 2796 (or 1320 × 2868 / 1260 × 2736). Play Store phone screenshots at 1080 × 1920. Google Play feature graphics at 1024 × 500 when used. PNG when gradients or text overlays need crisp edges. Designers miss dimensions when busy; AI generators encode them by default. See [how it works](/how-it-works) for StoreShots export behavior and our [Play Store complete guide](/blog/play-store-screenshot-generator-complete-guide-2026) for Android-specific asset rules. Incorrect sizes cause rejection or soft blur that screams low quality next to sharper competitors. Treat export specs as non-negotiable regardless of workflow choice. ### Decision matrix: pick your path Choose AI-first if you ship often, have limited design budget, need multiple locales, or want both iOS and Android exports from one project. Choose designer-first if you are establishing a distinctive visual brand, running large above-the-store campaigns, or need custom illustration that defines your category positioning. Choose hybrid if you have some design capacity, care about brand polish, but refuse to let screenshot production block releases. Most growth-stage mobile teams land here by year two. - AI-first — indie, startup, frequent releases, dual-store parity - Designer-first — enterprise rebrand, illustration-heavy category, agency-led launch - Hybrid — scale-ups refining AI baselines with selective human polish - Manual DIY — only if you enjoy design and ship rarely (honest rarity) ### Security, ownership, and who holds the source files Designer engagements should clarify file ownership upfront — Figma links, font licenses, and whether you can self-serve edits after the contract ends. Some agencies retain editable sources unless you pay for handoff; others deliver PNGs only, locking you into repeat engagements for trivial headline tweaks. AI platforms store projects in your account with re-export rights on edited slides. You still own your raw captures and exported PNGs. Review terms for data retention if screenshots contain unreleased product UI — most indie apps are low risk, but enterprise teams may have NDA constraints. Neither path eliminates the need for accurate marketing claims. Designers and AI both require you to verify that screenshots reflect shipping features before upload. ### Onboarding a new teammate or agency mid-stream Hybrid workflows shine when roles change. A new marketer can chat-edit headlines in an existing StoreShots project without learning your Figma component library. A new designer can import AI exports as reference layers rather than blank canvases — cutting exploration time. Document your slide order rationale in a one-page brief: hero outcome, workflow proof, differentiator, trust. Both humans and AI produce better output when they inherit strategy, not just assets. ### The future: more automation, not less craft AI screenshot tooling will keep improving: smarter locale-aware copy, tighter UI understanding, experiment variant generation, and integration with store analytics feedback loops. The production layer automates; taste and positioning stay human. Designers who embrace AI handle more concurrent clients and focus on concepting. Developers who avoid design entirely still ship credible listings. The gap between "we have no creative" and "we have store-ready creative" collapsed. Your competitive edge is not which tool you pick — it is how fast you align listing story with product reality when users compare you to five alternatives in search results. [Create screenshots with StoreShots AI](https://storeshotsai.com/login?next=%2Fdashboard) ### Final verdict AI app screenshot generators are not better than designers at everything — they are better at production speed, cost predictability, localization scale, and store-accurate exports. Designers remain stronger for bespoke brand worlds and complex cross-channel creative. For most teams shipping mobile apps in 2026, the rational default is an [AI app screenshot maker](/) with optional designer polish on hero assets. That is the workflow [StoreShots AI](/) enables: generate fast, edit surgically, export correctly, repeat every release without starting from blank canvas. Stop asking whether AI replaces designers. Ask how many hours and dollars you save by letting AI handle production while humans handle taste. Then invest those savings in growth. #### Can an AI app screenshot generator replace a designer completely? For routine App Store and Play Store listing production, often yes — especially for indie and startup teams. Custom brand illustration, large campaign creative, and complex visual systems still benefit from designers. Many teams use AI for 80% of production and designers for strategic polish. #### Is AI screenshot quality good enough for the App Store? Yes, when you start from sharp captures, edit headlines for accuracy, and export at 1290×2796. StoreShots AI produces store-ready PNGs with device frames and ASO copy. Review slides for policy compliance and UI truthfulness before submit — the same gate you'd use with designer output. #### How much cheaper is AI vs hiring a designer? Freelance screenshot projects often cost hundreds per refresh; AI tools typically cost far less per year via subscription or credits, with free re-export on edited slides. Exact savings depend on release frequency and locale count — frequent shippers see the largest gap. #### Which is faster for updating screenshots after a UI change? AI is usually faster: chat-edit or regenerate individual slides, re-export at correct dimensions in minutes. Designer workflows require briefing, scheduling, and revision rounds that stretch days or weeks. #### Do AI tools handle Play Store and App Store sizes? Quality tools do. StoreShots AI exports App Store at 1290×2796 and Play Store at 1080×1920 from one project, avoiding manual resize errors common in hybrid designer workflows. #### What is the best hybrid workflow? Generate a full baseline set with AI, validate slide order and copy, optionally send slide one to a designer for custom illustration, then export all sizes from the generator. Designers focus on direction; AI handles repetitive production. #### Will AI screenshot tools improve further? Yes. Expect better localization, variant generation for store experiments, and tighter integration with analytics feedback. Production automates; positioning and compliance review stay human. Sources: - [Screenshot specifications](https://developer.apple.com/help/app-store-connect/reference/screenshot-specifications) — Apple App Store Connect Help - [App Store product page](https://developer.apple.com/app-store/product-page/) — Apple Developer - [Add preview assets: screenshots and graphics](https://support.google.com/googleplay/android-developer/answer/9866151?hl=en) — Google Play Console Help - [Store listing experiments](https://support.google.com/googleplay/android-developer/answer/9793453?hl=en) — Google Play Console Help ### Google Play closed testing after your screenshots are ready URL: https://storeshotsai.com/blog/google-play-closed-testing-after-screenshots · Updated: 2026-05-23 · Author: StoreShots AI Editorial Listing visuals come first — then 12 opted-in testers for 14 days. How StoreShots AI and TestMyApps fit into one Android launch workflow. Most Android launches need two parallel tracks: a credible Play Store listing and a closed-testing run that satisfies Google's production-access requirements. Screenshots sell the product; closed testing proves real users can install and use it. For personal developer accounts, Google Play often requires at least 12 opted-in testers for 14 consecutive days before you can request production access. That is operational work — recruiting, opt-in links, participation, and follow-up — not something your screenshot tool should pretend to replace. ### Recommended order 1. Generate Play Store screenshots at 1080 × 1920 with StoreShots AI 2. Upload listing assets and finalize store copy in Play Console 3. Start a closed test with 12 real testers for the full 14-day window 4. Collect feedback, fix blockers, then request production access ### Where TestMyApps fits TestMyApps is our other service for your app — managed mobile app testing. It helps developers run Google Play closed testing and iOS TestFlight-style flows with verified testers, coordinated onboarding, and clearer progress toward store approval — without rebuilding a recruitment workflow for every release. Use StoreShots AI for listing visuals. When testing is the bottleneck, move to TestMyApps for the 12-testers-for-14-days requirement and managed coordination. #### Can I skip closed testing if my screenshots look good? No. Store visuals and closed testing solve different problems. Strong screenshots improve conversion; closed testing satisfies Google's pre-production requirements for many Android accounts. #### Does TestMyApps replace StoreShots AI? No. They are complementary. StoreShots AI generates store screenshots; TestMyApps manages tester coordination for closed testing and release readiness. Sources: - [App testing requirements for new personal developer accounts](https://support.google.com/googleplay/android-developer/answer/14151465?hl=en) — Google Play Console Help - [Set up an open, closed, or internal test](https://support.google.com/googleplay/android-developer/answer/9845334?hl=en) — Google Play Console Help ### The App Store screenshot order that converts browsers into installers URL: https://storeshotsai.com/blog/app-store-screenshot-order-that-converts · Updated: 2026-05-23 · Author: StoreShots AI Editorial A practical slide-by-slide order for iOS App Store screenshots — what to show first, how many slides you need, and how to align headlines with visible UI. App Store visitors decide in seconds. Your first screenshot is not a branding exercise — it is a promise. The strongest listings open with a clear outcome tied to visible product UI, not a logo splash or generic tagline. Apple allows up to ten iPhone screenshots per localization. Most high-converting indie apps ship five to seven slides: enough room for a story arc without exhausting scroll depth on a small phone screen. ### Recommended slide sequence 1. Slide 1 — Hero outcome: one sentence benefit above the primary screen users will use daily 2. Slide 2 — Core workflow: show the action that delivers the outcome (search, create, track, message) 3. Slide 3 — Differentiator: a feature competitors bury in settings, presented as a headline 4. Slide 4 — Depth or variety: secondary module, integration, or persona-specific use case 5. Slide 5 — Trust: ratings snippet, user count, award, or security/privacy cue if authentic 6. Slide 6 — Optional social proof or comparison frame if you have verifiable numbers 7. Slide 7 — Soft CTA: what happens immediately after install (free trial, no account required, etc.) ### Headline and UI alignment rules Every headline must match what is on screen. If the copy says "Track spending in one tap," the UI below should show a tap target or completed action — not an unrelated settings page. Keep headline length short enough to read in search results. Roughly four to seven words per slide survives carousel cropping better than full sentences. - Repeat the app name on slide one only — not on every frame - Use the same background system and device frame across the set - Export at 1290 × 2796 for 6.7" iPhone portraits unless you maintain separate asset classes - Regenerate localized headline copy per locale instead of overlaying translated text manually ### When to regenerate vs reuse Reuse the narrative order across releases; regenerate visuals when UI changes materially. Minor bug-fix builds rarely need a full redesign — update slides whose UI changed and keep the rest. StoreShots AI lets you chat-edit individual slides after the first generation, so you can fix one outdated screen without rebuilding the entire pack or paying again for unchanged exports. #### How many App Store screenshots should I upload? Five to seven strong slides beat ten weak ones. Lead with outcome, prove the workflow, then add trust. Only fill all ten slots if each slide adds a distinct message. #### Should the first screenshot include pricing? Usually no. Slide one should sell the core outcome. Mention free tiers or trials on a later slide or in the subtitle field, not at the expense of your hero promise. Sources: - [Screenshot specifications](https://developer.apple.com/help/app-store-connect/reference/screenshot-specifications) — Apple App Store Connect Help - [App Store product page](https://developer.apple.com/app-store/product-page/) — Apple Developer ### Store screenshot checklist before you hit Submit in App Store Connect or Play Console URL: https://storeshotsai.com/blog/store-screenshot-checklist-before-submit · Updated: 2026-05-23 · Author: StoreShots AI Editorial A pre-flight checklist for dimensions, file types, slide order, copy accuracy, and policy-safe visuals — so your listing does not bounce on a technicality. Review teams and store policies care about accurate marketing. Screenshots that promise features you have not shipped, show competitor logos, or use misleading before/after claims create rejection risk and refund churn. Run this checklist on every release — especially when you reuse an old creative set after a UI overhaul. ### Technical checks - App Store 6.7" portraits exported at 1290 × 2796 px (PNG recommended) - Play Store phone screenshots at 1080 × 1920 px portrait - Google Play feature graphic at 1024 × 500 px if you use one - No upscaled blurry captures — start from high-resolution device screenshots - File names organized by locale and slide index for faster uploads ### Message and policy checks - Slide headlines match visible UI on the same frame - No guaranteed ranking or income claims unless substantiated - Age-restricted content flagged appropriately in listing metadata - Third-party trademarks removed unless you have rights - Pricing and trial language matches current in-app purchase rules ### Story and conversion checks 1. Slide one states a user outcome, not internal feature jargon 2. At least one slide shows the primary happy-path workflow 3. Text readable at thumbnail size in search results 4. Visual style consistent across all slides and locales 5. Localized sets updated when you localize metadata ### After screenshots: Android closed testing Polished visuals get users to the install button; Google Play closed testing gets personal developer accounts toward production access. If you still need twelve opted-in testers for fourteen days, run that track in parallel on TestMyApps while screenshots are in review. #### How often should I refresh screenshots? Refresh when UI, core value prop, or brand identity changes materially — typically each major release or repositioning, not every patch version. #### Can I A/B test screenshots in the stores? Apple and Google offer product page experiments on eligible accounts. Export alternate sets at the same dimensions so variants differ in message, not aspect ratio. Sources: - [Screenshot specifications](https://developer.apple.com/help/app-store-connect/reference/screenshot-specifications) — Apple App Store Connect Help - [App Store product page](https://developer.apple.com/app-store/product-page/) — Apple Developer - [Add preview assets: screenshots and graphics](https://support.google.com/googleplay/android-developer/answer/9866151?hl=en) — Google Play Console Help - [Store listing experiments](https://support.google.com/googleplay/android-developer/answer/9793453?hl=en) — Google Play Console Help ### Play Store feature graphic vs phone screenshots: what each asset does URL: https://storeshotsai.com/blog/play-store-feature-graphic-and-screenshots · Updated: 2026-05-22 · Author: StoreShots AI Editorial Google Play uses a feature graphic and up to eight phone screenshots. Learn sizing, messaging split, and how to keep both assets visually consistent. Google Play listings combine a 1024 × 500 feature graphic with up to eight phone screenshots at 1080 × 1920. They appear in different surfaces — the feature graphic often anchors the top of your store page while screenshots carry the detailed story in the carousel. Teams that treat the feature graphic as a tiny poster and screenshots as proof convert better than teams that duplicate the same message in both places. ### Feature graphic guidelines - Size: 1024 × 500 px PNG or JPEG - No excessive text — Play may reject graphics that look like banners - Show brand mark + one visual hook, not a six-line paragraph - Pull colors from your app icon for instant recognition - Avoid critical detail near edges; safe margins help on varied devices ### Phone screenshots (1080 × 1920) Phone screenshots do the explanatory work: outcomes, workflows, proof. Keep slide one aligned with the feature graphic promise so users do not feel bait-and-switched when they scroll. StoreShots AI generates portrait phone sets with device frames and ASO headlines from the same raw captures you use for iOS — export Play and App Store sizes from one project. - First screenshot appears largest in search — treat it as your hero - Up to eight phone screenshots per listing - PNG preferred when gradients or type overlays are present - Maintain one master aspect ratio; avoid upscaling small captures ### Consistency checklist 1. Match accent color between feature graphic and screenshot backgrounds 2. Use the same tone of voice in feature graphic hook and slide-one headline 3. Show real product UI in screenshots, not abstract illustrations alone 4. Localize both asset types when you translate listing copy #### Can I use a screenshot as the feature graphic? You can repurpose visual elements, but the feature graphic has a wide 1024 × 500 canvas. A cropped phone screenshot rarely fills it well — design a simple poster-style graphic instead. Sources: - [Add preview assets: screenshots and graphics](https://support.google.com/googleplay/android-developer/answer/9866151?hl=en) — Google Play Console Help - [Store listing experiments](https://support.google.com/googleplay/android-developer/answer/9793453?hl=en) — Google Play Console Help ### How to localize App Store and Play Store screenshots without breaking layout URL: https://storeshotsai.com/blog/localize-app-store-screenshots · Updated: 2026-05-21 · Author: StoreShots AI Editorial Locale-specific headlines, longer translated strings, and export sizes — a workflow for multilingual store listings that stay readable on small screens. Translating your store listing title and description but leaving English screenshots sends mixed signals — and wastes conversion in non-English markets. Localized screenshots show that the product respects the user's language. The hard part is layout: German headlines run long. Thai line breaks differ. Manual Photoshop overlays break the moment you add a second locale. ### What to localize first 1. Slide headlines and subtext on every screenshot 2. On-screen callouts only if they are marketing overlays you control 3. Keep raw in-app UI in the user's language if your app supports it — capture locale-specific builds when possible 4. Feature graphic hook text for Google Play ### Workflow with StoreShots AI Create one project from your master captures. Generate the English set first and validate slide order. Then regenerate headline copy per target language while locking layout, colors, and export dimensions. Each locale in App Store Connect and Google Play Console can reference its own screenshot set at the correct size — 1290 × 2796 for iPhone 6.7" and 1080 × 1920 for Play Store phones. - Do not stretch one language's PNG into another locale slot - Shorter headline variants help languages that expand in translation - Re-export is free after generation — iterate copy without re-buying credits for downloads ### SEO and hreflang alignment Pair localized screenshots with localized store metadata and marketing pages. Crawlers and users should see the same language across your public site, listing copy, and visual assets. StoreShots AI publishes locale-aware marketing URLs (/es/, /pl/, etc.) with hreflang alternates so search engines connect language variants of your product pages. #### Must I localize screenshots for every country? Prioritize locales that drive installs today plus strategic markets you are actively entering. Perfect coverage is less important than strong native-language hero slides in your top three regions. Sources: - [Screenshot specifications](https://developer.apple.com/help/app-store-connect/reference/screenshot-specifications) — Apple App Store Connect Help - [App Store product page](https://developer.apple.com/app-store/product-page/) — Apple Developer ## Related ClyroLabs service TestMyApps (https://testmyapps.app/) — managed Google Play closed testing and real mobile app testers. Separate product from StoreShots AI.