Localize the whole screenshot, not only its headline
Adapt app captures, screenshot headlines and layout for each locale. Use a review matrix and a manual Skir workflow without assuming automatic translation quality.
A localized screenshot combines an accurate app screen, appropriate marketing copy and a layout that fits the language. Changing the large English headline while leaving the app interface in English can still misrepresent what the intended audience will see. Plan the capture and copy together.
Choose a supported locale and a real app experience
Begin with a language your app actually supports and an audience you can serve. Apple lists supported metadata localizations and explains that the displayed language can depend on the storefront, device settings and your configured languages. An editor language label is not a guarantee that the store has a matching localization slot.
For each locale, identify the app build, reviewer and source of the copy. Use fictional demonstration data in the local format: dates, names, currencies and measurements should make sense without exposing a real customer. Do not change a price, feature or promise merely to make the screenshot fit.
Use a small localization matrix
Keep an approved source sentence beside each translation. For an illustrative task screen, ‘Plan your day’ communicates an action; a translation that promises perfect productivity changes the claim. Ask the reviewer to assess meaning in context, not just spelling in an isolated text cell.
| Item | What changes | Approval question |
|---|---|---|
| App capture | Actual localized interface and demo state | Does this match the released app? |
| Headline | Meaning and natural phrasing | Can the visible screen support this statement? |
| Typography | Font coverage, line breaks and alignment | Are all characters readable and complete? |
| Delivery | Locale folder, device target and file order | Will these files go into the intended store slot? |
Prepare the localized artwork in Skir
This manual workflow does not require AI translation. The editor's size/language variant controls have plan restrictions; a locale label alone does not translate the copy. AI-assisted wording, where available, still needs a competent language reviewer and a check against the actual app.
- Open the intended screenshot set, or start another set from the same library template for the same app. Keep the approved source export in a separate folder.
- Replace the illustrative or older app capture with a real capture in the target language. Do not translate labels by painting over the app screenshot.
- Select each editable headline and supporting text layer and enter the reviewed wording. Check every board rather than assuming one edit changes the entire set.
- Choose a font that contains the required characters. Review accents, punctuation, numerals and any mixed-language app name.
- Shorten copy where meaning permits, adjust the text box and review the layout. Inspect the exported image as well as the editor view.
Check expansion and reading direction
Do not assume a fixed percentage of extra space is enough for every language. A short source headline can become several words longer, and a different font can wrap differently even when the character count is similar. Start by preserving the meaning, then adjust the composition around the approved text.
For right-to-left scripts, examine character shaping, punctuation, mixed Latin names and alignment separately. Mirroring a whole screenshot can reverse charts, logos or app controls incorrectly. Keep the app capture faithful to the localized app and obtain native-language visual review before publishing.
Approve the exact exported files
Export the available boards and open every image. The reviewer should see the composition at both full resolution and a small store-preview size. Record corrections against a filename and screenshot number so the right asset gets replaced. Keep the store locale code separate from a broad language label in your delivery notes.
A useful handoff contains the final images, their order, platform and locale, the app build used for capture, and the reviewer's approval date. The matrix below is a blank working document. It is not evidence that Skir has translated or linguistically approved your app.
Download the editable Markdown worksheet. Open it in any text editor and fill it with your own release evidence.
Sources and related guides
Platform documentation checked September 10, 2026. The workflow advice is Skir’s editorial guidance; it does not certify a particular app or predict conversion results.