Short answer: sell the game with the listing first

App store localization for games adapts your listing per market: translated title, subtitle, keywords, description, and screenshots, with genre terms researched locally instead of translated. Localize the listing first in two or three genre-strong markets, measure conversion, then fund in-game translation only where the listing pulls.

For an indie game, the listing is the cheapest demand test you can buy. A full listing pass in one market takes an afternoon: re-research 8 to 12 genre keywords from local autocomplete and rival listings, rewrite the 30-character name and subtitle around the two strongest terms, rebuild the 100-character keyword field from scratch, translate the description hooks, and re-render screenshot captions in the local tongue. Ship it, then read that market apart for three weeks: impressions per storefront, product-page conversion, and downloads. If impressions rise and conversion holds, the market wants your game and in-game translation is a safe bet. If impressions rise but conversion stays flat, your screenshots or ratings need work before more words. If nothing moves, that market can wait. This order caps your risk at one afternoon per market instead of one translation invoice, and every market that passes the test funds the next one from earnings.

The cost gap is what makes this order work. A listing pass covers six fields and a screenshot set. Full in-game translation covers menus, tutorials, quests, dialogues, achievements, and every future update, plus testing with local players. Agency guides agree: Asowin's 2026 game guide says to start with the cheaper listing pass to test demand before full in-game work. Our listing-versus-in-app guide draws the same boundary for non-game apps. Games just raise the stakes, because in-game word counts dwarf anything a listing holds.

Pick game markets by genre money, not population

Big populations mislead. A market with 200 million people means nothing if your genre barely charts there, while a smaller market can fund your whole year when your genre dominates its top lists. Rank markets by four signs: genre popularity in the local charts, revenue per player for your model, how crowded the local genre keywords are, and whether you can support players there. Your own analytics come first. If Brazil already sends you soft-launch traffic, Brazil outranks any expert tier list.

Consultant playbooks converge on the same first wave: Japan, Korea, France, Italy, Germany, and Spain on top of English, then Brazilian Portuguese once the first wave pays back. That order matches our market-depth guides one by one: Japan first, Korea second, Germany third, France fourth, Spain fifth, Italy sixth, Brazil seventh, Mexico eighth. Read the guide for each market you shortlist before you write a word. Each one names the traps (German compound packing, Japanese script mixing, French accent rules, elision in Italian, Castilian versus Mexican Spanish) that decide whether your listing fits.

One caution: games carry rules that utility apps skip. Age ratings, loot-box disclosure, and ad policies differ by storefront, and some markets gate game approvals behind local publishing numbers. Check the policy gate before you fund the words, and skip any market you can't legally enter, no matter how strong its genre charts look.

Research genre keywords per market, never translate them

Game vocabulary shifts more between markets than almost any other category. Players in different countries use different genre names, slang, and English loanwords for the same game. Translate your English genre term straight and you target a phrase nobody types. Research each market from zero: type your genre into local App Store autocomplete, open the rival listings that rank, and note which words repeat. A native speaker settles the close calls, such as whether the loanword or the local word wins.

Put category words in the title and subtitle, not your tagline. Talofa Games titles its game "Monster Walk: Step Adventure" because the subtitle carries the category words players search for. Its guide warns against translating the tagline when the local category term would rank instead. The same rule holds in every tongue. Lead with what the game is in words local players type, then add flavor. Our subtitle guide covers the 30-character fit per locale, and our keywords-field guide covers the 100-character rebuild mechanics, including byte math for character-based scripts where fewer visible characters can still cost more bytes.

Keep two lists per locale as you research. The first holds terms your listing targets now. The second holds near-miss variants for later: plurals, slang spellings, and competitor-adjacent phrases. When the core set ranks, our cross-localization guide shows how to stack extra locales onto the same storefront without rewriting the winners.

Make gameplay screenshots sell in every tongue

Shoppers decide from the first screen of your listing: the icon, the first two or three screenshots, and the ratings. For games, the screenshots must answer one question fast: what do I do in this game. Show the core loop: real gameplay with a one-line caption in the local tongue. Menus and settings screens don't sell. Make the first shot carry the whole pitch for shoppers who never swipe.

Re-render every caption instead of pasting translated text over old art. German captions expand and break tight layouts, so shorten the line before you render. Japanese captions need script checks, not just font checks. Arabic captions need right-to-left layout. Then check each set at phone size, because a caption that reads fine on desktop turns to noise on a 6-inch screen. Our screenshot tools guide compares the three caption workflows, and our QA pass lists the per-locale checks to run before submit.

Art itself may need more than translated captions. Character designs, color meanings, symbols, and themes land differently across markets. Asowin's guide flags Western versus East Asian art-style gaps as the classic miss. You don't need new art per market on an indie budget. Check three things: does the lead character read as hero or villain here, does the palette signal the right mood, does any symbol carry a meaning you didn't intend. One native-player review of the shot set catches most of it.

Keep listing words and in-game words matched

Talofa localizes its listing and its in-game text together so the words match, and that rule deserves a name: the words-match rule. When your listing promises a "step adventure" but the game calls itself a "walking quest" in the same tongue, shoppers smell a machine job and bounce. Worse, mismatched terms split your keyword equity: the listing ranks for one phrase while reviews and word of mouth use another.

Run a glossary row per locale with 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, listing or in-game, draws from the glossary. When in-game translation lags behind the listing, scope your listing claims to what the game actually shows: never advertise a localized quest line that still ships in English. Our mistakes roundup covers the listing-layer errors that burn indie budgets, and the boundary guide shows which half each string belongs to.

How App Store Localizer covers the game listing pass

Start from your public App Store URL and the tool pulls your title, description, icon, and screenshots through Apple's public lookup in seconds.

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.

Keyword suggestions come from free heuristics over your public listing plus any source keywords you paste. That gives your genre research a starting list, which you'll 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.

Measure each game market apart

One blended dashboard hides every answer you need. Read each market apart across equal windows: three weeks of localized listing against the three prior English-only weeks, per storefront. Track impressions (did the new terms get seen), product-page conversion (did the shots and ratings close), and downloads. Judge each layer apart. Impressions up with flat conversion means the terms worked and the screenshots or ratings need work. Conversion up with flat impressions means the shots worked and the terms added little. One market beating the rest means it funds in-game translation first while the others wait.

Ratings pull extra weight for games, so run the review loop in each tongue you ship. Ask for ratings at a happy moment, right after a win or a reward, with the platform prompt. Reply to reviews in the reviewer's tongue. Both stores show your replies, and a thoughtful reply in the local language converts the next ten shoppers who read it. Our review-reply guide gives the weekly loop, and our measure guide gives the full equal-window routine.

Frequently asked questions

  • Should I localize my game listing before the game itself? Yes, in almost every indie case. The listing costs an afternoon per market while in-game translation costs real money plus testing plus every future update. Ship the listing first in two or three genre-strong markets and read conversion for three weeks. Fund in-game translation only where the listing pulls. Exceptions are rare: an abstract puzzler with zero-language gameplay can hold longer on a light listing plus English in-game text.
  • Do game screenshots need translation, or just the text fields? Both, and screenshots matter more. Shoppers scan pictures before they read a word, and unlocalized screenshots tell them the game isn't for them. Re-render each caption in the local tongue and check the set at phone size. Go one step further for games: confirm the shown gameplay, characters, and symbols read correctly in that market. Text fields get you found. Screenshots get you installed.
  • How many languages should an indie game ship? Start with two or three markets where your genre already earns, not with twelve tongues at once. Each tongue you ship commits you to translating every future update, event, and reply thread in that language. Studios that launch in twelve tongues on a vendor quote often abandon half within a year. Add the next market from earnings, using the same listing-first test. Our strategy guide shows the revenue-ordered wave order that keeps the queue funded.
  • Will translated keywords alone rank my game? No. Translated terms are guesses until local players confirm them. Genre names, slang, and loanwords differ by market, so a straight translation often targets a phrase nobody types. Research each keyword field from local autocomplete and rival listings, then verify with impressions data per storefront. Our keywords-field guide covers the rebuild mechanics and our cross-localization guide shows how to stack extra locales once the core set ranks.

Paste your App Store URL at https://asolocalization.com today. Run the listing pass for the two or three markets where your genre already earns (fresh genre terms, rewritten name and subtitle, re-rendered gameplay captions) in one afternoon. Then read each market apart for three weeks and fund in-game translation only where the listing pulls. Our Japan and Korea guides name the script and keyword traps in the two strongest game markets. Our measure guide gives the equal-window routine that turns impressions into a funding decision.

The listing is the cheapest demand test you can buy, so run it before you translate a single quest line. If gameplay screenshots are new ground, read our screenshot tools guide for the caption workflows, then our QA pass to check each set before it ships.