Google Play Store External Billing Launches June 30 — New Fee Structur

After years of courtroom battles, mounting regulatory pressure across three continents, and a landmark ruling that handed Epic Games a significant win, Google is finally ready to put a date on it. Google Play Store external billing goes live on June 30 in the United States, United Kingdom, and European Economic Area — and the fee structure that comes with it looks dramatically different from the one developers were living under just a few years ago.

• Google Play Store external billing launches June 30 in the US, UK, and European Economic Area.
• The new Google Play Store external billing structure starts at 10%, down sharply from the previous 30% standard cut.
• Developers using Google Play’s own payment system will pay an extra 5% billing fee on top of the base rate.
• Additional fee reductions through Google’s Level Up and Apps Experience programs roll out in September.

What’s Actually Changing on June 30

The headline number is 10%. That’s the base service fee Google will charge every developer on their first $1 million in annual earnings, regardless of whether they collect payment through Google Play’s native billing system, a third-party alternative built into the app, or an external web link that sends users outside the app entirely. Google Play Store external billing covers all three of those routes under the same base rate. For the vast majority of Android developers — the indie studios, the solo app makers, the subscription SaaS tools — that threshold means a flat 10% on everything they earn through the Play Store.

To understand why that matters, you need to remember where this started. When Epic Games filed its antitrust lawsuit against Google back in 2020, the standard commission rate was 30%. Epic argued, with some success, that Google’s control over Android app distribution created an unlawful monopoly. The case dragged on for years, and while the legal outcome was complicated, the practical result has been a steady erosion of Google’s ability to maintain that 30% wall.

The 10% base rate that kicks in June 30 is the clearest evidence yet that the old model is gone. This isn’t a small adjustment — it’s a fundamental repricing of what it costs to reach Android users, and Google Play Store external billing is the mechanism that makes that repricing enforceable.

The Fee Structure in Full — It’s More Layered Than It Looks

The 10% base fee is the simple part. Beyond that first $1 million in annual revenue, the picture gets more complicated, and developers will need to pay close attention to how Google defines the users doing the transacting.

Google is splitting transactions into two categories based on install history. According to the Android Developers Blog, a ‘new install’ is a transaction from a user who first installed or updated the app from Google Play on or after the date the new fee structure launched in their region. An ‘existing install’ is the reverse — someone who had the app before that date. New installs attract a lower fee rate above the $1 million threshold; existing installs face a higher one. Google hasn’t published the exact percentage for those upper tiers in a single clean table, so developers working through high-revenue scenarios will want to model their earnings carefully before assuming the savings are uniform across their user base.

Then there’s the billing fee. If a developer chooses to use Google Play’s own payment infrastructure — the in-app purchase system that handles the actual card processing — Google adds a 5% billing fee on top of the base service fee. That’s the explicit cost of using Google’s rails rather than routing payments elsewhere. Developers who implement Google Play Store external billing or send users to an external web page to complete a purchase won’t pay that extra 5%. That distinction is meaningful: it’s Google acknowledging, in financial terms, that its billing system is an optional service rather than a mandatory toll.

Google Play Store External Billing and the Epic Games Legacy

It would be a mistake to view these changes in isolation. Google Play Store external billing didn’t emerge from goodwill — it emerged from a legal and regulatory gauntlet that Google has been navigating since the early 2020s.

The Epic v. Google trial concluded with a jury finding in Epic’s favour in late 2023, ruling that Google had illegally monopolised the Android app distribution market. The remedies phase stretched into 2024 and beyond, with courts ordering Google to open the Play Store to competing app stores and third-party billing options. Today’s announcement is effectively Google codifying those obligations into a published developer policy, with a hard start date attached.

The broader context here includes Apple, which is facing its own version of this reckoning. The EU’s Digital Markets Act has forced Apple to allow third-party app stores and alternative payment methods in Europe, and the ongoing Apple v. Epic litigation in the US continues to shape what’s permissible in app store billing. Google’s move to formalise Google Play Store external billing policy puts pressure on Apple to clarify and potentially expand its own concessions — particularly in markets where regulators are watching closely.

What This Means for Developers in Practice

For smaller developers, the 10% rate is genuinely good news. An indie app earning $500,000 a year was previously handing Google $150,000. Under the new structure, that bill drops to $50,000 — a $100,000 swing that changes the economics of building and maintaining apps on Android entirely.

For larger developers — the ones pulling in tens of millions through the Play Store — the calculus is trickier. The 10% rate only applies to the first million. Above that, the fee varies by install cohort, and anyone relying heavily on an existing, long-tenured user base could find the savings less dramatic than the headline rate suggests. Those developers will need to decide whether the engineering investment required to implement Google Play Store external billing or a third-party payment system is worth avoiding that additional 5% billing fee.

There’s also the user experience consideration. Google Play Store external billing means sending users to a browser to complete a purchase, which adds friction. Some developers will accept that trade-off for the fee savings; others — particularly subscription apps where conversion rates are everything — may decide Google’s 5% billing fee is a reasonable price for keeping users in a seamless checkout flow.

Level Up, Apps Experience, and What Comes in September

June 30 isn’t the end of the rollout. Google has two additional programs — called ‘Level Up’ and ‘Apps Experience’ — that unlock further fee reductions for developers who meet specific quality benchmarks. These include actively supporting alternate Android form factors like tablets and foldables, maintaining low crash rates, and implementing features Google recommends for a high-quality app experience.

Those programs don’t activate until September. That’s a deliberate sequencing choice on Google’s part — it gets the core billing changes live first, then layers in the incentive programs once developers have had time to update their billing integrations. It also gives Google a few months to see how the market responds to the June 30 changes before the full policy picture is in place.

For developers, the smart move right now is to start auditing their install base data — understanding what proportion of their active users will be classified as ‘existing installs’ versus ‘new installs’ after June 30 — and modelling out the fee impact across both Google Play billing and Google Play Store external billing scenarios. The savings are real, but they’re not identical for everyone, and the apps that benefit most will be the ones whose teams do that analysis before the deadline rather than after.

One thing is clear: the era of the 30% mobile tax is over on Android, and Google Play Store external billing is the structural change that makes that permanent. The pressure on the industry’s broader app store economics has never been higher. Where this ultimately lands for Apple — and what the combined effect looks like for the developer ecosystem writ large — will be one of the defining tech policy stories of the next two years.

Source: 9to5Google

Frequently Asked Questions