App Screenshot Translator: Translate the Text Inside Your Store Screenshots

A store screenshot has two layers of text: the marketing caption above or around the device, and the product UI inside it (buttons, tabs, list items, empty states). StoreLocale translates both, because a German caption over an English interface still reads as an English app.

Some content should never change, though. The table shows how each kind of element is handled during a translation run.

Detection sends a copy of the screenshot, downscaled to a 1280px longest edge, to a vision model. It returns each string with a normalized bounding box plus its color, alignment and font weight, so the translation knows where the text sits and how it should look.

Wrapped headlines are grouped into a single phrase, so a two-line caption is translated as one sentence rather than two fragments. Detection is free, which means you can check what was found on every slide before you spend a credit.

The translation step works on the detected strings, not on the pixels. It is instructed to leave brand marks and technical acronyms such as 4K, HD, PRO and AI untranslated, so a caption like "Export in 4K" should keep "4K" as written. Confirm this for each target language in review.

Every string can then be edited per locale. If your Japanese marketing lead prefers a different product term, change it once for that locale and the other languages are unaffected.

An image model edits the original screenshot and replaces each source string one to one, in the same position. The prompt tells it to match font, weight, color and kerning, to avoid duplicated or stuttering words, and to shorten or fit text rather than truncate it.

Everything that is not text is meant to stay unchanged. Media areas that the detector finds are masked before generation and restored from the source pixels afterwards, so check any poster or video frame it may have missed.

Translations often run longer than the English. The W3C notes (opens in a new tab) that English strings of up to 10 characters can grow by 200 to 300% in translation, which is why short button labels are the first place to check. The text expansion guide covers the worst offenders by language.

Detection and translation cost nothing. Credits are only spent when a localized screenshot is generated, and the tier sets both the price and the output resolution.

With your own OpenRouter or Gemini key, any tier runs at its normal resolution and uses 0 platform credits.

As an example, 8 slides in 6 languages is 48 screenshots: 48 credits at Standard, 96 at Pro or 192 at Ultra. Packs are one-time purchases with no expiry: Starter at $9 for 30 credits, Launch at $29 for 120, and Scale at $69 for 350. See pricing for details.

• Failed generations refund their reserved credits.
• If a screenshot's inputs have not changed, the saved result is reused and not billed again.
• Batch runs process two jobs at a time and show progress per locale.

Open the side-by-side compare view, with the source slide on the left and the localized one on the right. Check each string against the list below before you export.

• Meaning: a native speaker confirms the caption sells the same benefit, not just the same words.
• Fit: no clipped words, no single-letter leftovers, and the caption still reads at thumbnail size. Google Play advises that taglines take up no more than 20% of the image (Play Console Help (opens in a new tab)).
• Fidelity: numbers, prices, names and icons match the source exactly.
• Protected content: posters, ratings and badges are identical to the original.

Export produces PNG files in a ZIP, grouped by platform, locale and size. Every size is scaled from the same 1320x2868 portrait design, which matches Apple's 6.9-inch iPhone portrait size in the App Store Connect screenshot specifications (opens in a new tab).

Strict export blocks slides that still contain untranslated text, so a half-finished locale does not reach the store by accident. Uploading is manual: StoreLocale does not connect to App Store Connect or Play Console.