Listing Shot Kit

Localize App Store screenshots

Plan translated captions, choose the right captures and export one screenshot set per listing language. Review the final images before submission.

Create separate screenshot sets for each App Store listing language and keep their sequence aligned. In App Store Connect, a new listing language initially inherits screenshots from the primary language. To show localized artwork, choose the target language on the editable app version and add that language’s images. The listing language is configured separately from the languages in your app binary. Apple’s localization instructions

Start with the actual interface for the selected locale

Arrange your primary-language set and decide what each screenshot demonstrates before translating the captions. Write down the story in order, such as discover a task, complete it, see its result. Keep the same order for each language so you can compare the sets quickly. Use target-language app captures when your tabs, date formats, currencies or other UI labels change. If the app intentionally displays the same interface across markets, check that a caption does not promise a translated experience visitors will never see.

Check that your screenshots show realistic but fictional data. Avoid email addresses, private conversations or customer names. When using Apple Simulator, capture a clean account and verify accessibility text size, device orientation and wording under the actual target language and region. A photograph pasted behind an app screen cannot substitute for a feature shown in use.

Reflow exact copy on the target output

A concise English headline may take two lines after localization. Preview each card at its target size instead of assuming the original line breaks travel well. If long text reduces legibility, shorten the message while preserving the action or result it communicates. Check the brief supporting line separately. The editor wraps text for the available layout and reports when a caption is too long. System fonts are used in the canvas. Check language-specific glyphs on the browser and machine you’ll use for export.

Review bidirectional text such as Arabic and Hebrew with a fluent speaker. A centered headline can still put Latin numbers or punctuation in an unexpected place if you mix writing systems. If the app’s direction changes per language, capture a correctly mirrored screen. Avoid flipping the image itself, as that reverses labels and other elements.

Keep language codes and device sizes visible

Choose the correct listing language in the editor and export the set. For example, an English (United Kingdom) ZIP for 1206 × 2622 portrait is named with an en-GB-iphone-1206-1206x2622 prefix. Files inside it end in -01.png through the final shot’s position. The code helps a team sort files and does not set the language in Apple’s interface.

Use separate batches in the free editor for each device, orientation and locale. Keep a free localization checklist for releases with several caption translations. Check the exact pixel guide if a locale needs an iPad set or a different iPhone capture.

Check the localized listing in Connect

  1. Open the editable platform version and choose the exact locale. For instance, distinguish French (France) from French (Canada).
  2. Select the correct iPhone or iPad display slot and drop the extracted files in your planned sequence.
  3. Open the displayed image list and verify that it shows the intended language and order. Check the first image at a smaller size, then scan for any screenshots left over from the primary language.
  4. Verify the app continues to show real screens for the majority of each device’s set. Text overlays can point to features already visible in the capture.

Apple separately reviews language information and assets. If you later change the primary language, Apple requires an approved localization and matching approved screenshot sizes for supported platforms. Product pages with custom configurations can require additional screenshot sets. Apple’s primary-language requirements