Localizing your app store screenshots — at minimum the caption text overlays — lifts conversion roughly 20 to 30 percent in non-English markets, and Apple reports localized listings can multiply downloads 2 to 3 times. The 80/20 move is caption-only localization: keep the same English UI in the screenshot but translate the headlines into the local language. Start with your top revenue markets (Japanese and German are usually highest-ROI), design the layout once, and swap only the caption text per language.
Why does localizing screenshots matter so much?
The conversion data is consistent: apps that localize their screenshots see roughly 20 to 30 percent higher conversion in non-English markets, and Apple itself reports that fully localized listings can lift downloads two to three times in those markets. That's not a rounding error. That's the difference between an app that travels and one that's quietly invisible outside the English-speaking world.
Think about it from the user's side. Someone in Tokyo scrolling the App Store sees your screenshots in English, with English headlines they have to mentally translate. A competitor's screenshots speak to them in Japanese. Who feels more trustworthy, more *for them*? The localized one wins before a single feature gets compared.
And here's the part that surprised me: it's often not the biggest markets by population that pay off first — it's the markets where users most expect native-language content. Japan is the second-largest app market in the world and Japanese users strongly prefer native-language listings with a high willingness to pay, which makes Japanese localization consistently one of the highest-ROI single moves you can make. Germany is similar — the largest European market, with users far less likely to engage with an English-only listing than other European audiences.
Apple actually expanded what's possible here recently: as of March 31, 2026, App Store Connect added 11 new languages, taking supported localizations from 39 up to 50. So there's more surface to localize for than there was a year ago. Apple's localization resources are the canonical reference for what's supported.
What's the difference between caption and full UI localization?
Caption localization. Your screenshot still shows the English app UI, but the text overlays — the headlines and feature callouts you designed around the device — are translated into the local language. "Track every workout" becomes its German or Japanese equivalent. The screenshot inside the frame is unchanged; only your marketing copy on top of it changes.
Full UI localization. The app interface inside the screenshot is itself in the local language — your buttons, labels, and content are translated, and you capture fresh screenshots from the localized build. This is the complete version, and it's a lot more work because it depends on your app actually being localized and you re-capturing every screen per language.
Here's the 80/20 truth: caption localization captures most of the conversion benefit for a fraction of the effort. The headlines are what carry your pitch, and translating just those — while leaving the UI in English — gets you most of the way there. Full UI localization is better, but it's the second phase, not the starting line. If your app's UI isn't even translated yet, caption-only is still very much worth doing.
I learned this the expensive way on my first app. I assumed localization meant translating everything, got overwhelmed by the scope, and did nothing — so my non-English listings stayed fully English for a year. When I finally just translated the *captions* on my existing screenshots and left the UI alone, the German numbers moved within weeks. The lesson: don't let "do it perfectly" stop you from doing the 80% that's easy.
The practical workflow is to design your screenshot layout once — frame, background, headline position — and then produce one version per language where only the caption text changes. Because the device frame and composition stay identical, you're not redesigning anything; you're swapping a text layer. In the PlayMockUp studio the device frame and background stay locked while you change the headline, so generating the German, Japanese, and Spanish versions of a screen is editing text, not rebuilding the image.
Which markets should you localize first?
Start with your top markets by revenue, not by download count. A market that sends lots of free installs but no revenue is lower priority than a smaller market that actually pays. Check your own analytics for where the money already comes from, then double down on those.
If you have no data yet, the usual high-ROI starting lineup looks like this:
- Japanese — frequently the single best localization investment. Huge market, strong preference for native content, high willingness to pay. - German — the biggest European market, with users who often won't engage with English-only listings. - French, Spanish, and Brazilian Portuguese — broad reach across Europe and Latin America, and Spanish opens up a lot of countries from one translation. - Korean and Simplified Chinese — large, valuable markets, though Chinese comes with its own store and review complexities.
A few things that go wrong if you're not careful:
Machine translation without a human check. Auto-translating captions gets you 90% there, but marketing copy is exactly where the awkward 10% shows. A headline that's grammatically fine but culturally flat won't convert. Have a native speaker glance at your translated captions — it's a short list of phrases, so this is cheap insurance.
Text overflow. A headline that fits in English will often run longer in German or Russian, and shorter in Japanese or Chinese. If your caption area is tight, translated text collides with the device frame or gets cut off. Leave margin in your headline zone so translations have room to breathe — this is one reason designing on a consistent frame helps, since you can see the overflow immediately and adjust.
Right-to-left languages. Arabic and Hebrew read right to left, which can flip the natural reading order of your whole composition. If you localize for those, mirror the layout intentionally rather than just dropping RTL text into a left-to-right design.
Cultural mismatch. Currencies, example data, and imagery should feel local. A screenshot showing dollar amounts to a Japanese user, or US-centric example names to a French one, quietly signals "this wasn't made for you."
How do you localize screenshots without redesigning everything?
1. Nail the primary set first. Put all your creative energy into one great English (or your primary market's) screenshot set — layout, lead frame, headlines, palette, device frames, all of it. This is your master. Get it genuinely good before you clone it, because every flaw gets copied into every language.
2. Lock the layout, isolate the text. Keep the device frame, background, headline position, and font fixed across every language. The *only* thing that changes per locale is the caption wording. When the layout is locked, swapping languages is editing a text field, not rebuilding a design.
3. Translate the captions in a batch. Pull all your headlines into one list, translate them per target language (machine translation as a first pass, a native speaker for a quick review), and keep them as a simple per-language table. Now generating a locale is: load the master, paste the translated headlines, export.
4. Watch the overflow and the reading direction. As you generate each language, check that nothing overflows the caption zone and that RTL languages read correctly. Fix per-language quirks, but don't redesign the whole thing — small adjustments only.
5. Export at the same store sizes per locale. Each localized set still has to hit the store's screenshot dimensions, exactly like your primary set. Because the frame defines the export size, this is automatic if you're working in a frame-based tool — you can pull the right shells from the device frame library and every localized export lands at the correct Play Store or App Store size without recalculating anything.
The reason caption-first localization is such a strong move for solo developers is the payoff per unit of effort: one well-designed master set, a list of translated headlines, and a tool where the layout stays put while the text swaps. Adding Japanese stops being a redesign and becomes ten minutes of pasting and exporting. If you want the underlying dimension targets each localized export has to hit, they're all in the Play Store screenshot sizes guide, and the conversion principles you're translating live in how to make app screenshots that get downloads.
Frequently asked questions
Does localizing app store screenshots actually increase downloads?
Yes, significantly. Apps that localize their screenshots see roughly 20 to 30 percent higher conversion in non-English markets, and Apple reports that fully localized listings can lift downloads two to three times in those regions. Even translating just the caption text while leaving the app UI in English captures most of that benefit.
Should I translate the app UI in screenshots or just the captions?
Start with the captions. Caption-only localization keeps the English UI but translates your headline overlays, and it captures most of the conversion gain for a fraction of the effort. Full UI localization — capturing fresh screenshots from a translated app build — is a stronger second phase once captions are done.
Which markets should I localize my app screenshots for first?
Prioritize by revenue, not raw downloads. Japanese is often the highest-ROI single localization thanks to a large market and strong native-language preference, followed by German, then French, Spanish, and Brazilian Portuguese for broad reach. You can design one master set and swap only the caption text per language in the [PlayMockUp studio](/create).
How many languages does the App Store support for screenshots?
As of March 31, 2026, App Store Connect supports 50 localizations after adding 11 new languages, up from 39. You don't need to localize for all of them — start with your top revenue markets and expand as the returns justify it.
How do I localize screenshots without redesigning each one?
Design one master set with the layout, frames, and headline positions fixed, then change only the caption text per language. Keeping the device frame and background locked means adding a language is editing a text layer rather than rebuilding the image, and a frame-based tool like the [device frame library](/frames) exports every localized version at the correct store size automatically.
Can I use machine translation for screenshot captions?
Use it as a fast first pass, but have a native speaker review the result. Marketing headlines are short and high-stakes, so a grammatically correct but culturally flat translation can quietly hurt conversion. Since captions are a small list of phrases, a quick human check is cheap insurance that pays off.
Build the mockup in your browser.
Drop a screenshot into a real device frame and export at the exact store size — free, no signup.