Storeboard/Guides/Should you localize your screenshots?

Should you localize your App Store screenshots?

Localization 16 July 2026 · 5 min read

"Localize everything" is bad advice. So is "English is fine, everyone speaks English." Here's how to tell which situation you're actually in.

Start with what the screenshot is for

Your first two screenshots are the only ones most people ever see — they're what appears in search results, before anyone taps through to your page. They are not decoration. They are the argument for why someone should download your app, delivered in about three seconds.

Which reframes the question. It isn't "should I translate my captions?" It's "should my argument be in a language this person reads?" Put that way, the answer is obvious wherever you have real users.

When localization multiplies your downloads

• You already have installs in that market. The demand is proven — you're just removing friction from people who are already finding you and bouncing.
• Your category is everyday consumer software. Utilities, health, photo, productivity — the buyer isn't a developer and won't push through an English product page.
• Your value proposition needs explaining. If your app isn't self-evident from an icon, the caption is doing the work, and it must be readable.
• Your competitors are localized and you aren't. On a search results page, you're the one that looks foreign.

When it does approximately nothing

• Nobody in that market has heard of you. Localization multiplies existing demand. It rarely creates it. Zero × translated captions is still zero.
• Your audience is developers. The one genuinely English-fluent audience on earth. Localize last.
• Your screenshots have no words. If your captions are decorative, translating them changes nothing — fix the captions first.
• Your English listing is weak. Fifteen translations of a vague subtitle is fifteen vague subtitles. Fix the source.

The English variants are the free lunch

Before you think about Japanese, do English (UK), English (AU) and English (CA). Your copy is already written. The captions need almost no changes — maybe a spelling or two. And each one is a separate localization with its own 100-character keyword field targeting a different storefront.

Same effort as a coffee break, three extra keyword fields, four storefronts covered. More on why that matters →

The trap: localizing the wrong thing first

Teams reliably localize in exactly the wrong order. They translate the 4,000-word description — which Apple doesn't even index and almost nobody reads to the end — and leave the screenshots in English.

Reverse it. Screenshots and subtitle first; they're where the decision happens. Description last.

What actually breaks

Two things, both design problems rather than language problems:

Text gets longer. Translated copy is longer than English roughly 80% of the time. German is famously brutal — a caption that fits on one line in English becomes two, and your careful layout falls apart. Design captions with slack from the start.

Nobody looks at the output. The failure mode isn't a bad translation; it's a caption overflowing its frame in a language you don't read, shipped to a store you never open. Look at every language before you upload — even if you can't read them, you can see when something's broken.

The honest summary

Localization is not a growth hack — it's removing an obstacle you put in front of people who already wanted your app. That makes it very high-leverage where you have traction, and close to worthless where you don't.

So: do the English variants today, because they're nearly free and they buy keyword fields. Then open your analytics, find the countries where people are already downloading despite the English, and start there. Ambition is a bad targeting strategy; evidence is a good one.

Keep reading