Mobile App Store Fees: What Developers Actually Pay in 2026
Archi4 min read
Contents
- The headline number is rarely the whole bill
- The base rate and the cuts around it
- The processing fee nobody quotes in the pitch
- Regional rules are rewriting the arithmetic
- Small developers, large install bases
- What users actually pay
- Refunds, chargebacks, and the float
- The alternatives and their own bills
- What to watch in the next year
The headline number is rarely the whole bill#
Ask a mobile developer what they pay to sell an app and you will usually hear one figure: 30%. That number has been the anchor of app store economics since 2008, and it is still the default for most transactions. But the effective rate varies widely, from zero in some programs to well above 30% once payment processing and currency conversion are layered on. For a team deciding where to ship, or for a user wondering why an in-app purchase costs more on one platform than another, the gap between the sticker rate and the real cost matters.
The base rate and the cuts around it#
Apple and Google both reduced their standard commission to 15% for developers earning under $1 million per year in net revenue. The larger 30% rate applies above that threshold and to most in-app purchases. Subscriptions get a different schedule: after a subscriber stays for one year, the rate drops to 15% on both platforms. These tiers are not trivial. A small studio with $400,000 in annual app revenue pays roughly $60,000 in commission instead of $120,000, a difference that often decides whether a second hire is possible.
The processing fee nobody quotes in the pitch#
When a developer sells a digital good inside an app, the store handles the payment and takes its commission out of the gross. When a developer sells a physical good or a service consumed outside the app, many jurisdictions now allow an external payment link. That link does not come free. Payment processors charge roughly 2.9% plus a fixed fee per transaction, and those charges sit on top of whatever commission the store still collects. The result is a blended cost that can land between 3% and 33%, depending on the category, the region, and the payment route.
Regional rules are rewriting the arithmetic#
Europe's Digital Markets Act forced Apple and Google to open alternative payment routes in the EU. Apple responded with a reduced commission on external purchases plus a separate core technology fee for high-volume apps. Google introduced a similar structure. The headline commission looks lower, but the fixed per-install charges can punish a free app with a large user base. A developer with 5 million annual installs and modest in-app revenue may find that the new structure costs more than the old 30% did. This is not a hypothetical: several mid-sized studios have publicly modeled the crossover point and found it sits well below the install volumes that regulators expected.
Small developers, large install bases#
The apps most exposed to per-install fees are not the ones making money. They are the free tools, utilities, and games with broad reach and thin monetization. A flashlight app with 20 million downloads and almost no purchases can owe more under an install-based model than under a revenue share. That inversion is the quiet story of the 2024 to 2026 fee changes, and it is pushing some developers toward web distribution or toward charging for the app up front.
What users actually pay#
The commission is invisible to users, but it shapes prices. A $9.99 monthly subscription sold through an app store nets the developer about $8.49 after the 15% rate, or $6.99 after 30%. To hit the same net revenue, a developer selling outside the store can charge less or keep more. Some large services, notably music and video streamers, have raised in-app prices specifically to offset the commission, which is why the same subscription often costs a few dollars more when bought through the app. Users who subscribe on the web and sign in on the phone typically pay the lower price.
Refunds, chargebacks, and the float#
Stores also handle refunds, and the cost lands on the developer's ledger. A refunded purchase reverses the commission but not always the payment processing fee. Chargebacks add administrative overhead. Meanwhile, the store holds funds for a payout cycle that can run 30 to 45 days, which functions as an interest-free loan from developers to platforms. For a studio with $2 million in annual revenue, that float is worth tens of thousands of dollars in working capital each year.
The alternatives and their own bills#
Selling through a web storefront avoids the commission but adds payment processing, tax compliance, fraud screening, and customer support. In the EU and parts of Asia, the savings can be real. In the US, recent court rulings have loosened some restrictions, but the practical picture is still shifting. Developers who move distribution to the web often find that acquisition costs rise because they lose the store's discovery surface. The commission, in other words, buys more than payment processing. It buys placement, trust signals, and a billing relationship most small teams cannot replicate cheaply.
What to watch in the next year#
Three numbers will decide the next round of this argument. The first is the core technology fee threshold in the EU. The second is the share of revenue that moves to external payment links in markets where they are allowed. The third is the effective commission rate for subscription apps after the first year, which is where most recurring revenue now sits. Developers who model all three, rather than the headline rate alone, will have a clearer view of what their app actually costs to sell.
More articles