Show the core loop in shot one, no text needed
Game app store screenshots should open with gameplay at its peak, carry one localized caption per shot from shot two on, and get re-rendered per market for language, layout, and cultural fit. Translate taglines and overlays, keep in-game UI as is, check each set at phone size, and test demand with captions before paying for art.
Top game listings keep the first screenshot almost bare. The frame carries no headline and no feature list, only the game at its most exciting moment. Appstemple's 2026 teardowns show this pattern across top charts: shot one is pure visual proof, and captions start at shot two. There's a reason. Shoppers decide in seconds whether your game looks fun, and text over the best frame only shrinks the art.
So pick the single frame that answers one question: what do I do in this game. A match-3 board mid-cascade. A racer mid-drift. A builder with a city that looks alive. If a stranger can't name the verb in your game from shot one, reshoot the frame before you translate a word. Menus, settings screens, and logo cards don't sell. Gameplay sells, and it needs no translation, which makes shot one the cheapest asset you own. Every market sees the same frame. What changes per market starts at shot two, where words enter the picture. Test the frame before you commit. Show it to five people who never played your game and give them three seconds each. If four can't name the verb, pick another frame. Check it at search-result size too, since the first shot appears beside your name in results, where it competes at thumbnail scale.
Build the arc once in English. Shot one proves the loop with zero words. Shot two names the loop in the local tongue. Shot three shows progression (levels, unlocks, gear). Shot four shows modes or social proof (events, clans, leaderboards). Shots five and six handle objections your reviews raise, such as offline play or no forced ads. Then localize the caption layer per market instead of rebuilding the arc. When a market converts on this set, that market earned deeper work. When it doesn't, you learned it for the price of captions, and our games pillar shows how the full listing-first demand test funds what comes next.
Write captions a phone screen can carry
Most game captions fail on phones, not on desktop. A line that reads fine in your design tool turns to noise on a 6-inch screen over busy art. Write every caption under about five words, one idea per shot, in words a ten-year-old knows. Name a feeling or an action, not a feature. "Conquer your rivals" beats "Real-time strategy with 300 plus levels" because shoppers feel the first and skim the second. Appstemple's tests keep confirming this: feeling and action captions outperform feature captions from shot two onward.
Then give captions their own space. Busy gameplay behind text is unreadable, so put headlines on a solid band or a calm part of the scene. If you squint and can't read it, it's too small. Write for translation from the start. Short source lines cost less and break fewer layouts. Skip jokes, puns, and idioms, since none of them travel. "Win daily battles" stays sharp in most tongues while "Blast your way to the top" turns to mush. One shot, one claim. This discipline pays twice: it lifts conversion in English today and makes every future locale cheaper. Our subtitle guide covers the same short-line fit for the 30-character fields, and our keywords-field guide covers the 100-character rebuild each market needs fresh.
Re-render captions per locale, keep the UI
Here is the rule that saves indie teams real money: localize text, not necessarily UI. Screenshipper states it plainly. In-game UI shown in screenshots doesn't need a per-market rebuild. Taglines, headlines, and overlays do. Shoppers read your captions to decide, and they forgive foreign UI in a gameplay frame far faster than they forgive an English headline shouting at them from a Tokyo storefront. So keep the art, re-render the words. This only works if your art files keep text on a separate layer from day one. If your captions are baked into flattened key art, every locale means redesigning the shot, and Boom Screens names this as the classic game-localization trap. Fix it once: rebuild each shot with live text layers, then export per locale.
The per-locale pass then runs in this order. First, translate captions with a native eye, never a paste job. Game copy is harder than app copy because fantasy terms and genre conventions shift by market, so a literal translation often names something locals don't say. Second, fit the layout. German captions expand and break tight bands, so shorten the line before you render. Japanese needs script checks across kanji, hiragana, and katakana, not just a font that loads. Arabic needs full right-to-left layout, mirrored bands included. Third, check each set at phone size in that language, because length changes break designs that looked safe in English. Fourth, run our QA pass on every set before submit: text, keywords, visuals, and publish checks in one sweep. Our Japan and Korea guides name the exact script and keyword traps in the two strongest game markets, and our transcreation guide shows when a caption needs a full rewrite instead of a translation.
Culturalize the art with one native-player review
Translated captions on wrong-feeling art still lose. Asowin's 2026 creatives guide puts it well: game art often needs culturalization beyond translation, since character choices, color meanings, symbols, and themes land differently across regions, with East Asian art-style expectations as the classic gap. You don't need new art per market on an indie budget. You need one native player to review the shot set before it ships.
Send them the six shots and ask whether the lead character reads as hero or villain here, whether the palette signals the right mood, whether any symbol or gesture carries a meaning you didn't intend, and whether the gameplay matches what local players of this genre expect first. That review catches most disasters in an afternoon. Never show a mode or reward in a market where players can't get it. Bake the four questions into every seasonal pass, and our seasonal guide gives the per-market calendar for that rhythm.
Tie every caption to your game keyword glossary
Screenshots get you installed, but keywords get you found, and Semnexus shows genre terms matter more than feature terms for games. So tie the two together with a glossary row per locale. Four columns: English term, localized term, where it appears (name, subtitle, keyword field, captions, in-game), and the date you set it. Every new string draws from the glossary, listing or in-game. This is the words-match rule from our games pillar: when your captions promise one phrase and your keyword field targets another, you split your equity and shoppers smell a machine job.
The glossary also settles the loanword question per market, since some tongues search the English genre word and others the local one. Lead captions with what the game is in words local players type, then add flavor. When the core set ranks, our cross-localization guide shows how to stack extra locales onto the same storefront without rewriting the winners.
How App Store Localizer covers the game screenshot pass
Start from your public App Store URL and the tool pulls your title, description, icon, and screenshots through Apple's public lookup. It translates the title, subtitle, description, and the 100-character keyword field per target locale. It also re-renders screenshots with localized captions for the listing, which is exactly the caption layer this guide centers on. Keyword suggestions come from free heuristics over your public listing plus any source keywords you paste, so your genre research starts with a list you verify against local search behavior.
Output covers two screenshot sizes: iPhone 14 Plus at 1284 by 2778 and iPad Pro 12.9-inch at 2048 by 2732. You can download the assets or publish straight to App Store Connect. Packages are one-time: Starter at $19.99 for three tongues with all screenshots for one listing, Global at $99.99 for every supported tongue for one listing. The tool covers the listing half only. It doesn't touch in-game strings or Google Play, so treat its output as a fast complete draft: verify genre terms locally, rewrite the hooks, and run one native check on the name, subtitle, keyword set, and captions before you ship.
Read each game market apart before you pay for art
Never judge localized shots on a blended dashboard. Read each market apart across equal windows: three weeks of localized captions against the three prior English-only weeks, per storefront. Track three numbers. Impressions per storefront tell you whether the new terms get seen. Product-page conversion tells you whether the shots close. Downloads tell you whether the market wants your game. Judge each layer apart. Impressions up with flat conversion means the terms worked and the shots or ratings need work. Conversion up with flat impressions means the shots worked and the terms added little. One market beating the rest funds deeper art or in-game translation first while the others wait. Our measure guide gives the full equal-window routine behind this read.
Ratings pull extra weight for games, so run the review loop in each tongue you ship: ask at a happy moment and reply in the reviewer's tongue. Our review-reply guide gives the weekly loop. Only when a market passes this test should you fund custom art or event art per locale. Spend on captions first and save art for last.
Frequently asked questions
- Do game screenshots need text captions? Yes, from shot two on. Shot one should stay pure gameplay with no text, since top-chart teardowns show the bare hero frame wins. From shot two, short captions name the loop, progression, and modes in the local tongue. Uncaptioned sets after shot one leave shoppers guessing what they do, and English captions in a localized storefront tell shoppers the game isn't for them.
- Should I translate the in-game UI shown in my screenshots? No. Keep the UI, translate the taglines, headlines, and overlays. Shoppers forgive foreign UI in a gameplay frame far faster than an English headline. Re-render caption layers per locale with layout checks for expansion, script mixing, and right-to-left tongues, then verify each set at phone size.
- How many screenshots should my game listing have? Ship six. Shot one proves the core loop with zero words. Shot two names the loop locally. Shot three shows progression. Shot four shows modes or social play. Shots five and six answer objections your reviews raise, such as offline play or fair ads. This trailer arc gives every shopper a reason to install by the fourth swipe.
- Can I localize screenshots without making new art per market? Yes. Keep text on separate layers, re-render captions per locale on the same art, and run one native-player review per market for character, palette, symbol, and genre-expectation fit. Fund custom art only after a market passes the three-week conversion read, using earnings from the caption pass.
- How often should I refresh game screenshots? Plan a refresh every four to six weeks, matching live events, seasons, and new modes first. Rotate the seasonal shot per market calendar rather than shipping one global set, and re-run the four culturalization questions on every refresh so new art never reintroduces an old mistake.
Paste your App Store URL at https://asolocalization.com today. Run the caption pass for two or three markets where your genre already earns: real gameplay first, short localized captions from shot two, one native-player art check, then three weeks of per-market reads.
If this is new ground, read our screenshot tools guide for the caption workflows and our QA pass to check each set before it ships. The shots are the pitch, so make every market hear it.