Localize the whole screenshot, not only its headline

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.

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.

1. 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.
2. 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.
3. 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.
4. Choose a font that contains the required characters. Review accents, punctuation, numerals and any mixed-language app name.
5. Shorten copy where meaning permits, adjust the text box and review the layout. Inspect the exported image as well as the editor view.

Check text expansion and right-to-left (RTL) layout

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.

What our manual export check verified

On September 11, 2026, we tested English, German and Arabic text variants of the existing Keep Ideas Forever catalog template on live skir.app. In the initial three-locale round, each case changed four editable text layers across the first three Free-plan boards. We reopened the saved project, checked the headline in the editor, submitted a background export and downloaded the resulting ZIP in the browser.

All nine PNG files from that initial round decoded at 1290 × 2796 pixels without alpha or blank output. The text-free second board had the same file hash across all three runs. This verifies the tested save and export path. It does not establish translation quality, automatic localization or a fully localized app: the embedded app captures stayed unchanged, and the other two template boards were outside the Free export selection.

Two later German attempts with larger headlines timed out in the production worker. Subsequent German and Arabic reruns completed, with exact saved font settings and loaded editor canvases checked. Both successes and failures are retained in the downloadable record; the small sample does not establish an export reliability rate or a confirmed fix for those timeouts.

Native-language approval is still required. An earlier isolated Arabic text-box diagnostic also found glyph ink extending about 6 pixels above the nominal box; successful full-image export does not resolve that layout limitation. Review the exact composition and marks instead of treating a nonblank PNG as language approval.

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.