Storefronts and localization names read from Apple’s App Store localizations reference; language codes and field limits from Google Play’s translation language list and each store’s field reference. Checked August 29, 2026.
| Property | Value |
|---|---|
| Language | Portuguese — Português |
| App Store localization | Portuguese (Brazil), Portuguese (Portugal) |
| Google Play code | pt-BR, pt-PT |
| Script | Latin · left-to-right |
| Default storefronts | 2 |
| Supported storefronts | 3 |
| Keyword field | 100 bytes ≈ 100 Portuguese characters |
| Our translator code | pt |
Both stores treat Brazilian and European Portuguese as separate localizations, and the difference is not cosmetic — vocabulary, verb forms and register all diverge enough that Brazilian users notice a Lisbon translation immediately.
Brazil is the larger market by a wide margin, so pt-BR is the one to write first and pt-PT the one to add when you have reason to.
Where a Portuguese listing appears
Apple publishes the default language of all 173 App Store storefronts. Portuguese is the default in 2 of them, and an additional supported language in 1 more.
Default language in
Additionally supported in
What you translate, and what it costs you
Both stores cap the same fields, and neither cap changes by language — but the amount of meaning you fit inside them does. Apple’s keyword field is the one that surprises people: it is measured in bytes, so Latin at about 1 byte per character leaves roughly 100 characters. Google Play counts characters instead, and says so explicitly: its limits “apply to both full-width and half-width characters”.
| Store | Field | Limit |
|---|---|---|
| App Store | App name | 2–30 characters |
| App Store | Subtitle | 30 characters |
| App Store | Keywords | 100 bytes |
| App Store | Promotional text | 170 characters |
| App Store | Description | 4,000 characters |
| Google Play | App name | 30 characters |
| Google Play | Short description | 80 characters |
| Google Play | Full description | 4,000 characters |
The screenshots are part of the localization
Both stores let you upload a separate screenshot set per localization, and in practice the captions are what sells — a translated description under English screenshots converts like an English listing. Design the frames once, then export the same layout per language rather than rebuilding it: that is the difference between localizing into Portuguese in an afternoon and not doing it at all.
Write it once, ship it in Portuguese
Edok Studio drafts your store listing with AI, translates the whole thing — name, subtitle, keywords, description — into Portuguese and 30+ other languages, and exports a screenshot set per locale from one design.
Start free — no card