Translating your subscriptions (Google Play)
Localize the name, description and benefits of your subscriptions and in-app products in the Play Console, with character limits and fallback behavior.
Subscriptions and in-app products aren't part of the Play Store listing Releasely pushes for you: they have their own catalog, with their own translations. Everything happens in the Play Console, product by product. This page explains where and how.
Where this happens
The Play Console → your app → Monetize → Products → Subscriptions. Translations apply to the whole catalog: they don't depend on a release or a testing track.
What can be translated (and what can't)
A Google Play subscription carries three user-facing texts, all translatable:
- the Name — the subscription name, 55 characters max;
- the Description — 80 characters max;
- the Benefits — up to 4 bullets of 40 characters each, optional. They appear in the Google Play purchase sheet.
Not translatable:
- the product ID — a technical, permanent identifier that's never displayed;
- base plans and offers (monthly, yearly, free trial…) — their IDs are internal; what users see is the parent subscription's wording;
- the price — it's set per country on the base plan, and Google renders it in the local currency.
Translating a subscription
Open the subscription, then the Subscription details section. The languages block shows your default language (your app's) and a button to add languages.
Pick the languages, then fill in the Name, Description and, if you use them, the Benefits for each. Save: the change goes live without review and propagates within a few hours.
One-time products too
Non-recurring purchases (Monetize › Products › In-app products) work the same way, with different limits: 55 characters for the name, 200 for the description, and no benefit bullets.
What users see when a language is missing
If a user's language isn't among your translations, Google Play falls back to your app's default language. The product stays purchasable, just in the wrong language.
The rule of thumb: translate your subscriptions into the same languages as your Play Store listing. If you manage English, French and Spanish in Releasely, your catalog should cover all three.
No machine translation here
Google offers a translation service for the store listing, but not for the product catalog. Subscriptions are translated by hand, one at a time.
What about inside your app?
The Google Play purchase sheet uses the texts above, in the user's language. Your own paywall,
however, shows whatever you feed it: if your code reads the values returned by Google Play Billing
(ProductDetails), the translations flow through on their own; if your labels are hard-coded, you
have to translate them a second time in the app.
The price should always come from Billing (formattedPrice) — it's the only way to show the right
currency and format per country.
On the iOS side
The same task exists on the App Store, with tighter limits and a review step by Apple — see Translating your subscriptions (App Store).
Google Play metadata & settings
Understand what Releasely pushes for you and complete the required settings you must fill yourself in the Play Console (App content, category, pricing), with the access path.
Testing & release
The Play Store release tracks (internal, closed, open testing, production) and the testing required before production for new accounts.