How many players does an English-only game actually reach?

When you release a game in one language, you are making a decision about who it is for — but it rarely feels like a decision, because nothing on the screen tells you who is not in the room. The store shows you visits, wishlists, and sales. It does not show you the people who saw your page, could not read it, and left.

That missing group is not small, and it is not evenly distributed. If your assumption is that everybody on a major PC store reads English well enough to play a game in it, the actual platform data will surprise you — and it is public, published monthly, and takes about two minutes to look up.

This article is about finding that data, reading it without fooling yourself in either direction, and turning it into a sensible view of what each additional language would actually recover for your specific game.

Where Steam's language numbers actually live

Steam publishes a monthly Hardware & Software Survey, collected from users who opt into it, and among the graphics cards and processor breakdowns there is a section for language. It reports the distribution of the languages that Steam clients are set to. It is free, it is public, and it is the single most useful thing an indie developer can read before deciding to ship in one language. Look it up rather than trusting a summary — including this one — because the composition shifts over time.

Read it with the right caveats attached. It measures the language a person has set their client interface to, which is a proxy for the language they prefer to read but not a perfect one. It is a sample of users who chose to participate, not a census. It describes the whole platform population, not the subset who play your genre. And it counts accounts and installs rather than money, so it is a picture of reach rather than of revenue.

The one-line summary, stable enough to be worth stating: English-language users are a large group but nowhere near a majority of the platform, Chinese-language users are consistently among the very largest groups, and behind those there is a long tail of languages each large enough to matter to a small game. If you have been picturing a store where everybody reads English and a handful of other languages are rounding errors, the actual table will not match that picture.

Then there is a second, better source, and it is about you rather than the platform: your own Steamworks data. It reports traffic, wishlists, and sales broken down by country and region, which tells you where interest in your specific game is already coming from. Platform-wide statistics tell you what is possible; your own regional breakdown tells you what is already happening.

Who English reaches, and who it does not

The naive calculation is to take the English share from the survey and conclude that you are missing everybody else. That is wrong in both directions, and understanding why is what makes the number useful rather than alarming.

It overstates the loss because a substantial number of players whose first language is not English play games in English anyway, and have for years. English functions as a default second language on PC storefronts, and in some regions the proportion of players comfortable with it is high. Those players are already reachable.

It also understates the loss, in a way that depends on your game. Being able to read a store page is not the same as being willing to read forty hours of dialogue in a second language. The language barrier scales with how much text your game asks the player to process and how central that text is to enjoying it. A physics puzzler with fifteen UI strings is nearly language-neutral. A narrative adventure, an RPG, or anything with systems explained in prose is not — for those, comfortable-in-English is a much higher bar than able-to-browse-in-English.

The honest framing is therefore not 'English covers X percent of players'. It is: each language you add recovers the people who would have enjoyed your genre, and who would not have played it in English. That overlap is different for every game, which is precisely why the general statistic cannot answer your question — but it does tell you the size of the pool you are drawing that overlap from.

If your only language is not English

Everything above assumes English is your one language. If you are shipping in Japanese only, or Korean, German, or Portuguese only, the arithmetic is harsher, because your single language's share of the platform is smaller — often much smaller — than the English share.

This is why English is usually the first addition for a developer whose native language is something else, and the reason is not only its share of the user base. English is what most curators, press outlets, and streamers outside your own market work in, and it is the language a player in a country you have never thought about will try when your language is not on offer. Adding English does not just add English-speaking players; it makes your game legible to the people whose coverage brings other players in.

It also changes what your existing data means. If you ship in one non-English language and see almost no foreign traffic, that is not evidence that no foreign audience exists — the page they would have found you through does not exist yet. You cannot measure demand from a market you are invisible to.

Supported languages change how the store treats you

There is a mechanical layer to this on top of the human one. Every store page carries a supported-languages table, split by whether the interface, the subtitles, and the full audio are covered in each language. Players read that table, and many treat it as the deciding factor before anything else about the game.

Steam also lets players filter out titles that do not support the languages they have set. A game supporting a single language is therefore invisible to some proportion of browsing players before any judgement about the game itself gets made. It is not a soft disadvantage in the recommendation algorithm — it is a filter, and filtered means absent.

One thing worth knowing, because it opens a cheap option: the store page description is supplied per language independently of which languages the game itself supports. You can make the page readable in a language the game does not yet support. That is not a trick to inflate the table — the supported-languages table must stay honest, and claiming support you have not built produces exactly the disappointed reviews you would expect — but it does mean the page and the game are separate decisions, and the page is the small one.

The word count of a store page is a few hundred words. Adapting a game and its store page so they read naturally to players in another language is what the industry calls localization, and the page is its smallest possible unit. It works as an experiment: put it in a language your traffic data already points at, then watch whether the wishlist and traffic balance for that region moves against roughly the same amount of marketing effort.

Which language to add first

Rankings published online cannot answer this, because they do not know your genre, your text volume, or where your traffic already comes from. What they can do is narrow the list. The actual decision comes from three inputs you can check yourself.

• Your own regional data — countries already sending you traffic or wishlists while converting poorly are the clearest signal available, because they are people who found you and stopped at the language.
• Your text volume — a game with a few hundred strings can afford several languages; a script-heavy game may only be able to afford one at a time, which makes the choice matter far more.
• Engineering cost per language — adding a language that needs a different script means fonts covering thousands of glyphs, encoding that is UTF-8 all the way through your pipeline, and line-breaking that does not assume spaces between words. That is budget on top of translation, and it is worth knowing before you commit rather than after.

Look it up before you decide

The point of this article is not that you must support many languages. Plenty of games are released in one language for perfectly good reasons — scope, budget, a specific audience, a script that would cost more to translate than the game will earn.

The point is that this should be a decision you made rather than one that happened to you. Open the Hardware & Software Survey, find the language section, and look at the actual shape of the platform. Then open your own regional breakdown and see who is already showing up. Fifteen minutes of looking replaces a guess that quietly determines the ceiling on everything else you do — the store page, the trailer, the festival appearance, the launch — because every one of those things is capped by how many people can read the result.