DEV Community

ScreenParcel
ScreenParcel

Posted on

App Store & Google Play Screenshot Dimensions in 2026 (Cheat Sheet + Multi-Locale Overflow Gotchas)

#ios #android #aso #indiedev

Shipping a localized App Store or Google Play listing still fails on two boring details: the exact pixel sizes each store wants, and text that overflows once you leave English. This is the 2026 cheat sheet I keep open while exporting release packs.

ScreenParcel does not auto-translate your copy. You (or your translator) supply headlines/subtitles; the browser tool lays them out across locales and store sizes, checks overflow, and exports a clean ZIP.

Exact sizes that matter in 2026

Apple App Store Connect (portrait)

Device class Pixels (portrait) Notes
iPhone 6.9" 1320 × 2868 Primary phone master for newest iPhones
iPhone 6.5" 1284 × 2778 Still accepted; often cascaded from 6.9"
iPhone 6.3" 1206 × 2622 Newer mid-size phone slot
iPad 13" 2064 × 2752 Required if you ship iPad screenshots

Practical rule for solo apps:

  1. Design / export the 6.9" iPhone set first.
  2. If you support iPad, also export 13" iPad.
  3. Let App Store Connect cascade smaller iPhone sizes from the 6.9" masters when the UI allows — still verify the first three screenshots look sharp on a physical phone.

Up to 10 screenshots per locale. The first 3 appear in search results — treat those as paid ad creative.

Google Play

Spec Value
Aspect 16:9 or 9:16
Min side 320 px
Max side 3840 px
Count 2–8 per device type

A clean 1080 × 1920 (9:16) set covers phones. Prefer exporting Play from the same 6.9" master with a center crop rather than maintaining a second artboard forever.

Locale codes you will actually type

Market BCP-47 / store locale Watch-outs
US / UK en-US / en-GB Spelling differs; keep one master if budget is tight
Japan ja No spaces — line breaks on phrase boundaries
Germany de-DE +20–35% length, compound nouns
France fr-FR +15–25% length
Brazil pt-BR Not pt-PT
Spain / LatAm es-ES / es-MX Pick one primary
Korea ko Needs larger optical size than Latin
TW / HK zh-Hant Traditional, not Simplified
Arabic ar RTL; mirror layout, not just glyphs
Turkey tr Fast-growing, low competition

Multi-locale overflow gotchas (the ones that burn releases)

  1. German compounds blow past English one-liners. Leave ~30% horizontal slack or allow controlled font shrink with a floor (never below readable).
  2. CJK is shorter in character count but needs a larger font than Latin for the same perceived size. Your Latin display font almost never has CJK — set an explicit Noto / system CJK fallback.
  3. Arabic / Hebrew are RTL. Mirroring only the text box is not enough if your template has chevrons, progress bars, or phone bezels with assumed LTR.
  4. CSV / JSON import beats hand-typing 10 locales. Keep a column per locale for headline and subtitle, UTF-8, no Excel “smart quotes”.
  5. Line breaks: never wrap mid-word in German; never wrap mid-phrase arbitrarily in Japanese. Preview every locale at export size, not just in the editor canvas.
  6. First three frames win. If locale #7 looks perfect but frame 1 overflows in German, you still lose the search-result impression.

A sane solo-dev workflow

  1. Write English headlines at 3–6 words.
  2. Get translations (human or your usual process) into a CSV/JSON — do not paste from a chat window one cell at a time.
  3. Drop screenshots + copy into a layout tool that can render all locales × all five store sizes and flag overflow before you upload.
  4. Export a ZIP with folders per locale, upload with the next binary (iOS screenshots still ride with a version).

I built ScreenParcel for exactly this loop: upload screenshots, import or type localized headlines/subtitles, render iPhone 6.9"/6.5"/6.3" + iPad 13" + Play locally in the browser with CJK/RTL fallbacks and overflow checks, then download a clean ZIP. Free = up to 2 locales (watermarked). Paid = $9 Release Pack or $19 30-day Pass.

Also published as a living reference on the product site:

Checklist before you hit Submit

  • [ ] 6.9" iPhone + 13" iPad (if applicable) exported at exact pixels
  • [ ] Play 9:16 set present
  • [ ] Every locale previewed for overflow (DE / JA / AR at minimum)
  • [ ] CSV/JSON matches store locale codes
  • [ ] First 3 screenshots sell the benefit, not the feature list

Gotchas change slower than device names — bookmark the size table, automate the export, and spend your afternoon on copy quality instead of Figma frame babysitting.

Top comments (0)