Localized screenshots: the ASO win almost nobody ships

July 14, 2026 · 5 min read

Open the App Store in Tokyo and most indie listings look the same as they do in Toronto: English headlines on every screenshot. The description got translated, the screenshots did not. That mismatch is the first thing a Japanese user sees.

Why screenshots matter more than descriptions

Store visitors decide from the gallery. Most never expand the description at all, so a localized description under English screenshots localizes the part of the page people read least. If you are going to translate one thing, translate the words printed on your screenshots.

Why nobody does it

Because it multiplies design work. Five screenshots times ten languages is fifty artboards to re-typeset, re-export, and keep in sync every time the design changes. At a designer-day per language, the math kills the project, so teams ship English everywhere and move on.

Adaptation beats translation

Literal translation is the wrong tool for screenshot headlines anyway:

• Headlines are marketing copy. "Track every habit" needs the punchy local equivalent, not a word-for-word rendering.
• German runs long and will overflow a layout tuned for English. Short adapted phrasing fits; literal phrasing wraps badly.
• Japanese, Korean, and Chinese break lines by different rules entirely.
• Arabic is right-to-left, which changes the whole composition, not just the words.

How Storeboard does it

Storeboard treats a locale as a render target, not an afterthought. Pick from ten languages (Spanish, Portuguese, French, German, Italian, Japanese, Korean, Chinese, Hindi, Arabic), and it adapts each headline for the market, re-renders the full screenshot set per locale, verifies the rendered text letter for letter, and exports one ready-to-upload folder per language, listing copy included and still inside every character limit.