How to Update App Store Screenshots for Multiple Languages Without Going Insane

Why screenshots matter

Most users decide to download without reading the full description. Your first 2–3 screenshots do the heavy lifting. If those images speak the user’s language, conversion jumps—often dramatically.

What makes it hard

Localization multiplies work: multiple devices × multiple languages. Add text inside the image and you’ve got a small design project every release.

• Device sizes × languages → 150–500 images quickly
• Text inside images requires design updates
• Language expansion/contraction breaks layouts
• Platform resolution and format requirements

Modern solutions

You don’t need to choose between “painful” and “perfect.” These options balance speed and polish—pick the one that matches your resources.

• Fastlane snapshot: programmatic screenshots by language and device
• Design template tools: Figma/Sketch templates; swap localized text
• Screenshot platforms: generate all languages/devices quickly
• Hybrid (recommended): real UI + localized marketing overlays

Fastest workflow today

If you want results this afternoon, follow this path. It’s the quickest way to get localized visuals live without building a custom pipeline.

1. Capture clean source screenshots (all device sizes)
2. Translate short overlay text (punchy, 3–7 words)
3. Apply to templates; export per device
4. Upload per language in App Store Connect

Device sizes and quick specs

Use these as a starting point. Apple occasionally updates specs, so confirm before large exports.

• iPhone 6.7": 1290×2796 px
• iPhone 6.5": 1242×2688 px
• iPhone 5.5": 1242×2208 px
• iPad Pro 12.9": 2048×2732 px
• iPad Pro 11": 1668×2388 px

*Always check the latest specs in Apple's guidelines; sizes change with new devices.

Template strategy (Figma/Sketch)

Templates save hours once you set them up. A few layout choices upfront make multi‑language exports painless later.

• Create one master per device; use auto‑layout with text boxes that grow vertically.
• Design for the longest language (German) first; EN will fit naturally.
• Keep overlay text to 3–7 words per line; prioritize benefit first.
• Use styles for fonts/colors so language switches are one‑click.

Fastlane snapshot basics

For engineering‑heavy teams, Fastlane gives you repeatable, scripted screenshots—perfect for CI and release trains.

# Snapfile
devices(["iPhone 15 Pro Max", "iPad Pro (12.9-inch) (6th generation)"])
languages(["en-US","de-DE","ja-JP"])
scheme("AppStore")

Snapshot launches simulators in each language to auto‑capture screens in consistent states. Combine with deliver to upload localized metadata and screenshots.

QA checklist (10 minutes)

Before uploading, run this quick visual pass. It catches 90% of issues that cause re‑exports.

• No clipped text in DE/FR/IT; lines wrap gracefully.
• Contrast ratio is readable on OLED backgrounds.
• Locale‑specific numerals/currency in UI captioned areas.
• Overlay text aligns to safe margins across devices.

Update cadence

Treat screenshots like a lightweight campaign. Refresh the hero frames alongside big features or seasonal moments.

• Quarterly: refresh top 3 locales; rotate the first screenshot based on the latest feature.
• Major releases: update all languages; pair with localized “What’s New”.
• Seasonal: add temporary variants (Black Friday/Holidays) for high‑intent weeks.