Localizing App Store screenshots — a workflow that scales past 3 languages
App Store screenshots are per-locale: every language your store listing supports can carry its own set, and localized screenshots consistently lift conversion in non-English markets. The problem is arithmetic — 6 slides × 2 devices × 9 languages is 108 exact-size PNGs. This is a workflow that keeps that manageable. Last verified: June 2026.
The principle: one layout, translated data
The mistake that makes localization expensive is treating each language as its own design file. Then every layout tweak multiplies by your locale count, and the sets drift apart. The workflow that scales is the opposite:
- Design once in your source language — layout, device frames, colors are shared.
- Treat captions as data — a table of
slide × language, not text baked into images. - Swap screenshots per language by convention — a filename pattern, not manual placement.
- Export everything in one pass, already grouped by locale and device.
Step 1 — captions as a translation table
Export your captions as a CSV or JSON template with one labeled column per language, source included:
slide, slideId, field, en, ko, de
1, …, headline, "Scan anything", "무엇이든 스캔", "Alles scannen"
1, …, subheadline, "PDF in one tap", "한 번에 PDF로", "PDF mit einem Tipp"
2, …, headline, "Organize instantly", "", ""A file like this is something a translator, a spreadsheet, or an AI chat can all work on. No API keys needed: paste a translation prompt plus the template into ChatGPT, Claude, or Gemini, get the filled file back, re-import it. Empty cells are simply skipped, so you can translate incrementally.
Step 2 — per-language screenshots by filename
If your app's UI is localized, the screenshot inside the device frame should be too — an English caption above a Korean home screen looks broken. Capture each language's UI (simulator + your capture script of choice), then name the files so a bulk import can route them:
01-home.en.png → slide 1, English
01-home.ko.png → slide 1, Korean
02-add-pdf.en.png → slide 2, English
02-add-pdf.de.png → slide 2, GermanLeading digits pick the slide, the suffix before the extension picks the locale, and the middle is a free description for humans. Languages without an override fall back to the source screenshot — you can localize the two slides that matter and leave the rest.
Step 3 — preview before you export 100 files
Text expands: German and French headlines run ~30% longer than English; Korean and Japanese are often shorter but break differently. Before exporting, flip the canvas through each locale and check that nothing clips or collides. Catching one overflowing German headline before export beats regenerating the whole set after.
Step 4 — export grouped by locale and device
App Store Connect wants 1–10 screenshots per device slot, per locale, at
exact pixel sizes. Export the full
matrix in one pass, laid out either for humans (ko/iphone/1.png) or for
fastlane deliver
(screenshots/ko/iphone_01.png) so the upload is one command instead of an
afternoon of dragging.
01-name.locale.png convention, preview any language on the canvas, and
export every locale's exact-size set as a ZIP. Runs fully in your browser — no account,
images never leave your machine. →
FAQ
Which languages are worth localizing screenshots for?
Start from your store listing's existing locales and your install data. Japan, Korea,
Germany and France are the classic high-impact markets where English-only screenshots
measurably underperform.
Do I have to localize the screenshot images themselves?
No — caption-only localization over source-language UI shots is a common first step.
Localize the in-frame UI for your top markets when the lift justifies the capture work.
Can different languages have different layouts?
In this workflow, no — layout is shared and only text and screenshots vary. That
constraint is what keeps 9 languages maintainable; per-locale art direction puts you
back in the every-tweak-times-nine world.