Localize your App Store screenshots

Updated November 15, 2026

Localized screenshots help in each market, but the work multiplies with every language. This workflow keeps it manageable from 2 languages to as many as your app supports.

The workflow

  1. Design once, in the source language

    Pick one reference size and one language. Keep every text in a strings table rather than baked into images, so it can be replaced later.

  2. Capture the app in each language when its interface appears in the screenshot

    Text inside your app’s interface is part of the screenshot. Capture those screens per language, or you ship an English interface under a translated headline.

  3. Export what is missing

    Export only the strings that have no translation yet. A CSV is the simplest format to hand to a translator or a teammate.

  4. Translate

    Translate yourself, send the file to a translator, or use assisted translation. Keep captions short: they have to fit on a slide in every language.

  5. Import the translations

    Import the CSV. Run a dry run first to see what will change, then confirm. Nothing is written until you do.

  6. Check coverage and layout

    Look for titles that overflow, characters a font does not cover, and screenshots still in the wrong language. Fix blockers language by language.

  7. Map languages to App Store locales

    One language can serve several App Store locales: English covers en-US, en-GB, en-AU and en-CA, French covers fr-FR and fr-CA, Latin American Spanish covers es-MX. Locales without their own screenshots show those of the primary language.

  8. Publish

    Upload every ready locale to App Store Connect, then follow the version state until it is live.

Translating with a CSV

A spreadsheet keeps translators out of design tools. One row per string, one column per language. This layout is illustrative:

key,en,fr,de
home.title,"Every workout. Guided & tracked.","Chaque séance. Guidée et suivie.","Jedes Training. Geführt & erfasst."
scan.title,"Just snap a pic.","Prenez une photo.","Einfach fotografieren."

With the Vitrine CLI:

vitrine strings export --app jyva --missing --format csv > to-translate.csv
vitrine strings import --app jyva translations.csv --dry-run
Translators should see the slide, not only the string. A caption that reads well in a table can overflow once placed on a slide.

What to check before publishing

  • Missing or stale texts: strings with no translation, or whose source changed after translation.
  • Overflow: German and Finnish captions are often much longer than English ones.
  • Fonts: make sure the font covers the language’s script, for example Thai, Arabic or Hebrew.
  • Right-to-left: mirror the layout of captions, not the whole interface.
  • Captured screens: the app interface in the screenshot must be in the same language as the caption.
  • No silent fallback: a language with a missing item should be reported, not quietly shown in English.

Vitrine’s coverage matrix runs these checks per language and per slide.

Next: create an App Store Connect API key to publish every locale from the tool.

Try it on your own app

Add your app by name, pick a template and see your first slide in a few minutes.

Get Started