Create your app store visuals easily

The App Store and Google Play use different pixel dimensions, and Apple updates its required device targets as new iPhones ship, so treat exact numbers as something to confirm before every release rather than memorize. On the App Store you export one set of iPhone screenshots at the largest current display size, currently the 6.9-inch iPhone at 1290 by 2796 pixels, and, if your app supports iPad, a 13-inch iPad set at 2064 by 2752 pixels. Apple scales that largest set down to smaller devices automatically, so you no longer need a separate export for every screen. You can upload up to 10 screenshots per device size and per language. Google Play is more forgiving on dimensions: phone screenshots must sit between 320 and 3840 pixels on each side with a 16:9 or 9:16 aspect ratio, and you upload between 2 and 8 of them.

Rather than track these numbers by hand, use our free screenshot size calculator to get the current export dimensions for every device target, and the icon size guide for the exact icon files each store expects. Both live in the free ASO tools and need no account. Exporting at the right size from the start matters more than it sounds: an image a few pixels off the required dimension is rejected at upload, and a low-resolution icon looks amateur next to competitors in the same search results.

The most important rule is that most people decide from the first one or two screenshots, so your strongest message has to be in frame one. Do not open with a plain login screen or an empty state. Lead with the single clearest benefit of your app, shown inside a device frame with a short caption above it. Then treat the carousel as a story: each screenshot covers one benefit, in priority order, with a consistent caption style, background, and font throughout. A set of five coherent frames reads as a designed product; five raw screenshots with no captions read as an afterthought.

• Show the value in the first frame. Assume the viewer sees only one screenshot and make it count.
• Add a short benefit caption to each frame, written as an outcome for the user, not a feature name.
• Keep one template: same background, caption placement, type, and device frame across every screenshot.
• Use real content, not lorem ipsum. Believable data makes the app feel finished and trustworthy.
• Respect the safe area. Keep captions and key UI away from the rounded corners and the notch region.

Localizing visuals means more than translating the caption text, though translated captions are the baseline and both stores let you upload a different screenshot set per language. The captions on your screenshots are marketing copy, so they should be written for each market rather than machine-translated word for word, and the in-app content shown in the frames should match the language too. A Japanese user who sees English UI inside your screenshots assumes the app itself is English only. Where it matters, adapt the imagery as well: currency, date formats, and culturally specific examples all signal that the app was built for that audience. Localized visuals consistently lift conversion in non-English markets more than almost any other single change.

The efficient way to do this is to build one master template with the caption text as an editable layer, then swap the language and the underlying screen for each locale while everything else stays fixed. That keeps the set visually consistent across markets and turns localization into a text-and-screen swap rather than a redesign. If you are planning a multi-market launch, our guide to managing multiple languages in a mobile app covers the listing side end to end.

You do not need Photoshop or a designer to make a professional set. The category of tools that solves this is the screenshot generator: you drop your raw app captures into a device frame, add a caption and background, and export at every required store size in one pass. Mockup generators do the framing, template galleries give you a starting layout, and the best tools export the App Store and Google Play sizes together so you never hand-resize. The workflow below turns a folder of raw screen captures into a complete, localized visual set.

• Screenshot and mockup generators: place raw captures into device frames with captions and backgrounds, then export every store size at once.
• Template galleries: start from a proven layout instead of a blank canvas, then restyle it to your brand colors.
• Design tools with export presets: general design apps work if you set up artboards at the exact required dimensions yourself.
• Releasely's visual generation: create framed, captioned, correctly sized screenshots and icons inside the same workspace you use to build and publish, so visuals and store metadata ship together.

Here is a repeatable sequence that takes you from raw app screens to an upload-ready, localized set. Do it once carefully and every future release is a quick edit of the same template.

1. Capture clean screens from the app on a device or simulator, using real, believable content and no debug overlays.
2. Finalize the app icon at the highest resolution, then confirm the exact per-store files with the icon size guide.
3. Pick your five to eight strongest screens and order them by benefit, with the single best one first.
4. Build one master template: device frame, background, caption style, and a text layer you can edit per screen and per language.
5. Write a short benefit caption for each frame, phrased as a user outcome rather than a feature label.
6. Export at every required size using the screenshot size calculator so nothing is rejected at upload.
7. Duplicate the set per language, swapping captions and in-app content while keeping the layout fixed.
8. Add the Google Play feature graphic and, if it helps, a 15 to 30 second app preview video.

Consistency comes from treating the visual set as a reusable template, not a one-off deliverable. Keep the master file with editable caption and screen layers, and version it alongside your app. When the UI changes, you re-capture the affected screens and re-export, rather than rebuilding the whole set. When you add a language, you duplicate and swap. This is also where doing visuals inside your release workflow pays off, because the icon, screenshots, and metadata move together every time you cut a version instead of drifting apart across separate files and tools.

The App Store requires a set of iPhone screenshots at the largest current display size, currently the 6.9-inch iPhone at 1290 by 2796 pixels, and a 13-inch iPad set at 2064 by 2752 pixels if your app supports iPad. Apple scales the largest set down to smaller devices automatically. You can upload up to 10 screenshots per device size and per language, all managed in App Store Connect. Use the screenshot size calculator to confirm the current dimensions before each release, and see improving ASO in App Store Connect for where visuals fit into the wider listing.

No, a preview video is optional on both the App Store and Google Play, and many successful apps ship with screenshots only. A 15 to 30 second video helps most when the core value is motion-based or hard to show in a still, such as a game or a complex flow. If you add one, front-load the payoff in the first few seconds, since most viewers do not watch to the end. Start with strong screenshots first, then add video if you have the time.

Yes. A screenshot generator handles the device frames, captions, backgrounds, and correct export sizes for you, so the design skill is reduced to picking your strongest screens and writing clear benefit captions. Start from a template rather than a blank canvas, keep one consistent style across the set, and export at the exact required sizes. Many apps with excellent listings never involve a dedicated designer at all; they use a repeatable template and a generator.

Upload enough to tell a complete story without padding, which for most apps means five to eight strong frames. The App Store allows up to 10 per device size and Google Play allows up to 8, but quality beats quantity. Every screenshot should earn its place by showing a distinct benefit. Lead with your strongest frame, since many people decide before scrolling, and stop once you start repeating yourself. For more on ordering and testing, see improving your app store listing conversion.