# Localized App Store Screenshot Text (Lift Downloads)

> By Lawrence Arya, Founder & CEO of VP0. Published 2026-05-30, updated 2026-06-02. 4 min read.
> Source: https://vp0.com/blogs/app-store-screenshot-localized-text-ui-figma

The captions do real conversion work, so they should speak the user's language.

**TL;DR.** App Store screenshot captions sell the app, and English-only captions convert worse in other markets. Localize the text per market (real translation, kept short), design the template with the caption as a separate swappable layer, and use the App Store's per-locale screenshot slots. Localizing well can lift downloads around 1.5x in those markets.

App Store screenshots usually carry caption text ("Track every habit," "Pay in one tap"), and if that text stays English in every market, you are leaving downloads on the table. The short answer is, localize the caption text on your screenshots per market, design the screenshot template so swapping languages does not break the layout, and prioritize the markets that matter to you. Build the screenshot frames from a free VP0 design with text as a separate, swappable layer. The captions do real conversion work, so they should speak the user's language.

## Why localized screenshot text matters

Most App Store visitors decide from the first few screenshots, and the caption is what tells them why the app is worth it. If that caption is in a language they do not read, it converts worse, and the App Store reaches users in dozens of languages across many regions, as Apple's [product page](https://developer.apple.com/app-store/product-page/) guidance details. Localizing the metadata and screenshot text can lift downloads meaningfully in non-English markets, by some estimates on the order of [1.5x](https://developer.apple.com/localization/) in markets where you localize well. The work is mostly disciplined: separate the text from the artwork so you can swap it per locale, and translate it properly (real translation, not machine output for the headline).

## How to set up localized screenshots

VP0 is a free iOS design library for AI builders. Build your screenshot template from a VP0 design: the device frame, the screen image, and crucially the caption as a separate text layer, not baked into the image. Then for each target locale, swap the caption text (translated by a person for the key markets) and export. Keep captions short so they fit when a language runs longer (German and others expand). Upload per-locale sets in [App Store Connect](https://developer.apple.com/app-store-connect/) so each market sees its own screenshots, and check the layout in each language before publishing. Prioritize the few markets that matter rather than all forty. For the screenshot fundamentals, see [App Store screenshots that get more downloads](/blogs/app-store-screenshots-that-get-more-downloads/).

## Localized screenshot checklist

Here is what to get right.

| Item | What to do |
|---|---|
| Text layer | Separate from artwork, swappable |
| Translation | Real, not machine, for headlines |
| Length | Short, survives longer languages |
| Per-locale slots | Each market gets its own set |
| Priority markets | Localize the ones that matter first |

## A worked example

Say your app is taking off in Germany and Brazil. Build one screenshot template from a VP0 design with the caption as a text layer. Create a German set (properly translated, captions kept short so they do not overflow) and a Brazilian Portuguese set, and upload each to its locale's screenshot slots in App Store Connect. Leave smaller markets in English for now. The German and Brazilian users now see captions they actually read, and downloads in those markets rise. For the listing text alongside screenshots, see [how to write an App Store description that ranks](/blogs/how-to-write-an-app-store-description-that-ranks/); to translate a whole web product for these markets, [web app to iOS app UI kit Figma](/blogs/web-app-to-ios-app-ui-kit-figma/).

## Common mistakes

The most common mistake is baking caption text into the screenshot image, so localizing means redoing the artwork each time. The second is machine-translating headline captions, which often reads awkwardly in the very spot that sells the app. The third is captions that overflow when a language expands. The fourth is trying to localize every market at once instead of the few that matter. The fifth is forgetting the App Store's per-locale slots, leaving every market with the English set.

For a cross-check from outside Apple, accessible UI follows the [W3C WCAG standard](https://www.w3.org/WAI/standards-guidelines/wcag/), the international baseline for inclusive design.

## Key takeaways

- Screenshot captions do conversion work; English-only captions cost downloads in other markets.
- Localizing screenshot text and metadata can lift downloads meaningfully (around 1.5x in well-localized markets).
- Keep caption text as a separate, swappable layer so localizing does not redo the artwork.
- Translate headlines properly, keep them short, and prioritize the markets that matter.

## Frequently asked questions

How do I localize App Store screenshot text? Build the screenshot with the caption as a separate text layer (not baked into the image), translate it properly per market, keep it short so it survives longer languages, and upload each set to the App Store's per-locale screenshot slots.

Does localizing screenshots actually increase downloads? Yes, especially in non-English markets, where a caption in the user's language converts better. Localized metadata and screenshots can lift downloads meaningfully, on the order of 1.5x in markets you localize well.

Can I machine-translate the captions? For the key markets, use real translation for the headline captions, the spot that sells the app. Machine output often reads awkwardly there and undercuts conversion.

Should I localize every market? No. Prioritize the few markets that matter to you, localize those well, and leave the long tail in English until they are worth the effort.

## Frequently asked questions

### How do I localize App Store screenshot text?

Build the screenshot with the caption as a separate text layer (not baked into the image), translate it properly per market, keep it short so it survives longer languages, and upload each set to the App Store's per-locale screenshot slots.

### Does localizing screenshots actually increase downloads?

Yes, especially in non-English markets, where a caption in the user's language converts better. Localized metadata and screenshots can lift downloads meaningfully, on the order of 1.5x in markets you localize well.

### Can I machine-translate the captions?

For the key markets, use real translation for the headline captions, the spot that sells the app. Machine output often reads awkwardly there and undercuts conversion.

### Should I localize every market?

No. Prioritize the few markets that matter to you, localize those well, and leave the long tail in English until they are worth the effort.

---
*Published on the [VP0 Journal](https://vp0.com/blogs). Free to read, index and cite with attribution.*