Google Play Subscriptions in 2026: Setup, Structure, Fees, and Key Changes
Android app developers and product managers set up Google Play subscriptions by targeting Android API level 35, running an estimated 14-day testing period with 12 testers, and allowing about 20 days for publishing. Subscriptions consist of base plans and offers, with up to 250 total and 50 active at once, following changes introduced in May 2022. Management includes grace periods for auto-renewing plans to handle billing issues, keeping subscriptions active through trial ends without charges. Fees stand at 15% on the first $1M in annual revenue (with enrollment) and 30% thereafter as of 2025, with Google ending the 30% fee--rolling out in EEA/UK/US by June 2026 and globally by September 2027.
This guide covers Play Console changes to help subscription-based Android apps launch faster while staying compliant. Developers configure products separately in the console, test thoroughly, and plan for fee shifts to optimize revenue.
2026 Setup Requirements for Google Play Subscriptions
Publishing subscription-enabled apps on Google Play requires targeting Android API level 35 (Android 15) <sup>[1]</sup>. This ensures compatibility with the latest platform features and security standards.
The process involves mandatory pre-launch testing, estimated at around 14 days with at least 12 testers. Developer experience points to an overall publishing timeline of about 20 days <sup>[1]</sup>. Internal testing tracks in the Play Console validate billing flows and subscription renewals before launch.
Steps include:
- Integrate Google Play Billing Library.
- Create subscription products in the Play Console.
- Run closed testing with selected testers.
- Submit for review, monitoring for policy compliance.
These timelines, drawn from developer experience, help with launch scheduling.
Understanding Google Play Subscription Structure
Since May 2022, Google Play has separated subscriptions into base plans and offers for greater flexibility <sup>[2]</sup>. A subscription product now serves as a container. Base plans define core pricing and billing cycles, while offers provide variations like trials, introductory pricing, or promotions <sup>[3]</sup>.
Each subscription supports up to 250 total base plans and offers combined, with a maximum of 50 active simultaneously <sup>[2]</sup>. This structure allows tailoring to user segments without overwhelming the catalog.
For migrations, tools like Apphud handle Google Billing v5 and automatically adapt existing subscriptions to base plans <sup>[4]</sup>.
Configure in the Play Console by:
- Adding a new subscription.
- Creating base plans with intervals (e.g., monthly, yearly).
- Attaching offers for specific pricing.
This setup supports dynamic pricing strategies.
Managing Active Subscriptions and Grace Periods
Subscriptions remain active through the trial period without charging users. They transition to paid only upon renewal success <sup>[5]</sup>.
For auto-renewing base plans, specify a grace period in the Play Console. This window--typically days to weeks--allows retries for failed payments due to card issues or temporary declines, reducing involuntary churn. Users retain access during this time <sup>[5]</sup>.
Key rules:
- Trials end without charge if not renewed.
- Grace periods apply post-trial for ongoing subs.
- Monitor via Play Console reports for renewal status.
Proper configuration minimizes disruptions and supports retention.
Google Play Subscription Fees and 2026 Changes
As of 2025, Google charges a 15% service fee on the first $1M in annual revenue for enrolled developers, rising to 30% thereafter on paid apps and in-app purchases using Play Billing <sup>[6]</sup>.
A major update eliminates the 30% fee entirely. Rollout begins in EEA, UK, and US by June 30, 2026, expanding globally by September 30, 2027 <sup>[7]</sup>. Developers should track regional availability to forecast costs accurately.
| Revenue Tier | Fee (as of 2025) | 2026+ Change |
|---|---|---|
| First $1M/year | 15% (enrolled) | Toward elimination |
| Above $1M/year | 30% | Phased end by 2027 |
This shift aids budgeting for scaling apps.
Google Play vs. App Store: Key Subscription Differences
For multi-platform apps, Google Play offers distinct features in structure and timelines compared to the App Store. Play's base plans and offers enable granular pricing, unlike the App Store's more rigid subscription groups.
| Aspect | Google Play | App Store |
|---|---|---|
| Setup Time | ~20 days (estimate based on developer experience) <sup>[1]</sup> | Varies; often faster review |
| Testing | ~14 days / 12 testers (estimate based on developer experience) <sup>[1]</sup> | TestFlight; fewer mandated testers |
| Fees | 15% first $1M / 30% after (ending 30% by 2027) <sup>[6]</sup> <sup>[7]</sup> | 15-30% tiers |
| Structure | Base plans + offers (250 total / 50 active) <sup>[2]</sup> | Subscription groups + family sharing |
Play metrics draw from developer reports; App Store details highlight contrasts where Play provides more evidenced flexibility in testing scale and offer limits. Choose Play for Android-focused apps needing extensive base plan variations.
FAQ
What API level is required for Google Play apps with subscriptions in 2026?
Apps must target Android API level 35 (Android 15) <sup>[1]</sup>.
How long does it take to publish a subscription app on Google Play?
About 20 days, including an estimated 14-day testing period with 12 testers, based on developer experience <sup>[1]</sup>.
What are base plans and offers in Google Play subscriptions?
Base plans define core pricing and billing cycles; offers add trials or promotions. Up to 250 total, 50 active per subscription <sup>[2]</sup>.
What are the current Google Play service fees for subscriptions?
15% on the first $1M/year (enrolled developers), 30% thereafter as of 2025 <sup>[6]</sup>.
When does Google end its 30% Play Store fee?
Rollout starts EEA/UK/US by June 30, 2026; global by September 30, 2027 <sup>[7]</sup>.
How do grace periods work for Google Play subscriptions?
They allow payment retries for auto-renewing base plans during billing failures, keeping access active; length set in Play Console <sup>[5]</sup>.
Next, review your app's Play Console setup for API 35 compliance and base plans. Test with a small group to validate before full launch.