Localize a screenshot set.

A repeatable workflow for localizing app store screenshots, checking typography, and keeping language variants accurate across releases.

Localization is more than changing the headline. The app screen, number format, typography and reading direction all contribute to whether a screenshot feels coherent. Treat each language as a small, reviewable product release.

1. Decide what needs to change.

Separate the content into three groups: headline and supporting copy, text inside the app screen, and visual assets containing text. A screenshot of an English onboarding screen does not become a German screen when the marketing headline changes.

Create a glossary for feature names and terms that should stay consistent. Note words that should remain in the original language, such as a product name. Keep the glossary alongside the release notes so reviewers have the same reference.

2. Write for the available space.

Start with a concise source message. Ask the translator to preserve the benefit, not the exact number of words. German text can become longer; Turkish characters need font coverage; Arabic changes reading direction. There is no single expansion percentage that guarantees a good layout for every phrase.

In ShotFleet you can maintain English, Turkish, German, Spanish, French and Arabic copy within the same project. This release uses text you supply; it does not automatically translate or certify language quality.

3. Review the rendered result.

• Overflow: is any headline clipped or squeezed into too many lines?
• Glyph coverage: do characters such as ğ, İ, ş and Arabic letters render in the intended font?
• Direction: are Arabic text, punctuation, numbers and mixed Latin product names ordered correctly?
• Source screen: does the app UI match the language promised by the headline?
• Meaning: does the copy describe a feature that actually exists in that version of the app?

4. Keep a release checklist.

For each language, record the reviewer, app version, source screenshot date and approval state. When a screen changes, revisit the corresponding localized asset. A copy edit may affect one language; a redesigned screen may affect all of them.

Start with the markets you can support well. Two carefully reviewed language sets are a better initial workflow than many unreviewed variants. Add more languages once you can reliably update the existing ones.

5. Upload to the intended listing.

Check the store language selection before uploading. Apple’s localization guidance explains localized app information. Google’s custom store listing guidance explains targeting and language behavior; custom listings are not automatically translated.

Keep exploring.