What is ARPPU (Average Revenue per Paying User)?
ARPPU is the average revenue generated by customers who paid during a specific period (month, quarter, year).
It focuses on monetization quality among payers—useful when most users don’t pay and blended averages hide real pricing and conversion dynamics.
In corporate finance terms, ARPPU helps connect pricing and revenue quality to unit economics (LTV, CAC, payback), operating leverage, and ultimately value creation.
Formula
Example
A SaaS has monthly revenue from paying users of $120,000 and 2,500 paying users.
So ARPPU is $48 per paying user per month.
Annualized per paying user:
That’s $576 per paying user per year, which can be used alongside churn and gross margin to pressure-test LTV and CAC payback assumptions.
How to Use the ARPPU (Average Revenue per Paying User) Calculator
Frequently Asked Questions
Who counts as a “paying user” for ARPPU — do trials or free users count?
Count only unique users who actually paid during the selected period. Free users don’t count, and free-trial users shouldn’t count until they’re billed.
Should “Revenue from paying users” be gross revenue or net revenue (after refunds, taxes, fees)?
Use the revenue definition you’ll actually compare over time. For SaaS unit economics, net revenue you keep (after refunds; excluding VAT/sales tax) is usually more decision-useful—just stay consistent.
Why does the calculator show “ARPPU (monthly, normalized)” and “ARPPU (annualized)” — when should I use each?
Use “per selected period” for a clean snapshot of that exact time window. Use “monthly, normalized” to compare performance across different period selections. Use “annualized” when you want an annual run-rate view for planning or benchmarking.
ARPPU vs ARPU — which one should I track for freemium SaaS?
Track both. ARPPU tells you how well you monetize payers (pricing/upsell impact). ARPU blends payers + non-payers, so it’s heavily driven by conversion rate and is better for overall monetization efficiency.
Sources & Methodology