How to Localize App Store Screenshots and Previews

Most developers who localize their App Store presence focus on text: descriptions, keywords, What's New notes. That's a solid start. But screenshots are the single most influential element on your product page. Research from SplitMetrics shows that 60–80% of visitors make their download decision based on visuals alone, without ever scrolling to read the description.

If your screenshots show English text overlays to a Japanese user, you're signaling that this app wasn't built with them in mind. That friction costs you conversions — and in competitive categories, it's the difference between a download and a bounce.

This guide covers everything you need to localize your App Store screenshots and previews effectively: what to localize, the exact specifications for each device, cost-effective workflows, and when full localization is worth the investment versus simpler approaches.

Why Screenshot Localization Matters

The App Store product page is a conversion funnel. When a user lands on your page — whether from search, browse, or a feature — they see your icon, screenshots, and app name before anything else. On iOS, the first three screenshots are visible without scrolling horizontally, and they auto-play if the first asset is a video.

Here's what the data tells us:

• Screenshots are the #1 conversion driver — More than the icon, rating, or description, the screenshot gallery determines whether users tap "Get"
• Localized screenshots build trust — Users in non-English markets are more likely to download apps that appear to natively support their language
• Localization signals quality — If you've invested in localized screenshots, users assume the in-app experience is also localized
• Competitive advantage — In many markets, most competing apps only show English screenshots. Localized visuals make you stand out immediately

Consider the user's perspective in South Korea. They search for a productivity app, and the results show five options. Four have English screenshots; one shows the app in Korean with Korean text overlays explaining features. Which one feels like it was made for them?

What to Localize in Your Screenshots

Not every element needs localization. Break down your screenshots into layers and decide what to change per market:

1. Text Overlays (High Priority)

These are the captions, headlines, and feature callouts overlaid on your screenshots. They're the most visible text element and the easiest to localize. Examples: "Track your habits effortlessly," "AI-powered meal planning," "Sync across all your devices."

Text overlay localization is non-negotiable for your top markets. It's also the easiest to automate — if your screenshots use a template system, you can swap text programmatically.

2. In-App UI Language (Medium Priority)

The actual app screens shown in your screenshots should ideally display in the target language. If your app is localized internally (which it should be, per Apple's guidelines), capture screenshots with the device language set to each target locale.

If your app isn't internally localized yet, this is a chicken-and-egg problem. You can start with text overlay localization alone — it's better than nothing — while working on in-app localization in parallel. For more on the full process, see our complete App Store localization guide.

3. Cultural Imagery (Situational)

This is the most nuanced layer. Cultural imagery includes:

• Currency symbols — Show yen for Japan, won for Korea, rupees for India in finance apps
• Date and time formats — DD/MM/YYYY vs MM/DD/YYYY, 24-hour vs 12-hour
• Sample content — Names, locations, food items that feel local rather than American-centric
• Color associations — Red means luck in China but danger in Western markets; white is mourning in some Asian cultures
• People and diversity — Representation matters. Users engage more with imagery that reflects them

Full cultural adaptation is expensive and only makes sense for your highest-revenue markets. For most apps, localizing text overlays and in-app UI language covers 90% of the conversion benefit.

4. Layout Direction (Essential for RTL Languages)

Arabic, Hebrew, and Persian read right-to-left. If your app supports RTL layout (as it should for these markets), your screenshots must show the RTL interface. This isn't optional — showing an LTR interface to an Arabic speaker looks broken and unprofessional.

RTL screenshots also need mirrored text overlay placement. If your English screenshot has a caption on the left, the Arabic version should have it on the right.

App Store Screenshot Specifications

Apple requires specific dimensions for each device class. Here are the current specifications you need to know:

You can upload up to 10 screenshots per device type per localization. Most developers focus on the 6.7" iPhone and 13" iPad Pro sizes, since Apple scales down from these for smaller devices. That said, if your UI looks significantly different on smaller screens, provide dedicated assets.

App Preview Video Localization

App previews auto-play on the product page and can dramatically boost conversion. Apple allows up to 3 preview videos per device size per localization, with these specs:

• Duration: 15–30 seconds
• Format: H.264, M4V/MP4/MOV
• Resolution: Must match device screenshot specs
• Audio: Optional, muted by default on product page

When to Localize Videos

Not every preview needs localization. Evaluate based on content type:

• Must localize: Videos with spoken narration, text title cards, or prominent UI text
• Can reuse: Videos showing primarily visual interaction (gesture-based games, visual apps) with minimal text
• Partial localization: Re-record narration or swap text overlays while keeping the same footage

For most apps, the most practical approach is creating a single video that relies on visual storytelling rather than text. If you do use text, build it as a separate layer so you can swap it per language without re-editing the footage.

Cost-Effective Localization Workflows

Full custom screenshots for 40 languages is a massive production effort. Here are five approaches ranked from most to least expensive, with guidance on when each makes sense:

Approach 1: Full Custom Per Market ($$$)

Create unique screenshot sets for each market with localized text, cultural imagery, and market-specific messaging. This is what major publishers like Spotify and Netflix do.

Cost: $500–$2,000 per language (design + translation)
Best for: Top 3–5 revenue markets for apps earning $50K+/month
Downside: Unsustainable for more than a handful of markets

Approach 2: Template-Based Text Swap ($$)

Design screenshot templates in Figma, Sketch, or Photoshop with text layers separated from backgrounds and device frames. Swap the text layer for each language while keeping the visual design identical.

Cost: $50–$200 per language (translation + export time)
Best for: Apps targeting 10–40 languages with text-heavy screenshots
Downside: Text expansion/contraction can break layouts; needs some per-language adjustment

Approach 3: Automated Screenshot Generation ($)

Use tools like Fastlane Snapshot to programmatically capture screenshots with the device set to each locale. Combine with a framing tool to add localized text overlays automatically.

Cost: Engineering time upfront, near-zero marginal cost per language
Best for: Apps with fully localized in-app UI; teams with CI/CD infrastructure
Downside: Requires app to be internally localized; initial setup takes 4–8 hours

Approach 4: Text Overlay Only ($)

Keep the same screenshot images (showing English or your primary language UI) but localize only the text overlays. This is the minimum viable localization for screenshots.

Cost: $20–$50 per language (translation only, bulk export)
Best for: Apps where the UI is primarily visual (games, photo editors, music apps)
Downside: In-app text still appears in primary language, which can look inconsistent

Approach 5: No Screenshot Localization (Free)

Use the same screenshots everywhere and focus your localization budget entirely on keywords and descriptions.

Best for: Very early stage apps validating international demand before investing in visuals
Downside: Leaves significant conversion gains on the table, especially in competitive categories

Building a Screenshot Localization Pipeline

For teams that want to scale screenshot localization efficiently, here's a proven pipeline:

Step 1: Design with Localization in Mind

This is the single most important decision. When creating your original screenshots, architect them for localization from the start:

• Separate text from imagery — Use Figma components or Sketch symbols with overridable text fields
• Use generous text containers — Allow 40% more space than your English text needs (for German, Russian expansion)
• Avoid embedding text in images — Rasterized text can't be swapped
• Choose fonts with broad Unicode support — Your design font needs to cover CJK characters, Arabic, Thai, and Devanagari at minimum
• Plan for RTL — Mirror your layout for Arabic/Hebrew from the beginning

Step 2: Create a Translation Brief

Screenshot text isn't regular copy — it's ultra-short, high-impact marketing language. Provide translators (or your AI tool) with:

• Character limits per text field (measure in pixels, not just characters)
• Context for each caption (what feature is being shown, what's the key benefit)
• Brand voice guidelines (casual? professional? playful?)
• Terms that should not be translated (app name, branded feature names)

Step 3: Generate and Export

Using your template system, batch-generate screenshots for all languages. If you're using Figma, the Variables feature lets you define text strings per locale and switch the entire design between languages with a single click. Export at the required resolutions for each device class.

Step 4: Upload via API

The App Store Connect API supports programmatic screenshot uploads. You can automate the entire submission as part of your release pipeline, uploading the correct screenshots for each locale without manually navigating App Store Connect.

Common Mistakes to Avoid

After working with hundreds of apps on their localization efforts, these are the most frequent screenshot localization failures:

• Text overflow — German text that extends beyond the screenshot frame because the container was sized for English. Always test with your longest-translating language first.
• Font rendering issues — Your trendy display font doesn't support Thai or Korean characters, so the system falls back to a mismatched font. Test every language before exporting.
• Outdated screenshots — Your app's UI has been redesigned twice since you last updated localized screenshots. Stale screenshots that don't match the actual app experience hurt trust.
• Ignoring the first three — Only the first three screenshots are visible without scrolling. If screenshots 1–3 aren't compelling and localized, screenshots 4–10 don't matter.
• Literal translation of marketing copy — "Get cooking!" is a playful English call-to-action. The literal translation in Japanese makes no sense. Give translators creative freedom to adapt messaging, not just convert words. This is the difference between localization and translation.
• Same screenshots for all markets — A finance app showing USD to a Brazilian user, or a food app showing hamburgers to a Japanese user. Your top markets deserve locally relevant sample content.

When to Invest in Full Screenshot Localization

Not every app needs fully localized screenshots in 40 languages. Here's a practical framework for deciding:

• Always localize text overlays for any language where you have localized metadata. It's low-cost and high-impact.
• Localize in-app UI screenshots for languages where your app is internally localized. Use Fastlane Snapshot or equivalent to automate captures.
• Invest in cultural adaptation only for markets contributing more than 5% of your revenue or where you're actively running user acquisition campaigns.
• Prioritize the first 3 screenshots over having 10 mediocre ones. Three excellent, localized screenshots beat ten generic ones every time.

The App Store localization checklist includes screenshot localization as part of a comprehensive launch workflow for new markets.

For the text metadata side of localization — app names, descriptions, keywords, and pricing — tools like AppStoreLocalization.com can handle 45+ languages automatically, freeing you to focus your manual effort on the visual assets that require design attention.