How to localize App Store screenshots
Localizing screenshots means uploading a separate set for each language in App Store Connect and Google Play Console: the same design and story, with the captions in that language.
Why bother
Both stores ask for it. Apple: "If your app is available in multiple languages, make sure to localize your app description, keywords, app previews, and screenshots, for each of the markets in which you offer your app." Google tells developers to localize screenshot taglines and text overlays for each market.
Screenshots are often the first thing people see on your product page.
Step 1: Pick your languages
App Store Connect supports metadata in about 50 languages and locales, from Arabic to Vietnamese. Each country has a default language, and some have more. A few examples from Apple's table:
| Country | Default | Also supported |
|---|---|---|
| Germany | German | English (U.K.) |
| Japan | Japanese | English (US) |
| Switzerland | German | English (U.K.), French, Italian |
| Canada | English (Canada) | French (Canada) |
| Mexico | Spanish (Mexico) | English (U.K.) |
| Brazil | Portuguese (Brazil) | English (U.K.) |
Start with the countries where you already see downloads or revenue in App Store Connect and Play Console. See the full list of App Store localization languages.
Step 2: Decide what to translate
- Captions on the screenshots (the headline text): yes, always.
- The app UI inside the phone: only if your app itself is localized. If it isn't, keep the UI in its original language. Showing a translated UI the app doesn't have sets the wrong expectation.
- Store text: name, subtitle, keywords, promotional text and description on the App Store; title, short description (80 characters) and full description on Google Play. Keywords in particular should be researched per language, not translated word for word.
Step 3: Plan for what breaks
- Length. German and French captions often run longer than English. Leave room, or allow a smaller font size.
- Line breaks. Japanese and Chinese don't use spaces, and Thai doesn't separate words with spaces either, so automatic line breaking can split words in the wrong place. Check every CJK and Thai caption by eye.
- Direction. Arabic and Hebrew read right to left. Text alignment, and often the layout, should mirror.
- Fonts. Make sure your font has the glyphs; otherwise fall back to a system font for that script.
- Proofreading. Get a native speaker to check at least your top 2–3 markets.
Step 4: Export every size
Each localization needs its own screenshots for each device size you support. Apple allows 1 to 10 per size, with no transparency. If your UI is the same everywhere, you can provide just the largest required size and let App Store Connect scale it down. Full tables: App Store screenshot sizes and iPhone Duo sizes.
Step 5: Upload per language
- App Store Connect: open the app version, switch the language menu at the top of the page to each localization, then upload that language's screenshots per device size.
- Google Play Console: under Store presence > Main store listing, add translations, then upload the screenshots for each language.
Three ways to do it
| Method | Good for | Watch out for |
|---|---|---|
| By hand in Figma / Sketch | A few languages, full control | Time: languages × sizes × screenshots adds up fast |
| fastlane snapshot + frameit | Teams with UI tests and .strings files; free | You supply every translation; limited design control |
| A localization tool (HelloPack, AppScreens, others) | Many languages without redoing the design | Check how it handles length, CJK and RTL, and what it costs per release |
How HelloPack does it: upload the screenshots you already have (1 to 10). HelloPack puts each one, untouched, in a device frame on a background in your app's colours, with your caption translated above it, for iPhone 6.9″, 6.5″, iPhone Duo outer and inner, and Google Play phone, in up to 23 languages. It also writes the store listing per language. Only the captions are translated; the app UI stays as you designed it. See 2 languages free, no card needed. Then $19 once.
Need just the sizes? The free iPhone Duo screenshot resizer runs in your browser with no signup.
Localize your screenshots in your own design. Upload the screenshots you have and see 2 languages free, no card needed.
Get your free preview Free screenshot resizerFAQ
Do I have to localize screenshots for every language? No. Without a localized set, the store falls back to another language you provide. Localize for your most important markets first.
Should I translate the app UI in the screenshot? Only if the app itself is localized for that language.
How many screenshots per language? App Store: 1 to 10 per device size. Google Play: up to 8 per device type, and at least 4 for some recommendation slots.
Sources (checked 18 Oct 2026): Apple, Creating your product page · Apple, App Store localizations · Apple, Screenshot specifications · Google, Add preview assets.