Average Revenue Per User: iOS Subscription App

What ARPU actually measures — and why the denominator matters

ARPU is the ratio of revenue to users over a given period, but "users" is where most benchmarking goes wrong. The figure means nothing without its denominator. Revenue per install (RPI) counts every download in the base. Revenue per paying customer counts only those who converted. These two numbers can differ by an order of magnitude for the same app, so always confirm which one a benchmark is reporting before comparing it to your own dashboard.

Per RevenueCat's State of Subscription Apps 2026 — covering 115,000+ apps, $16B+ tracked revenue, and 1B+ transactions (primarily 2025 data) — median revenue per install across all categories is $0.23 by day 14 and $0.34 by day 60. Those are install-based figures, not paying-subscriber figures.

Median year-one realized LTV per paying customer sits at $23 globally and $32 in North America, per the same report. That's the paying-customer denominator. Use the install-based figure when sizing UA spend; use the paying-customer figure when setting price.

ARPU benchmarks by segment

The "average" ARPU for an iOS subscription app is not a useful operating number. What matters is where your app sits across three dimensions: geography, category, and paywall model. The table below organizes the key figures from RevenueCat's State of Subscription Apps 2026.

Source: RevenueCat's State of Subscription Apps 2026; 115,000+ apps, $16B+ tracked revenue, 1B+ transactions (primarily 2025 data). "—" means the report does not break out that specific cross-segment figure.

A few things to read from this table before moving on. Hard-paywall apps generate roughly 8x higher RPI at day 60 than freemium apps ($3.09 vs. $0.38), per RevenueCat's State of Subscription Apps 2026. That's a structural effect: hard paywalls select for users willing to pay, compressing the denominator dramatically. But that selection also excludes users who'd have paid later — which is the real trade-off the table doesn't show. See the hard paywall vs soft paywall decision framework if you're weighing a switch.

How geography moves the needle more than most founders expect

Geography is the most under-managed ARPU lever for apps that run a single global price. North America produces a median day-60 RPI of $0.55 vs. $0.11 in India and Southeast Asia — a 5x gap — per RevenueCat's State of Subscription Apps 2026. Year-one realized LTV follows the same pattern: $32 in North America vs. $23 globally.

The practical implication: if your install mix is skewing toward lower-purchasing-power regions and you haven't localized pricing, your blended ARPU will drift down even if your product improves. This is where price benchmarking by storefront becomes a concrete action, not a nice-to-have. AppApex's Price Benchmarker surfaces regional pricing gaps against competitors in your category, which is the first step before testing a localized price.

Trial conversion also varies by region. Median trial-to-paid conversion is 34.2% in North America vs. 15.2% in India/Southeast Asia, per RevenueCat's State of Subscription Apps 2026. Lower conversion in a region means fewer paying customers in the denominator, which further compresses your paying-user ARPU even if subscribers in that region pay similar prices.

Does paywall model affect who stays — or just who converts?

This is where the generic advice gets the mechanism wrong. Most growth content implies that hard paywalls "increase retention" because they filter for more committed users. The data doesn't support that framing. Per RevenueCat's State of Subscription Apps 2026, year-one retention of yearly subscribers is nearly identical across paywall models — approximately 27% for hard paywall vs. approximately 28% for freemium. The paywall model changes who converts, not who stays.

So when you're modeling ARPU, the real paywall question is a revenue-mix question, not a retention question. Hard paywalls produce higher RPI by shrinking the install denominator (fewer people ever make it to the paying stage), not by making those who do convert more loyal. If your ARPU looks great on a hard-paywall model but your total paying subscribers are thin, you may be optimizing a ratio while starving volume.

Why trial length is an ARPU lever most apps leave on the table

Trial length directly affects how many users reach paying status — and the industry is largely running the wrong length. Per RevenueCat's State of Subscription Apps 2026, median trial-to-paid conversion is 42.5% for trials of 17–32 days vs. 25.5% for trials under 4 days — longer trials convert roughly 70% better. Yet the share of apps using sub-4-day trials rose from 42.1% in the 2025 report to 46.5% in the 2026 report. More apps are moving toward the length that converts worse.

The mechanism is counterintuitive: a longer trial doesn't just give users more time to adopt — it self-selects for users who are genuinely evaluating the product rather than impulsively starting and abandoning. Those users convert at higher rates and, because they've actually used the product, churn at lower rates in the first month. Per RevenueCat's State of Subscription Apps 2026, 55.4% of all 3-day-trial cancellations happen on day 0, and 84% happen between day 0 and day 1 — users on short trials are deciding almost immediately, before they've seen enough to commit. If you're running a 3-day trial and your ARPU looks soft, that's where to look first. The guide to increasing trial-to-paid conversion on iOS walks through the specific mechanics.

How category context changes what "good" ARPU looks like

Median year-one realized LTV per paying customer is $62.19 for high-priced apps vs. $23 globally, per RevenueCat's State of Subscription Apps 2026. Category matters too: day-60 RPI for Health & Fitness is $0.66 — nearly double the $0.34 global median. AI apps sustain a 41% year-one realized-LTV premium over non-AI apps ($30.16 vs. $21.37 median), per the same source.

What this means operationally: comparing your ARPU to a global average is almost always misleading. A $0.40 day-60 RPI is strong for a Gaming app (where the median download-to-paid conversion is just 1.0%, per RevenueCat's State of Subscription Apps 2026) and weak for a Health & Fitness app operating in North America. Frame your target as a category-and-geography pair, not a single number.

What to actually do when your ARPU is below benchmark

Diagnosing low ARPU requires separating three distinct problems that look the same in aggregate revenue data.

1. Low conversion rate — fewer installs reach paying status, which inflates your install-denominator and drags down RPI. Check your trial-to-paid rate against the 42.5% median for 17–32-day trials (RevenueCat's State of Subscription Apps 2026). If you're running a short trial and converting below 25%, start there.
2. Low price relative to category — your conversion rate may be fine, but you're leaving per-subscriber revenue on the table. Use the Price Benchmarker to see where you sit versus competitors by storefront.
3. High early churn — per RevenueCat's State of Subscription Apps 2026, the first month accounts for 35% of all annual-plan cancellations. If your ARPU degrades steeply between day 30 and day 60, retention is the bottleneck, not conversion. The churn rate benchmarks for iOS subscription apps give you a category-appropriate floor to compare against.

Billing errors are also a silent ARPU drag worth auditing: they cause 14% of subscription cancellations on the App Store, per RevenueCat's State of Subscription Apps 2026. That's involuntary churn — real margin lost without any product failure on your part.

Once you've identified which of the three problems is primary, the fix is different in each case. AppApex's Conversion agent diagnoses paywall and onboarding leaks; the Retention agent runs churn autopsies and flags winback opportunities; and dozens of specialized agents (including refund forensics and pricing watchers) surface the secondary signals that raw ARPU data buries.

If you want a fast read on where your specific app stands, run it through the free Growth Audit — enter your App Store ID, get a health score and analysis in under five minutes, no account required.