I was about to redo our store screenshots when I opened my old size notes. They said "6.7-inch, 1290 × 2796." App Store Connect, however, was asking for something else. The note was months old.
Here is what I'd like to say first: a screenshot size table starts going stale the moment you copy it down. The earlier version of this guide was exactly that. This time I re-read the official pages as of October 2026, replaced the numbers, and rebuilt the Figma setup so it's easy to fix when the specs move again.
Check the specs on the official page before you design
I keep a handful of wallpaper apps in the stores, so I swap screenshots a few times a year. The size is the one thing I always verify first. I've been burned by building a whole set from an old note and having it rejected at upload—my stomach still drops a little at the memory.
What App Store Connect accepts
According to the App Store Connect screenshot specifications, the main rules today are:
| Device | Required? | Accepted sizes (px) |
|---|---|---|
| iPhone with Dynamic Island (medium display) | At least one | 1179 × 2556 or 1206 × 2622 (portrait); swap the sides for landscape |
| iPad 13-inch display | If the app supports iPadOS | 2064 × 2752 or 2048 × 2732 (portrait); swap the sides for landscape |
Three more points matter:
- You can upload up to 10 screenshots per device size.
- Files must be JPEG, JPG or PNG, with no alpha channel or transparency.
- If your UI is the same across devices and localizations, the highest required resolution is enough; App Store Connect scales it down for smaller devices.
My earlier advice to prepare 6.5-inch and 5.5-inch sets "for coverage" is the wrong default now. Make one set at the largest size, and add device-specific sets only where the layout really differs.
What Google Play accepts
The Play Console Help page is looser than Apple's:
| Item | Requirement |
|---|---|
| Count | At least 2 across device types to publish; up to 8 per device type |
| Format | JPEG, or 24-bit PNG without alpha |
| Dimensions | 320–3840 px per side; the long side at most twice the short side |
| Tablets and Chromebooks | At least 4; 1080–7680 px per side, 9:16 or 16:9 |
| For promotion eligibility | At least 4 for apps, 1080 px minimum per side, 9:16 or 16:9 |
The old "8 MB per file" figure does not appear on the page I checked for phone screenshots. Rather than hard-coding a number the docs don't state, I rely on the console's upload warnings.
Build the template in Figma
With the numbers settled, the plan is simple: one master frame, and every export derived from it.
Frames and pages
Create the App Store master at one of the accepted sizes—say 1206 × 2622—rather than the old 1290 × 2796. Make the Google Play version a separate frame at 1080 × 1920 with the same design.
Split pages like this so adding a language never gets confusing:
- Template: master frames and components
- ja / en / …: one page per language
- Export: frames used only for output, named with size and language code
I name frames like appstore_1206x2622_en_01—store, size, language, sequence—so a batch export already tells me the upload order.
Treat device frames as decoration
Plugins that generate device frames exist in plenty, but the numbers shift as new models appear. Always compare the plugin's screen area with your own frame. If you see a thin gap above or below your pasted screen, a size mix-up is the quickest explanation.
Paste in real captures from a device or simulator. If your app was built with Rork, the exported PNG works just the same. Just don't upload transparent PNGs: App Store rejects alpha channels, so include a background colour when you export.
Design text from the longest language
I put the headline in the top 20–30% of the frame. On a ~1200 px wide frame I start around 56–72 px for headlines and 32–40 px for supporting text, then check legibility on a real phone.
The real problem is length. English often runs 1.2–1.3× Japanese, and German can exceed 1.5×. Early on I polished a Japanese layout, dropped in the English, watched it spill to four lines, and rebuilt everything. Now I paste the longest translation into the master first and design for that width.
Wrap text in Auto Layout so the background grows with extra lines. It cuts the post-translation adjustments dramatically.
Rolling out languages
My order of work:
- Finish the master in Japanese: colours, spacing, components.
- Test the longest language (often German or Russian) for overflow before anything else.
- Duplicate the page and replace text layers only.
- Export and upload per language in App Store Connect and Play Console.
I only swap text—never position or size. If I feel the urge to nudge something, I fix the master instead; otherwise slightly different designs multiply per language.
For going wider, see one capture scaled down for a multilingual App Store pipeline and localizing Google Play screenshots into 16 languages. If you're still choosing a tool, the Figma, Stitch and Canva comparison is a decent starting draft.
Export and pre-submission check
Select the frames on the Export page and export as PNG at 1x. The frame dimensions are already the store's required sizes; 2x produces off-spec files that get rejected.
Before submitting, confirm four things:
- The dimensions match one of the sizes in the tables above.
- No transparency remains (App Store forbids alpha).
- The count is within limits and the first image carries your strongest feature.
- Text in every language still reads when scaled down to phone size.
Do the last check on a real device, in the actual store listing. Text that looked fine on my monitor has turned to mush in small search cards more than once.
Wrapping up
Check the numbers on the official page, build one master frame, derive everything from it—those three habits cut the work on the day a spec changes.
Never copy the numbers down; re-read them every time. Fix the design in one place only. I intend to keep that line.
Your next step: compare the sizes you're using today with the current official pages. If anything is off, start by correcting the master frame.