Google Play commission cuts: who actually wins

Google confirmed this week that Play Store's standard commission is coming down from its long-standing 30% baseline to a tiered structure of 25% and 20%, with the split determined by when an app was first installed rather than a developer's revenue tier alone. The lower, 20% rate applies to installs that happen after the June 30 implementation date; a 25% rate applies to installs that occurred before it. The change takes effect across the European Union and the United Kingdom, and in the United States, on June 30, with Google saying other regions will follow on a later, unspecified timeline. Paul Feng, Google Play's vice president of engineering, said the final rate a developer sees will depend on several factors, including revenue level and payment system choice as well as participation in specific Google programmes, without detailing exactly how those factors interact.

Google Play commission cuts of this size aren't a small announcement for any developer whose Play revenue runs to tens of millions, and the immediate reaction across developer commentary has understandably focused on the headline drop from 30%. The more useful question is who actually captures the benefit once the mechanic is read closely rather than at the headline number. A Deconstructor of Fun piece raised that framing, and it's worth taking seriously even though its full detail remains unconfirmed.

Why the install-date split matters more than the Google Play commission cuts headline

A commission tied to when a user first installed the app, rather than to ongoing revenue tier or a simple flat cut, creates a permanent two-tier system inside a single app's revenue base for as long as both cohorts remain active. Think about what that does to a mature title. A game with a large, long-tenured player base installed well before June 30 will keep paying the higher 25% rate on that cohort's spend indefinitely, while only new installs after the cutoff earn the lower rate. For a live-service game with strong retention, exactly the kind of title this industry rewards, the commission benefit therefore accrues slowly, tied to how much of total revenue eventually comes from post-June-30 cohorts, rather than landing as an immediate, portfolio-wide saving the way a flat-rate cut would.

Where the reduction is real, and where it is optics

The reduction is real. Google is genuinely giving up revenue share it previously collected in full, and for any developer acquiring meaningfully in the three launch markets after June 30, the 20% rate is a straightforward improvement on unit economics. As a broad, immediate relief measure it deserves more scepticism, because the structure as described concentrates the benefit on new growth rather than existing revenue, and because Google has explicitly left room for the effective rate to move up or down through the unspecified "several factors" Feng referenced. Don't assume 20% is the number that will actually appear on the following month's statement without checking against those criteria directly in the Play Console once the change is live.

Who wins: a framework rather than a verdict

Reading this changed structure honestly produces at least three different answers depending on who is asking. Developers acquiring aggressively into new markets after June 30 win outright, since new cohort revenue pays the lower rate from day one. Developers with large, mature, high-retention player bases installed before the cutoff see a much smaller near-term benefit; most of their revenue sits in the higher-rate cohort for the foreseeable future. And Google keeps meaningful flexibility through the unstated modifying factors in the new rate structure, which means the headline 20% may end up functioning more as a best-case ceiling than a guaranteed floor for most developers.

Modelling the impact on your own Play revenue

A practical exercise for any finance or UA lead with meaningful Play revenue is to split current monthly revenue by whether each player installed before or after June 30, even using rough proxies like registration date or first-purchase date if precise install date isn't readily available. Apply 25% to the pre-cutoff cohort's revenue and 20% to the post-cutoff cohort's, then compare the blended result to what the flat 30% rate would have produced. Then look at the gap. For a hypothetical title generating $2 million a month in Play revenue with 80% of that revenue still coming from players who installed before June 30, the blended commission works out closer to 24% than 20%, a meaningfully smaller saving than the headline figure suggests, and one that only improves as the older cohort's share of revenue naturally declines over time.

What remains unresolved

This announcement lands while Google's broader legal position with Epic is still unsettled. Judge Donato voiced open scepticism about the proposed Play Store settlement as recently as April, and nothing about that scepticism has been publicly resolved. Whether this commission structure survives in its current form, gets folded into whatever final settlement or injunction terms eventually emerge, or gets revised again before most developers see a meaningful benefit, is a genuinely open question that this week's announcement does not close.

Why the regional rollout order is itself a signal

Google chose to start this change in the EU and the UK alongside the US, three of the jurisdictions where regulatory and legal pressure on its Play Store commission structure has been most intense, rather than rolling out globally at once. That sequencing is unlikely to be coincidental. It suggests Google is treating this reduction, at least in part, as a response to the specific legal and regulatory environments applying pressure in those markets, rather than a company-wide reassessment of what Play's commission should be everywhere. Developers whose revenue sits mostly outside those three markets shouldn't assume a comparable cut is imminent on any predictable timeline; keep planning around the existing 30% rate for those markets until Google says otherwise.

A note on comparing this to Apple's fee changes

It's tempting to read Google's move alongside Apple's own sequence of EU fee changes as evidence that platform commissions generally are trending down under sustained legal pressure, and directionally that reading is fair. But the two aren't directly comparable in mechanism. Apple's changes have mostly restructured how it calculates a fee, moving from a per-install charge toward a percentage of revenue, without necessarily lowering the effective rate for every developer. Google's change is a more straightforward headline rate reduction, tempered by the install-date split described above. Model each change on its own terms. A developer operating on both platforms shouldn't assume the direction of travel is identical, since the practical effect on a given title's margin can differ meaningfully between the two even when the press describes both as a step toward lower platform fees.

Related archive reading

These articles provide related context and remain subject to their stated review status.

• Apple's Core Technology Commission and the 5% math
• Apple's EU fee overhaul: a flat 5%, a 26/20/15 ladder, and October 1