How to Legally Avoid the 30% Apple App Store Commission in 2026

Why Fora Soft wrote this playbook

Fora Soft has been shipping iOS products since 2005. We build streaming apps (Vodeo), e-learning platforms (Scholarly, BrainCert), and dozens of consumer and B2B apps — many of which had to answer the same question: “do we really have to give Apple 30% of everything?”

The answer in April 2026 is “only if you architected yourself into it.” The regulatory landscape has shifted dramatically since 2023: the EU Digital Markets Act, the Epic v. Apple Ninth Circuit ruling, the arrival of the Core Technology Commission, and Apple’s own small-business programs have rewritten the rules. This article covers what actually works, what the current rates are by jurisdiction, and what a vendor like us would do to re-architect an existing iOS product for lower commission — without getting the app rejected at review.

Apple commission rates in 2026 — the actual numbers

The “30%” headline is still technically correct for standard large-developer in-app purchases, but it’s one of five rates Apple runs in parallel.

The Small Business Program — 15% for under $1M proceeds

Apple’s Small Business Program (ASBP) cuts commission from 30% to 15% for any developer whose total App Store proceeds — not gross revenue, net of Apple’s take and taxes — were below $1M in the previous calendar year. You apply through App Store Connect; approval lands about 15 days after your fiscal-month end.

Three things developers get wrong:

1. Proceeds, not revenue. The $1M cap is measured on what hits your bank account, not what customers pay gross. A developer with $1.15M in gross revenue and 15% Apple take is at ~$977k in proceeds and still qualifies.

2. Free trials don’t count toward the 1-year sub cliff. If you have 12 months of paid conversions for 85% retention, you hit the 15% sub rate — regardless of free-trial time before that.

3. Re-qualifying is real. If you crossed $1M in year 1, got kicked out, and fall back under $1M in year 2, you can re-apply. The cap is checked annually, not once.

For most indie and mid-market apps, ASBP is the answer to the “do I really pay 30%?” question. The only reason not to use it is if you’re already over $1M, in which case the next patterns become relevant.

Digital Markets Act in the EU — what actually changed

The DMA took effect in March 2024. The European Commission fined Apple €500M in April 2025 for non-compliance, and Apple rolled out a comprehensive rework of its EU rules by June 2025. From 1 January 2026, the old Core Technology Fee (€0.50/install after 1M) was replaced by a layered Core Technology Commission (CTC).

The new EU math, for apps using the external-payment entitlement:

Total: roughly 12–20% for EU developers using the formal entitlement. Smaller developers (under €10M global revenue) qualify for partial exemptions. For a fast-growing EU app, this new math is often worse than the old CTF, not better — run the numbers for your specific volume before opting in.

One striking data point from Apple’s own November 2025 study: more than 90% of EU developers did not pass DMA savings on to consumers. Whatever margin developers recaptured went to their own P&L, not to users. That’s worth remembering when weighing the operational complexity of opt-in.

Alternative marketplaces have not been the revolution the DMA promised. MacPaw’s Setapp Mobile shut down in February 2026 citing “complex business terms”; most EU users still install apps via the App Store. Plan accordingly.

The US after Epic v. Apple — 0% external-link commission (for now)

The US story is simpler and, at the moment, more developer-favourable. Three dates matter:

30 April 2025. Judge Yvonne Gonzalez Rogers found Apple in “willful contempt” of her 2021 injunction. Apple had been charging 27% on external-payment transactions, which the court ruled made the injunction meaningless.

May 2025. Apple updated App Store Review Guidelines 3.1.1 and 3.1.3 for the US to explicitly allow external-payment links, buttons, and calls to action. No entitlement, no approval process, no commission.

December 2025. The Ninth Circuit partially reversed: it upheld the contempt finding but allowed Apple to charge a “reasonable commission” tied to demonstrable costs. The exact fee is TBD pending district-court approval. As of April 2026, no fee is in effect.

April 2026. Apple filed a Supreme Court petition seeking to overturn the contempt ruling. Certiorari has not yet been granted; even if granted, a decision would likely arrive in 2027.

Practical guidance for US-targeted apps in April 2026: you can ship an external payment button today at 0% commission, but design your implementation so you can flip on a commission calculation later without re-architecting. Capture external-purchase analytics from day one; you’ll need them when/if a fee is set.

The reader app rule — if you qualify, you probably should use it

Apple defines a “reader app” as one whose primary function is letting users access content they already purchased or subscribed to elsewhere. Qualifying categories:

• Magazines, newspapers, books

• Audio, music, podcasts

• Video, including streaming services

Examples: Netflix, Spotify, Kindle, Audible, Medium, NYT. If you qualify and apply for the External Link Account Entitlement, you can put a link inside the app that opens an external browser to your sign-up / subscription page. Purchases made on your website carry zero Apple commission.

Rules that trip people up:

1. External browser, not web view. The link must open in Safari or the user’s default browser. A WKWebView inside your app gets rejected.

2. No price information on the link. You can’t advertise “Sign up for $9.99/month” next to the external link. “Manage subscription” or “Create account” is fine.

3. You can still offer IAP in parallel. Netflix doesn’t, but some reader apps offer both a higher-priced IAP and a cheaper external option. Apple permits it; it’s a UX choice.

Approval typically takes 2–4 weeks. Apply early.

Physical goods and real-world services — always 0%

Apple’s 30% (or 15%) only applies to digital goods and services. If the buyer walks away with a physical object or a real-world service, IAP is forbidden — use Stripe, Adyen, PayPal, or your payment processor of choice, and keep 100% minus their per-transaction fee (typically 2–3%).

Examples clearly on the “physical” side of the line:

• E-commerce of any physical product (clothing, hardware, food)

• Travel bookings (flights, hotels, rental cars)

• On-demand services (ride-share, food delivery, cleaners, haircuts)

• Event tickets and venue reservations

Gray-zone cases that have caused rejections: cloud storage of user-owned files (digital), online tutoring where the tutor is a real person and the session is real-time (physical, technically), in-person classes booked through a digital booking flow (depends on the review’s opinion). When in doubt, structure the transaction so the digital component is the minor part.

The web-first purchase pattern — the cleanest 0% strategy

For non-reader apps that want to bypass IAP entirely, the practical pattern is: move sign-up and billing to your website; keep the iOS app as a consumption surface only. Users sign up on yoursite.com, pay via Stripe, receive credentials, and the iOS app authenticates against your API for access.

This is how many B2B SaaS products work on iOS today (Slack, Notion, Figma) — the iOS app is free; the paid plan is purchased via the web. Apple explicitly allows it as long as:

1. The app has meaningful free functionality. A login-wall-only app with no free utility gets rejected as a “thin client” under Guideline 4.2.

2. You don’t direct users to the web from inside the app (outside the US and qualifying EU flows). In non-US/non-EU jurisdictions, you still can’t include a “Sign up at example.com” link. Users must find your website on their own.

3. No in-app friction that pushes users to web. Artificially degrading the free tier to drive web signups can trigger a rejection.

Build effort for re-architecting an existing subscription app to web-first is typically 200–500 dev-hours — usually 3–6 weeks at Fora Soft using agent-assisted engineering. Break-even on the commission saving is often in the 3–6 month range for apps above $200k ARR.

External payment entitlement (US & EU) — in-app links that work

The External Purchase Link entitlement is what lets you include a “Subscribe on our website” button inside the app, with the link opening in an external browser. US App Store: no entitlement required as of May 2025, 0% commission. EU App Store: entitlement required, ~12–20% CTC applies.

Implementation checklist for apps that plan to use it:

1. StoreKit external purchase APIs. Even in the US where it’s not strictly required, using the official APIs future-proofs your code if Apple imposes a fee later.

2. Apple’s required disclosure sheet. Before the external browser opens, Apple requires an on-device sheet explaining that the user is leaving the App Store. Your app must show it.

3. Storefront check. Gate the external link behind SKStorefront so US users see it, non-US users don’t (unless your EU entitlement is approved).

4. Analytics and reporting. Report external-purchase revenue to Apple per the commercial terms for your region. Required in the EU; prudent in the US in case a fee is re-imposed.

Enterprise distribution (ADEP) — 0% but narrow scope

The Apple Developer Enterprise Program (ADEP) lets organisations with 100+ employees distribute apps privately to their own staff. No App Store review, no commission. $299/year developer-program fee.

This is the right tool for:

• Internal employee apps (HR, field operations, sales enablement)

• Line-of-business tooling deployed via MDM

• B2B apps with a fixed, known enterprise customer list who can MDM-deploy on their staff’s devices

Not the right tool for consumer apps. Apple audits ADEP usage; redistribution of an enterprise app to the public is a program-termination event.

Mini case — cutting effective commission from 30% to 4%

A B2B productivity client came to Fora Soft paying Apple 30% on auto-renewing subscriptions. Their ARR was approaching $900k and they were about to cross the SBP cap, which meant all new revenue would be at 30%.

We re-architected their flow in 5 weeks: signup and plan selection moved to the web, Stripe became the system of record, the iOS app became free and authenticated against their API. Existing IAP subscribers were offered a one-time migration incentive (20% off lifetime) to move to Stripe billing; 58% took it. Within one quarter, effective commission dropped to about 4% (Stripe + processing), and the ARR crossed $1M without triggering the cliff.

Want the same analysis on your product? Book a 30-minute call and we’ll walk through your numbers live.

Cost and timeline to re-architect for lower commission

With Fora Soft’s agent-assisted engineering, ranges below reflect recent iOS commission-reduction projects. Your specific stack and the maturity of your web infrastructure will move numbers up or down.

Break-even analysis is simple: if the project cost is < 6 months of commission savings, it’s a clear win. For apps with $200k+ ARR and a 30% baseline, most strategies pay back in a single quarter. See our software estimating guide for the math we run on these projects.

A decision framework — pick your commission strategy in five questions

Q1. Are your App Store proceeds under $1M last calendar year? Yes → enrol in the Small Business Program today. No → continue to Q2.

Q2. Does your app sell physical goods or real-world services? Yes → IAP is prohibited; use Stripe or equivalent. No → continue to Q3.

Q3. Is your app category eligible for reader-app treatment (magazines, books, music, podcasts, video)? Yes → apply for the External Link Account Entitlement. No → continue to Q4.

Q4. Is your primary revenue from US users? Yes → add US external-payment links; 0% today, plan for a TBD future fee. Mixed US/EU → implement both flows with storefront-based gating.

Q5. Is the majority of your revenue from subscriptions and you’re over $1M? Yes → a full web-first re-architecture usually has the best ROI. No → pick a smaller lever (external link, SBP, or category shift).

Five pitfalls that get commission-avoidance apps rejected

1. Using a WebView as “external browser”. The link must open in Safari / the user’s browser, not a WKWebView. Rejection is automatic.

2. Price advertising next to external links. “Subscribe on web for $9.99” violates the reader-app rules. “Manage your subscription” is fine.

3. Thin-client apps. An app with no meaningful free functionality whose only job is to collect a login gets rejected as a wrapper. Ship real utility in the free tier.

4. Mis-classifying digital as physical. Cloud-only subscriptions, game currencies, and unlockable software features are always digital. Don’t try to argue around it; Apple reviewers are not amused.

5. Ignoring storefront gating. Shipping a US external-link feature to EU users triggers CTC fees you weren’t expecting. Always gate by SKStorefront.

KPIs — measuring commission-avoidance success

Financial KPIs. Effective commission rate (weighted average across all channels; target <20% for non-SBP, <10% for reader/web-first), monthly cash uplift vs. pre-change baseline (should be >70% of the theoretical max within 90 days), payback period on engineering effort (target <6 months).

Conversion KPIs. In-app to web-checkout completion rate (healthy range 25–50% depending on category), IAP-to-external migration rate for existing users (target >40% for a well-executed migration), time from external-link click to paid (target under 3 minutes).

Compliance KPIs. App Store review pass rate (target 100% after re-architecture), user complaints about payment friction (target no material uptick), external-purchase reporting accuracy (required in EU; 100% reconciliation monthly).

When the 30% is actually fine

Sometimes the simple IAP flow wins. Keep the standard 30% path when:

• You’re under $1M proceeds (SBP auto-covers you at 15%).

• Conversion matters more than margin. IAP is the highest-conversion payment flow on iOS — Apple ID is already in the device and family-sharing works. Moving billing off-app typically drops conversion 20–40%.

• You don’t have web infrastructure. Building billing, auth, webhooks, email receipts, dunning, and refunds from scratch is real work. If you don’t run a web product already, the hidden cost is substantial.

• Your LTV is low. 30% of $4 is $1.20; the engineering cost of commission avoidance is usually higher than the lifetime margin improvement on low-ARPU consumer apps.

• Your user base is global and fragmented. Running US, EU and Rest-of-World payment flows simultaneously is 3x the work of running one. Sometimes a uniform 15% through the App Store is the cheaper operational choice.

How Google Play compares — quick take

Because many of our clients ask about both platforms: Google Play has a broadly similar structure but looser enforcement. Standard 30% with a 15% tier for the first $1M in annual revenue (no program opt-in required — applied automatically per developer account). Subscription second-year drop to 15%. Since 2022 Google has allowed external payment providers via the User Choice Billing program; developers can direct users to alternative billing, Google still charges a reduced fee (typically 26% instead of 30%).

The net effect in 2026: Android is slightly more developer-friendly on commission terms but the overall ecosystem pressure matters less because iOS users spend ~2–3× more per capita. For most apps, iOS optimization has higher commission-savings ROI than Android.

FAQ

What to read next

Ready to stop paying 30%?

Apple’s commission is negotiable now in a way it wasn’t in 2023. Between the Small Business Program, the US external-link flow, the reader-app entitlement, and EU external-payment options, almost every legitimate iOS product can legally move below 20% effective commission — often below 10%, sometimes to zero — without risking rejection.

The catch is the implementation details: storefront gating, StoreKit API conformance, disclosure sheets, reader-app entitlement applications, and the operational complexity of running two or three billing paths in parallel. Fora Soft has shipped every one of these patterns in production. If you want a ranked list of commission-reduction levers tailored to your app, plus a fixed-fee estimate, start with a 30-minute call.