Marketplace fees
Use this Google Play Fee Calculator to compare Play regimes across current Google Play fees and the 2026 EEA business model, resolve the model before date inference, and show when downloaded-app or external-offer branches still need allocation or market rollout inputs before they can claim exact coverage.
This calculator is strict about precedence because current Play programs and the 2026 EEA business model are different commercial models, not just different dates. Selecting the model first keeps the page from silently switching a current path into the newer model when the date moves forward.
Google Play fee questions often sound like one percentage question, but the public sources split the answer across service-fee pages, user-choice billing programs, EEA conditions, external offers, and the 2026 EEA business model. Program path and market need to stay visible so the user can see exactly which public regime was resolved.
Most percentage-based Play branches do not need user allocation. Downloaded-app external-offer paths can, because the public source includes fixed per-install service fees that have to be expressed as a per-transaction estimate somehow. When that allocation is missing, the page stays partial instead of manufacturing a neat blended answer.
Workflow
Google Play Fee Calculator is built for branch discipline first and arithmetic second. That is important because Google Play now exposes multiple public commercial paths that can look similar if you only skim the percentages. A user choice billing path, an EEA external-offers path, and a 2026 EEA business-model path may all sound like variants of the same question, but they are not interchangeable. If the resolver chooses the wrong regime, the numeric result can still look polished while being anchored to the wrong source.
This tool makes the model, program path, market, and date part of the resolved basis. That keeps the result easier to audit and prevents date alone from doing work it should not be doing.
How it works
A common failure mode in fee calculators is to use the date as a shortcut for commercial intent. That is not safe here. The March 4, 2026 Android Developers Blog post introduces a new EEA business model with its own rollout timing, but that does not mean a current Play program path should quietly migrate into that model once the date passes. The resolver in this tool handles the commercial model first, then the program path, then market and date. That order keeps the user's chosen public regime intact.
It also makes testing stronger. You can prove that current EEA paths remain current when selected directly, while the newer EEA model becomes exact only when the model, market, and rollout date all line up.
Limits
Some Google Play branches are straightforward percentage schedules. Others depend on rollout timing or fixed per-install service fees that need to be spread across a user-defined transaction count. Those gaps are not bugs in the calculator. They are real differences in what the public source has already made numeric and what the user still has to supply in order to convert a policy into a per-sale estimate.
That is why the coverage reasons are ordered. A result can say market rollout not effective, missing install allocation, or eligibility unknown in a way that matches the actual blocker. The user can then see whether they need to wait for the public rollout, confirm a program status, or simply provide the missing allocation input.
Use cases
Use Google Play Fee Calculator when the team is debating whether a fee question belongs to a current Play program or to the 2026 EEA business model, when you need to test an EEA external-offer path with or without allocation, or when you want to show exactly which public resolver inputs changed the answer. The value is not just the number. It is the fact that the number stays attached to the chosen public regime.
That makes the tool useful for pricing reviews, planning notes, and internal comparisons where the wrong regime can create a polished but misleading answer. The browser page stays narrower than account analytics, but that narrow scope is what keeps the public fee branch auditable.
Because the commercial model is the bigger branch decision. A current Play path and the 2026 EEA business model are not just versions of the same schedule. They come from different public regimes. The resolver keeps that choice first so a current path does not become a newer one automatically just because the date is later.
Those public EEA external-offer terms include fixed per-install service fees for downloaded apps. If you want a per-transaction estimate in the browser, that fixed fee has to be spread across some user-supplied transaction count. Without that user input, the calculator can still identify the branch, but it should not claim the blended fee is exact.
The March 4, 2026 Google announcement publishes numeric terms for the new EEA business model, but those terms still depend on market and rollout timing. If the market or date gate has not been met, the branch can be identified while still remaining informational because the public rollout has not yet made that path effective for the chosen resolver inputs.
Use it when you need a source-backed browser estimate for one clearly selected Play regime, want to compare a current program path with the new EEA business model, or need to see whether the only blocker to exactness is rollout timing or a missing allocation input. If the question depends on unpublished commercial detail, this page should be treated as an honest public-schedule boundary instead of a replacement for account-level review.