App Price Localization: The Complete Guide for iOS and Android

Price localization gets confused with currency conversion constantly, and the confusion costs indie devs real money. Converting $9.99 to euros or rupees at today's exchange rate isn't localization, it's the same price wearing a different currency symbol. Real localization asks a different question: what does $9.99 actually feel like to someone earning a local income, and what number would feel the same somewhere else. It's one piece of the broader pricing framework, the one most apps get wrong first.

Exchange rates measure the wrong thing

An exchange rate tells you what a dollar converts to. It says nothing about what that money can buy where the person lives, or how many hours of local wages it represents. A country's currency can be strong against the dollar while local salaries are still a fraction of a US salary, or the reverse. If you localize on FX alone, you'll systematically underprice rich markets and overprice poor ones, the opposite of what you want.

Purchasing power is the number that matters

Purchasing power parity (PPP) asks: how much local currency does it take to buy the same basket of everyday goods here as it does elsewhere. It's the economic concept behind why a haircut, a coffee, or a meal can cost wildly different amounts in dollar terms from one country to the next, even after you account for the exchange rate.

The classic, simplest version of this is The Economist's Big Mac Index: since a Big Mac is close to identical everywhere, its local price is a rough, honest gauge of what money is actually worth in a given country. We use the same idea under a different name (the Burger Index) because the logic holds for any near-identical product sold globally: cheap burger, cheap country, lower app price makes sense; expensive burger, pricier country, the app can charge more there too.

The three inputs a real localization needs

1. Your base price, in your home currency.
2. A purchasing-power signal per target country (the burger price differential, in our case).
3. The store's actual allowed price points. Neither the App Store nor Google Play let you charge an arbitrary decimal, every territory has a fixed ladder of prices you can pick from.

Miss any one of the three and the output is wrong: skip the purchasing-power signal and you're just doing FX conversion again; skip the price ladder and you'll recommend a number nobody can actually set.

How the App Store and Google Play handle this today

Apple auto-generates a price for every territory from your base price, using its own exchange-rate table, and lets you override any territory manually from the Pricing and Availability screen. Google Play does the same on a per-country basis in Play Console. Both defaults are pure currency conversion, not purchasing-power localization, which is exactly the gap this leaves open: the platform will let you set a purchasing-power price, it just won't compute one for you.

Rounding to a real price point

Even a perfect purchasing-power number is useless if it doesn't land on something the store will accept. India's price ladder doesn't include ₹387.42; it includes fixed tiers like ₹350 and ₹399. A real localization tool snaps your computed price to the nearest real tier, rounding down when the two options are equidistant so you never accidentally overprice a market you were trying to make more accessible.

A worked example

Take a $9.99/month subscription priced from the US. A burger costs $6.12 in the US and the equivalent of about $2.51 in India, roughly 41% of the US price. Run that through a conservative localization and India lands at ₹350/month (about $3.88, a 61% discount), still profitable, still rounded to a real Play Store and App Store tier, and priced at a level Indian buyers actually pay for apps. The full India walkthrough, with more price points, is here.

Not every market goes cheaper. Countries like Switzerland or Norway often price above the US once purchasing power is accounted for, because a burger costs more there in real terms. Good localization moves prices in both directions, not just down.

The one guardrail

Don't localize so aggressively that your price looks suspiciously cheap everywhere. A price that's too low doesn't read as generous, it reads as low-quality. The right approach caps how far you discount while still meeting each market close to where it can actually pay.

Do it in practice

Enter your base price and pick a country in the calculator: you'll get a purchasing-power price for 73 App Store and Play Store territories in one pass, already rounded to real tiers, with a CSV export ready to paste into App Store Connect or Play Console. Here's exactly how to apply it once you have the numbers.