Table of contents
- Quick nav
App Store Screenshot Captions & Localization: Metadata That Matches the Visuals
Captions are metadata with pixels
On the App Store, screenshot “captions” (the promotional text you overlay or place beside device frames) do more than decorate. They are often the first readable promise in search results thumbnails and the bridge between your keyword set, subtitle, and in-app reality. When English US captions say “Offline maps” but the DE set shows a cloudy sync metaphor with no offline claim, you don’t just lose polish—you confuse intent.
This guide focuses on caption strategy and localization for App Store product pages: what to say, how long to say it, and how to keep every locale honest.
Always verify live App Store Connect fields and App Review Guidelines for your category.
Separate three caption layers
Treat each screenshot as three layers you can localize independently:
| Layer | Role | Localization note |
|---|---|---|
| Overlay headline | Benefit in ≤6–8 words (EN) | Translate meaning, not idioms |
| UI chrome inside the shot | Proof | Ship real localized UI builds when possible |
| Optional subline | Clarifier / constraint | Use for pricing honesty, offline, platforms |
Never bury keywords only in overlays while the binary stays English. Reviewers and users both notice.
English caption craft (baseline before translation)
Strong EN patterns:
- Verb + outcome: “Export store-ready sizes”
- Outcome + time: “Mockups in minutes”
- Pain removed: “No more manual 6.9" crops”
Weak patterns:
- “Next-gen synergy for creators”
- Keyword stuffing: “ASO ASO screenshots mockup generator tool”
- Claims you cannot show in the same frame
Character comfort zone for overlay headlines on phone screenshots: roughly 24–40 characters. If it wraps to three lines in the frame, cut it.
Localization workflow that doesn’t break ASO
1. Freeze a source brief, not a source sentence
For each frame, document:
- User job-to-be-done
- One allowed claim
- Forbidden claims
- Keyword themes (not forced exact strings)
Translators then write native captions. Exact EN strings force awkward calques (“Make screenshots goodly”).
2. Map keywords per storefront
Apple’s search behavior differs by locale. Your US keyword field is not a paste target for overlay text in JP or FR. Instead:
| Locale | Caption priority | Keyword field still owns |
|---|---|---|
| en-US | Benefit clarity | Synonyms, competitor gaps |
| en-GB / en-AU | Spelling & idioms | Same themes, local variants |
| de-DE | Compound nouns carefully | Avoid unreadable long overlays |
| ja-JP | Short phrases, UI-first proof | Reading direction & density |
| es-MX vs es-ES | Vocabulary differences | Separate QA, don’t clone |
3. Prefer localized UI screenshots
A perfect Spanish headline over English settings copy signals “we didn’t finish.” If you cannot ship all languages yet, prioritize:
- Primary revenue storefronts
- Frames that show lots of text UI
- Paywall and permission frames (highest trust risk)
4. Keep claim parity
If en-US frame 1 promises “No account required,” every locale either keeps that promise or drops the frame—not a softer mistranslation that implies accounts are optional when they are not.
Caption + metadata alignment matrix
Use this before every version release:
| Frame | Overlay claim | Subtitle echo? | Keyword theme? | In-app proof |
|---|---|---|---|---|
| 1 | Fast export | Yes/No | export, mockup | Export success UI |
| 2 | Device sizes | Optional | iPhone, iPad sizes | Size picker |
| 3 | Templates | Optional | templates | Template grid |
| 4 | Privacy angle | Only if true | — | Local processing toggle |
| 5 | Team seats | Only if sold | — | Invite screen |
If subtitle and overlays fight (subtitle: “Meditation”, overlays: “Crypto portfolio”), conversion and review risk both rise.
Custom Product Pages and caption sets
Apple Ads Custom Product Pages (CPPs) let you align screenshots to keyword themes. Captions should specialize, not merely recolor:
- Brand CPP: outcome + trust
- Competitor-conquest CPP: differentiation claim you can prove
- Feature CPP: one feature vocabulary matching the ad group
Do not reuse a generic five-frame set with a single word swapped; users feel the bait.
Accessibility and localization intersect
- Avoid text baked into low-contrast gradients.
- Leave margin for languages that expand 20–30% (DE, FR).
- Don’t rely on color alone for “new” badges when localizing.
- Dynamic Type isn’t available on store pages, so your caption font size must already read at thumbnail scale.
QA checklist per locale
- Native speaker (or trusted linguist) reviewed overlays
- UI language matches overlay language
- No leftover EN Lorem or debug strings
- Prices, trials, and taxes honest for that storefront
- Screenshots re-exported for required device sizes
- Claims match privacy labels and IAP config
Practical production tips
- Maintain a caption spreadsheet:
frame | en-US | de-DE | … | claim_id | last_verified_build. - Name export files with locale and size:
1_hero_en-US_69.png. - When a feature ships late in one locale, ship a fallback frame rather than a lying caption.
- Re-test thumbnails in App Store search on a physical device—desktop ASC previews flatter readability.
Example five-caption arc (productivity app)
- “Turn notes into tasks in one tap”
- “Shared lists that stay in sync”
- “Reminders that respect focus time”
- “Works offline on your commute”
- “Export PDF when you need a record”
Localize the arc, not isolated punchlines. Frame 4’s offline claim must remain true everywhere you show it.
Closing
Screenshot captions are not a dumping ground for keyword leftovers. They are localized product promises. Write them like packaging copy: short, verifiable, and adapted to how each market reads—then make sure the pixels inside the device frame keep the same promise.