If you've ever tried to manually localize App Store screenshots for even 5 languages, you know the pain.
10 screenshots × 40 languages = 400 individual images.
I spent two weekends doing this in Figma for my first app. Copy text layer, paste translation, adjust font size because German is 35% longer, fix the layout breaking in Arabic because RTL, realize Japanese needs a completely different font... then repeat 398 more times.
There had to be a better way.
The Math That Breaks Every Developer
Let's say you're a solo developer with an app available in 20 countries. Apple wants screenshots for at least 2 device sizes. That's:
- 10 screenshots × 20 languages × 2 devices = 400 images
- At 5 minutes per image (optimistic) = 33 hours of work
- Every time you update your app UI = start over
This is why most indie developers just... don't localize. And they leave 30-80% more downloads on the table.
The Template-Based Approach
The key insight that changed everything for me: separate design from content.
Instead of creating 400 static images, you create one dynamic template where text is a variable. Change the translation, and the screenshot regenerates automatically.
Here's what that workflow looks like:
Step 1: Design Once
Create your screenshot template with placeholder text. Every text element — headlines, captions, UI labels — is a separate, editable layer.
I built Shotlingo specifically for this. It's a browser-based canvas editor where you design your screenshot once and mark each text element for translation.
Step 2: Add Translations
For each text element, add translations for your target languages. You can:
- Use AI translation as a first pass (surprisingly good for app-related terminology)
- Import translations from your existing localization files
- Manually enter translations from your localization team
The smart part: the template automatically adjusts text size and positioning based on the translated content. German text gets slightly smaller, Arabic layouts mirror, Japanese uses the right font stack.
Step 3: Batch Export
Hit export. All 400 screenshots generate in seconds, correctly sized for every device, named according to App Store Connect and Google Play conventions.
What used to take 33 hours now takes about 10 minutes.
Handling the Tricky Languages
Some languages need special attention:
RTL (Arabic, Hebrew, Persian): Beyond mirroring text direction, the entire visual layout should flip. If your English screenshot shows a phone on the right, the Arabic version should show it on the left.
CJK (Chinese, Japanese, Korean): More compact than English, so you actually gain space. But font selection matters — not every custom font includes CJK character sets.
German, Finnish, Hungarian: These languages are significantly longer than English. Your carefully designed layout will break if you don't account for this. Auto-sizing text is essential.
Vietnamese, Thai: Heavy use of diacritics that clip if line height is too tight. Build extra vertical padding into text containers.
The Results
After localizing my app's screenshots for 25 languages:
- Downloads increased 45% in non-English markets within the first month
- Japan and South Korea showed the biggest jumps (60%+ increase)
- Total time spent: ~15 minutes for initial setup, ~5 minutes per update
The ROI on screenshot localization is absurd. It's probably the highest-impact, lowest-effort ASO task you can do.
Getting Started
If you want to try this workflow:
- Start small — localize for your top 5 markets first
- Use AI translation for the first pass, refine later
- Measure the impact — App Store Connect and Google Play Console both show per-country conversion rates
- Iterate — update screenshots with every major release
Shotlingo is free to start — you can design templates and export for your first few languages without paying anything.
What's your current screenshot localization workflow? I'd love to hear how other developers handle this.
Top comments (0)