App Store Storefront Country List

Storefront codes follow ISO 3166-1 alpha-2 — “us” for the United States, “jp” for Japan, “de” for Germany — and they surface everywhere in App Store tooling. Public listing URLs embed them (apps.apple.com/de/app/…), the iTunes Search and Lookup APIs take them as the country parameter, App Store Connect analytics segments by them, and Apple Ads campaigns target them. A wrong code silently returns another country’s data, which is a classic source of corrupted rank-tracking numbers.

It is worth internalizing that a storefront is not a language. The Swiss storefront (“ch”) serves German, French, and Italian speakers; the Canadian storefront serves English and French; the Belgian one Dutch and French. Conversely one language spans many storefronts — Spanish listings serve users across more than twenty of them. Availability, pricing, and charts are per storefront; listing text is per localization; the mapping between the two is exactly what this table documents.

Search behavior is defined by the storefront-plus-language combination, not by country alone. Each storefront maintains its own search index and its own set of indexed localizations, so a keyword that ranks #3 in the UK storefront may not rank at all in Australia despite both being English-speaking. Rank tracking, keyword research, and competitor analysis all need to be pinned to a specific storefront code to be meaningful.

The mapping also drives localization strategy. Before paying for a new localization, check how many storefronts it unlocks: Portuguese (Brazil) primarily serves one giant storefront, while Arabic serves a dozen mid-size ones, and Spanish (Mexico) serves Latin America and additionally gets indexed inside the US storefront. Counting reachable storefronts per language is the first step of any locale prioritization exercise.