Steam regional pricing: a practical guide for indie developers

You set one number, and Steam immediately asks you about several dozen more. The pricing screen fills itself in with suggestions per currency, and the honest first reaction for most solo developers is that they have no idea whether those numbers are right, no data to check them against, and no intuition for what a game should cost in a country they have never been to.

The good news is that accepting the suggestions is a defensible default and most developers should do exactly that at launch. The useful knowledge is not how to compute a better number from scratch. It is understanding what the suggestion is trying to do, recognising the few situations where it is worth overriding, and knowing which problems regional pricing can solve and which it cannot.

This guide covers all three, and ends with the part that catches people out: the timing rules that constrain when you are allowed to change your mind.

Why the same game costs different amounts in different countries

The instinct is to think of regional prices as one price converted into local currency. That is not what they are, and treating them that way is the underlying mistake behind most bad regional pricing.

A price is a signal about how significant a purchase is, and that signal depends on income, not on exchange rates. The same converted amount can read as an impulse buy in one country and as a considered purchase you talk yourself into over a week in another. A conversion that is arithmetically correct can therefore be commercially wrong in both directions: too expensive to be bought at all in one market, or so cheap in another that it undercuts what the market would happily have paid.

There are three further reasons the numbers do not line up neatly. Exchange rates move, and a price set once drifts away from whatever it was meant to represent. Round numbers are culturally specific, so a price that looks deliberate in one currency looks like a conversion artefact in another. And because Steam charges in local currency, the player never performs the conversion themselves; they see a number in the currency they think in and judge it against the other games they see in that currency, which are also priced regionally.

How the suggested prices are meant to be used

Steamworks generates a suggested price for each currency from the base price you set. The right mental model is not that it is a currency converter with a discount applied, but that it is a well-informed default maintained by a party with access to vastly more sales data across regions than you will ever have. For a first release with no data of your own, deferring to it is not laziness; it is the correct use of better information.

The part that matters more than the launch decision is that the suggestions are not static. Steam periodically revises them as exchange rates and its own model move, and prompts developers when a revision affects them. Those prompts are easy to ignore, especially a year or two after launch when you are working on something else.

That is where the most common regional pricing mistake actually lives. It is rarely a wrong number chosen deliberately. It is a number that was right at launch, was never revisited, and has quietly become something else while the developer was busy. If you do only one thing from this article, make it this: when Steam tells you the suggestions have changed, open the page and look, even if you then decide to keep what you have.

When it makes sense to override the suggestion

There are real cases for setting your own number. They are narrower than people expect, and each one has a reason behind it that you should be able to state out loud.

The non-reasons are worth naming first, because they come up more often than the reasons do. Wanting more revenue is not a reason to raise a regional price: the suggestion already reflects what that market will bear better than your preference does. A competitor pricing differently is not a reason either, unless you know something about their situation that you almost certainly do not. And a region simply selling badly is not, on its own, evidence of a price problem — that is a diagnosis, covered two sections below, and getting it wrong means cutting your revenue without changing your sales.

The cases that do justify an override look like these:

• Your home market price sits at a psychologically meaningful point that the conversion destroys — worth fixing in that one currency, not everywhere
• You are deliberately entering a market and want the price to help, most often a market where you have just added the language and want the first wave of players to be easy to acquire
• Consistency across your own catalogue — a new title priced oddly against your existing games in the same region confuses returning players and undermines bundles
• You have actual data, after enough time has passed, showing a region converts far below or far above the others in a way price plausibly explains

Two cautions before you start typing numbers

Whatever you change, change one currency at a time and write down why. A year later, looking at a pricing table full of numbers you cannot account for, that note is the difference between a considered decision you can revisit and a set of values you are afraid to touch.

The first caution is that Steamworks will tell you when a price you have entered sits far outside its suggestion. Treat that as information rather than an obstacle. Extreme outliers are not just flagged; they create the conditions for the second caution.

Large gaps between regions create an incentive to buy where the game is cheap and move the copy somewhere it is expensive. Platforms limit this — gifting between certain regions is restricted and keys can carry region restrictions — but the enforcement is the platform's job and its coverage is never complete. Your lever is not enforcement. It is not creating an extreme gap in the first place.

The wrong conclusion to draw from that is to price everything at the level of your highest-income market to be safe. That does not protect anything; it simply removes the markets you were pricing for. The workable position is the ordinary one: follow the suggestions, deviate for a stated reason, and keep the deviations modest.

Why a low price does not sell a page nobody can read

Here is the interaction that gets missed, and it is the one most likely to be costing you money right now. The regions where purchasing-power adjustment produces the biggest discounts are overwhelmingly regions where English is not the first language. So the markets you are pricing for and the markets you have not translated for are largely the same markets.

Lowering the price there without a readable store page is optimising the last step of a funnel whose first step is broken. A player who cannot tell from your page what kind of game this is does not buy it at any price; they close the tab. Price is the final objection a buyer raises, and you only get to answer it if the earlier questions — what is this, is it for me, is it any good — have already been answered.

There is a diagnostic in the regional data that separates the two cases cleanly. Look at your traffic and wishlist numbers for a region. If people are reaching your page and not converting, the page or the price is the problem and price is a reasonable thing to try. If almost nobody is reaching the page at all, price is not your bottleneck and adjusting it changes nothing; the missing piece is discovery, and language support is one of the levers that moves it.

It is also worth noting which lever is cheaper to pull twice. A price cut reduces your revenue on every unit forever and is awkward to reverse, because players notice increases and wishlist owners have already formed an expectation. Adding a language costs a fixed amount once and does not reduce what you earn per sale. When both are available and you can only do one, that asymmetry is worth weighing.

How often to revisit, and what constrains the timing

A reasonable rhythm has four triggers rather than a fixed calendar: when Steam prompts you about revised suggestions, when you add a language for a region, before you plan a major sale, and once or twice a year as a maintenance pass whether or not anything has happened.

The constraint people run into is that you cannot change prices whenever you feel like it. Platforms apply cooldowns around discounts and restrictions on changing prices close to a sale, and those rules affect how quickly you can react to anything you discover. Check the current rules in the Steamworks documentation before you build a sale calendar, because a plan that assumes you can adjust a price the week before an event may simply not be executable.

The other constraint is not a rule but a fact about perception: lowering a price is easy and raising it is not. A discount is announced to the people who wishlisted your game; an increase is discovered by them. Launch pricing is therefore closer to a one-way door than the pricing screen makes it feel, which is another argument for starting from the suggestions rather than from a number you improvised.