AppScreenDesign
Menu

Localization workflow

Localize the screenshot set
without duplicating the project.

Add App Store Connect languages, fill a new locale from the main localization and then adjust its copy, captures and layout where the translation needs a different rhythm.

Start with your screenshots See the editor

Free during early access · No card required

Localized screenshot composition with bold caption and app interface
Real renderer. Illustrative app screens.

App Store Connect localizations

50 locales, one editable project.

Choose a main localization, add more languages in bulk, then adapt each locale’s copy, raw captures and design. This is the supported App Store Connect catalog, rather than every operating-system language.

See supported languages and locale codes
Arabic ar-SABangla bnCatalan caChinese (Simplified) zh-HansChinese (Traditional) zh-HantCroatian hrCzech csDanish daDutch nl-NLEnglish (Australia) en-AUEnglish (Canada) en-CAEnglish (U.K.) en-GBEnglish (U.S.) en-USFinnish fiFrench fr-FRFrench (Canada) fr-CAGerman de-DEGreek elGujarati guHebrew heHindi hiHungarian huIndonesian idItalian itJapanese jaKannada knKorean koMalay msMalayalam mlMarathi mrNorwegian noOdia orPolish plPortuguese (Brazil) pt-BRPortuguese (Portugal) pt-PTPunjabi paRomanian roRussian ruSlovak skSlovenian slSpanish (Mexico) es-MXSpanish (Spain) es-ESSwedish svTamil taTelugu teThai thTurkish trUkrainian ukUrdu urVietnamese vi

Catalog matches the product. Apple’s localization reference, checked 29 October 2026. Filling from the main localization copies a starting point; it does not translate the copy automatically.

Practical walkthrough

A repeatable localization review.

Copying the main localization is a starting action, not a translation service or a permanent link. Review each locale as an independent screenshot set.

  1. Fill from the main localization

    Add the desired languages, then copy the main set into each one. Do this before locale-specific editing so a later fill does not replace work you want to keep.

  2. Replace both words and captures

    Translate the headline and every visible label. Upload raw screenshots from the localized app so an English interface does not sit under a translated promise by accident.

  3. Check wrapping and completeness

    Inspect long words, punctuation, script coverage and the final reading order. With JSON or MCP, reread the document and preview each changed panel before export.

01

Add languages in bulk

Search the supported App Store Connect localization catalog and select several locales at once.

02

Keep locale-specific inputs

Upload raw screenshots for each language and edit the text fields that belong to that locale.

03

Use JSON or MCP

Edit localization documents manually, through the API or through an agent using the same structured project model.

Translation is a layout problem too

A translated headline can be shorter, longer or split differently. Each localization keeps its own copy and design so you can fix line breaks without damaging the main language.

Start from a safe copy

Fill a locale from the main localization, then review every screen. Raw captures and text remain inspectable rather than hidden inside a flattened export.

Questions

Before you start.

Are localizations linked forever?

No. Filling from the main localization is a starting action. The locale can then carry independent text, screenshots and design choices.

Can an agent edit several languages?

Yes. MCP and API localization documents expose structured fields so an agent can update each locale while preserving unrelated languages.

Can I upload different screenshots per language?

Yes. Each localization can keep its own raw screenshot assets and bindings.

You built the app.
Give it an introduction.

Start with a composition. Keep every detail editable.

Open the editor