How to Localize Your App Store Screenshots (2026)

A screenshot that converts beautifully in English can fall flat in Tokyo or São Paulo — not because the app is worse, but because the caption is in a language the shopper doesn't read, the currency looks foreign, and the sample data feels imported. The App Store and Google Play both let you upload a different set of screenshots per language, and shoppers browsing in their own language see conversion lift when the imagery speaks to them directly.

To localize app store screenshots means creating language- and market-specific versions of your screenshot set so each store visitor sees captions, sample data, and formatting that feel native to them. This guide covers which languages to prioritize, what actually needs to change beyond the words, and how to produce every version without blowing your size specs or your weekend. It builds on our screenshot pillar — if you haven't nailed your base set yet, start with app store screenshot sizes and come back.

Should you localize screenshots at all?

Not every app needs it on day one. Localization pays off most when:

You already see meaningful downloads from non-English markets in your analytics.
You're actively targeting a specific country (a launch, an ad campaign, a partnership).
Your category is competitive in that market and rivals are localized.

If you're a brand-new app with no international traction yet, localize your store text first (title, subtitle, keywords, description) — that's cheaper and drives discovery — and add localized screenshots as data tells you where demand is. Text localization and screenshot localization aren't the same project; the text feeds search ranking, while screenshots convert the visit. Our ASO playbook for indie developers covers the text side in depth.

Which languages should you prioritize?

You don't need all 40 App Store languages. A focused shortlist captures most of the upside. A sensible priority order for a first localization pass:

Priority	Languages	Why
1	English (US/UK)	Your baseline and largest single market for most apps
2	Spanish, French, German	Large App Store spend and broad reach across regions
3	Japanese, Korean, Simplified Chinese	High-value markets where English screenshots underperform sharply
4	Portuguese (Brazil), Italian	Fast-growing, strong mobile-first audiences

Let your own numbers override this table. If your analytics show a spike in installs from Brazil, Portuguese jumps to the front regardless of the generic ranking. Localize where you have evidence of demand or a concrete plan to create it.

Translating vs. localizing: what actually changes

Swapping the caption text is only the first layer. True localization adapts everything inside the frame so nothing reads as "translated from English":

Caption copy — translated by a native speaker, not just a machine. Idioms and value props rarely translate literally.
In-app sample data — names, cities, and content shown on the screen should match the market (use local names, not "John Smith").
Currency and numbers — show ¥, €, or R$ where relevant, with correct formatting (1.000,00 vs 1,000.00).
Dates and units — DD/MM vs MM/DD, metric vs imperial, 24-hour vs 12-hour clocks.
Text length — German runs ~30% longer than English; Japanese far shorter. Captions that fit in English can overflow or look sparse elsewhere.
Imagery and color — occasionally a photo or icon carries different connotations in another culture; check anything region-sensitive.

The text-length issue is the one that quietly breaks layouts. A headline that fits on one line in English wraps to three in German and crowds the device frame. Design your caption zones with room to breathe so translations don't force a redesign.

How to keep every localized set on-spec

This is the part that trips people up: localized screenshots still have to meet the exact same store dimensions as your originals. Only the content inside changes — the pixel size never does. That means every language needs its own file at:

Device / store	Dimensions
iPhone 6.9"	1320×2868
iPhone 6.7"	1290×2796
iPad 13" (M4)	2064×2752
Google Play phone	1080×1920

Multiply those by five languages and three screenshots each and you're suddenly managing dozens of exact-size exports. Doing that by hand in a general design tool is where mistakes creep in — one off-spec file and the whole locale gets rejected.

This is exactly what a purpose-built tool removes. In the App Store screenshot generator, you build your base layout once with device frames, backgrounds, and caption text, then duplicate it per language, swap the text and sample data, and export each version at the correct store size automatically. Because the canvas is locked to store dimensions, every localized set comes out on-spec — no per-language resizing, no rejected uploads. If you want to compare tools before committing, see our roundup of the best app store screenshot generators.

A repeatable localization workflow

Here's a workflow that scales from two languages to ten without chaos:

Lock your base set (English). Finalize layout, caption zones, and design before you translate anything. Changes made after localization multiply across every language.
Extract your captions. Put every caption in a simple spreadsheet, one row per screenshot per language. This becomes your single source of truth.
Get native translations. Use a native speaker or a professional service for anything customer-facing. Machine translation is fine for a first draft but should be reviewed.
Localize the in-frame data. Update names, currency, dates, and sample content per market — not just the caption.
Duplicate and swap in your editor. Copy the base canvas per language, drop in the translated text and localized data, and check for overflow.
Export at exact store sizes. One correctly sized file per screenshot per language for each device class you support.
Upload per language in the console. In App Store Connect and Play Console, each language has its own screenshot slot — attach the matching set.
QA in-store. Preview each localized listing before release to catch truncation or the wrong set in the wrong slot.

Keep the spreadsheet. When you ship a feature and update your screenshots, you re-run steps 4–7 instead of rebuilding from scratch.

Common localization mistakes to avoid

Machine-translating and shipping it. Obvious auto-translation reads as low effort and can hurt trust. Always have a human review.
Leaving English sample data in a "localized" set. A German caption over an app screen showing dollars and American names breaks the illusion instantly.
Ignoring text expansion. Captions that overflow the frame look broken. Design with slack.
Resizing instead of re-exporting. Scaling an English file to "fix" a layout throws off the dimensions. Export fresh at spec.
Localizing screenshots but not the store text. If the description and keywords are still English, you lose the discovery that would've sent shoppers to those screenshots in the first place.

Localization is one of the highest-leverage screenshot upgrades once you have international traction, precisely because most indie competitors never bother. When a shopper in a non-English market sees a listing that speaks their language down to the currency symbol, you stand out. For the design fundamentals that make each localized set convert, revisit how to make app store screenshots that convert, and check the pricing page to see what exporting localized sets costs.

Frequently asked questions

Do I have to localize screenshots for every language?

No. Start with the languages that already drive your downloads or the markets you're actively targeting, then expand. Localizing your top three to five languages captures most of the upside without producing dozens of image sets.

What's the difference between localizing and just translating screenshots?

Translating swaps the caption text into another language. Localizing goes further — it adapts currency, dates, names, sample data, and sometimes imagery so the screenshot feels native to that market rather than machine-translated.

Do localized screenshots have to be the same size as the originals?

Yes. Every localized set must still meet the exact store dimensions — for example, 1320×2868 for the iPhone 6.9" display. Only the text and content inside the frame change; the pixel dimensions stay identical across all languages.

Tools mentioned in this guide: App Store Screenshot Generator, App Privacy Policy Generator.