Marketplace fees
Use this App Store Fee Calculator to compare branches across worldwide and EU App Store fees, keep CTF and CTC branches exact only when the public rates and your install allocation inputs both exist, and avoid date shortcuts that would turn older EU branches into a made-up single model.
The first decision in this calculator is not the percentage. It is the branch family. Worldwide App Store commission logic and EU branch logic are not the same job, and mixing them too early creates the kind of blended output that sounds convenient while hiding the actual commercial path the estimate came from.
The EU selector is treated as a real resolver key. Alternative terms, communication and promotion of offers, and the StoreKit external purchase link path remain separate branches because the current Apple support pages still keep those families distinct. The tool does not assume the calendar has already replaced them with one final model.
CTF or CTC lines are not automatically non-exact here. They stay exact when the fee branch is public and the missing allocation math has been supplied by the user. If the install-based fee applies but the allocation is absent, the result downgrades itself openly instead of pretending the blended per-transaction answer is already known.
Workflow
App Store Fee Calculator is built around a practical problem: Apple fee questions often fail before the percentages are even applied. Teams ask for one App Store rate, but the real answer depends on whether the branch is worldwide, tied to a specific EU commercial path, or affected by install-based platform fees that need to be spread across some user-supplied transaction count. If the branch is resolved loosely, the numeric answer inherits that looseness.
This calculator makes the branch explicit first. That keeps the result more trustworthy because the user can see whether the estimate came from a worldwide public commission path, an EU branch family, or a branch that still needs allocation or eligibility detail before it can claim exactness.
How it works
A common mistake in platform-fee tools is to treat install-based fees as permanently fuzzy. This page does not do that. If Apple publishes a numeric branch and the user supplies the missing allocation needed to express an install-based fee as a per-transaction estimate, the branch can still be exact. The exactness decision is not about whether the fee is install-based in the abstract. It is about whether every fee line shown in the result is either public and numeric or directly supplied by the user as part of the allocation input.
That rule is why the coverage reasons matter. The page can say missing install allocation, eligibility unknown, or public numeric schedule with user allocation instead of collapsing all those cases into one generic confidence label.
Limits
The calendar alone is not enough to collapse Apple's EU structure here. As of March 15, 2026, Apple's current support content still contains language that points to multiple EU branch families rather than one settled replacement model. That means a browser calculator should not invent a final state just because the user is asking after a future-looking milestone date. If Apple later publishes a normalized numeric replacement, that can become a new branch family. Until then, the safer approach is to keep the older branches selectable and explicit.
That choice makes the tool slightly more complex, but it also keeps it aligned with the public support pages the user can verify for themselves. Precision without source-backed branch discipline is not trust; it is presentation.
Use cases
Use App Store Fee Calculator when you are comparing a worldwide commission path with an EU branch family, preparing an internal pricing note, or trying to determine whether the only blocker to exactness is missing install allocation. It is also useful when a team needs to understand why two App Store answers that sound similar are actually grounded in different public branches.
That use case is different from legal advice or account-level reconciliation. The page is there to resolve and explain one public fee branch quickly in the browser, while keeping any remaining ambiguity visible enough that the next step is obvious.
Because exactness is about whether every fee line shown on the screen is resolved, not about whether the fee is based on installs or transactions. If Apple publishes the numeric branch and you supply the allocation needed to express that install-based charge as a per-transaction estimate, the calculator can stay exact while still telling you that user allocation was part of the resolved basis.
The current Apple support pages still keep those branch families explicit on March 15, 2026. A browser tool should not close or auto-migrate them by date alone when the public support content has not yet been replaced by one fully published numeric branch family. Keeping the branches selectable is the safer and more source-aligned choice.
Eligibility matters when a reduced public branch has been selected or when the branch depends on a status the user has not yet confirmed. In that case the page can still show the math for the chosen branch, but it should not claim exactness until the eligibility question has been answered clearly enough to remove that ambiguity from the result.
Use it when you need a fast browser-side view of one App Store branch, want to compare a worldwide path with a current EU path, or need to see whether missing install allocation is the only reason an otherwise public numeric branch has dropped to partial. If the question depends on a private agreement or a branch Apple has not published numerically, this page should be treated as a boundary marker instead of a substitute for legal or commercial review.