Localize the whole message in your app screenshots

Prepare localized copy and authentic app screens together, then review each locale and device export without rebuilding the campaign.

The method

1. List the markets and languages the app actually supports.
2. Adapt the benefit and examples to each audience. Translation alone may preserve the wrong meaning.
3. Attach UI screenshots in the target locale and record the build version. Check legal copy and prices if present.
4. Review exports at their actual size. When the source changes, inspect affected copies and keep prior versions for comparison.

A translated headline over an untranslated screen is an unfinished localization. Treat the promise, proof and destination as one message.

Worked example: fictional puzzle app

English benefit: Learn the next move without guessing.

French benefit: Trouvez le prochain coup sans deviner.

Proof: a screen captured from the French version of the actual app.

Review: line breaks, localized examples, and the destination language.

The current Slides.win renderer supports Latin-script campaigns. Review platform requirements for additional scripts and destinations.

Reviewed September 16, 2026.