Localization guide

Translate screenshots without losing clarity.

Localized screenshots usually fail because the design assumes English text length. Plan for longer words, different proof points, and reviewer feedback before export day.

Localize the promise, not only the words

A literal translation can be technically correct and still weak. Rewrite the caption so the local user understands the benefit instantly. For example, a productivity app might emphasize time saved in one market and team coordination in another.

Use filename language hints

Frame Launch can detect language codes in filenames such as screen-01_de.png or onboarding_pt-br.png. This makes it easier to upload language-specific screenshots and keep them attached to the same project screen instead of creating a messy duplicate list.

Design for expansion

German, French, Spanish, and Turkish captions often need more room than English. Leave extra width, avoid tiny badge text, and test line breaks in every target language. When a caption gets too long, cut the idea instead of shrinking the type until it becomes unreadable.

Review workflow

  • Export a draft ZIP for each language.
  • Ask a native speaker to check store context, not only grammar.
  • Review screenshots on a phone-sized display.
  • Keep a changelog of which captions changed after review.

Next step

Open Frame Launch, add your target languages, and test the longest caption first. The longest language usually reveals the layout problem fastest.