Translation isn't a checkbox, it's a bet. Spend on the wrong languages and you've burned cash on words nobody reads; skip the right ones and you've quietly capped your sales in markets that were ready to buy. The good news: localization is one of the most measurable decisions you'll make before launch, so you can stop guessing and start spending on evidence.
Should You Localize Your Indie Game At All?
Whether you should localize your indie game depends less on ambition and more on two numbers: how text-heavy your game is, and where your audience already lives. A physics puzzler with twelve UI strings is a trivial localization job with outsized upside. A 90,000-word narrative RPG is a different animal there the question isn't 'should we' but 'how much can we afford to do well.'
Before committing, read your own Steam data. The clearest signal sits in your wishlist breakdown and store traffic by country. If 15% of your wishlists already come from a region whose players can't read your store page, that's not a translation cost it's revenue you're leaving on the table.
Text Volume Decides Your Tier, Not Your Budget
Most studios price localization backwards. They pick a budget, then ask how many languages it buys. Flip it. First sort your text into tiers, because each tier carries wildly different cost and risk.
- Store + UI only: page description, menus, settings, tooltips. Cheap, fast, and the single highest-ROI layer for most games.
- Gameplay-critical text: tutorials, item names, objectives. Players need this to not get stuck mistranslation here generates refunds.
- Narrative and flavor: dialogue, lore, barks. Expensive per word and quality-sensitive; bad narrative localization reads worse than none.
- Full voiceover: a separate project entirely. Almost never worth it for an indie at launch.
A practical move: ship UI-and-store localization for many languages, and reserve full-text localization for the two or three markets your data actually justifies. Players forgive English dialogue far more readily than an English store page they can't even decide to buy from.
The Numbers That Actually Justify The Spend
Localization pays back through three mechanisms, and you should model all three before signing off. First, conversion: a translated store page converts browsers to buyers (and to wishlists) at a meaningfully higher rate in that region. Second, reach: Steam's algorithm surfaces your game more readily to players whose language you support. Third, reviews non-English players who get a native experience leave fewer angry 'no language support' reviews that drag your rating down.
Run a back-of-envelope check per language: estimated regional units × your price × that region's purchasing-power-adjusted conversion lift, minus translation cost. A Steam Pricing Planner exercise makes this concrete because regional pricing and conversion are inseparable a perfect German translation at a tone-deaf USD price still underperforms.
When Skipping Localization Is The Right Call
Saying no is a legitimate strategy. If your game is pre-traction with thin wishlists, your money is better spent proving the game converts in English first through community, festivals, or a focused Paid Ads Setup than spreading a tiny budget across half-finished translations. Localization multiplies demand; it doesn't create it. Multiplying zero is still zero.
Equally, don't half-localize a story game. A machine-translated narrative that players can tell was run through software does real reputational damage and shows up in reviews. If you can't fund a quality job in a language, leave it in English and revisit it post-launch when sales data tells you exactly where the demand is.
Sequencing: What To Do Before You Sign A Contract
- Pull your wishlist-by-country and store-traffic data and rank regions by real demand, not assumptions.
- Freeze your text. Translating against a moving target means paying twice when you rewrite a quest line.
- Build a string export pipeline early retrofitting localization into hardcoded text is the most common avoidable cost.
- Start with store + UI for your top languages, measure the wishlist response, then decide on full text.
If you're still unsure where your demand actually sits, start by reading the data you already have a quick pass through a Steam Wishlist Calculator and your regional wishlist split usually points to the one or two languages worth funding first. From there the decision mostly makes itself, and we're happy to sanity-check your numbers whenever you want a second set of eyes.