Localising screenshot captions: length, line breaks and right-to-left

On both stores, screenshots are often the first thing people look at, and the captions on them are often the only text they read. A localised listing with English captions sends a mixed message. Here is how to localise captions so they still fit and still read well.

Why captions matter more than they look

Most people browsing a store page scan the screenshots rather than reading the description. A caption is a headline: it says what this screen does for the user in a few words. If the listing text is in Japanese but the screenshots say "Track every habit" in English, many users will assume the app isn't really for them.

Rule one: write short in English first

The easiest captions to localise are short ones. Aim for a single idea per screenshot, in a few words, with an optional smaller second line. Long English captions leave no room for any language that runs longer, and they're harder to read on a phone anyway. If your English captions are long, shorten them before localising rather than after.

Also keep captions as live text in your design file, not flattened into images. You'll need to swap them per language, and that's far easier when the caption is a text layer.

Text expansion: German, French and friends

The same sentence is often noticeably longer in German, French, Spanish, Portuguese or Italian than in English. German forms long compound words, which also makes line breaking harder because a single word may not fit on a line. French tends to need more words for the same meaning.

Ways to deal with it:

Chinese, Japanese and Korean

CJK captions usually take fewer characters than English, but each character is wider, so the line length in pixels doesn't shrink as much as you might expect. The bigger issue is line breaking.

Arabic and other right-to-left languages

Arabic and Hebrew read right to left, and a store page in those languages is laid out right to left. Captions need more than translated text:

Store specifics worth knowing

App Store Connect lets you upload different screenshots per localisation, and Play Console lets you add localised graphics per language. If you only translate the listing text, screenshots fall back to your default ones, which is the mixed-language page you want to avoid in your main markets.

A caption localisation checklist

  1. Shorten the English captions first: one idea per screen.
  2. Write each language to fit the space, not as a literal translation.
  3. Back-translate so you know what each caption says.
  4. Check line breaks by eye in every language, especially German and CJK.
  5. Right-align and mirror for Arabic and Hebrew; confirm letters are joined.
  6. Look at the finished screenshots at phone size before uploading.
Want it done for you? 10 languages, $39. Per-locale keyword research, store limits enforced, English back-translation for every field. See how TenTongues works.