Free apps can make money through advertising, subscriptions, paid features, marketplace commissions, affiliate referrals or sales of goods and services. A free download is an acquisition choice; it does not identify who ultimately pays the business. The right model depends on the value the app provides and how often people need it.
This is a product-planning guide for founders. If you want to earn by using someone else's app, visit our earning apps directory instead. The using apps versus owning an app guide explains that distinction.
Compare the main revenue models
| Model | Who pays? | What must work? | Main trade-off |
|---|---|---|---|
| Advertising | Advertisers through a network or direct arrangement | Eligible impressions and a tolerable experience | More placements can damage retention |
| Subscription | Customers with a recurring need | Ongoing value and reliable paid access | Cancellation and churn reduce recurring revenue |
| Paid upgrade | Users needing a specific feature or purchase | A clear benefit and understandable limits | A one-time sale must support future costs |
| Marketplace commission | A buyer, seller or both | Completed transactions and useful intermediation | Refunds and support complicate margins |
| Affiliate referral | A merchant or partner | Qualified tracked outcomes | Partner conditions and attribution control payment |
Advertising: model impressions, not installs
Ad revenue depends on served, eligible advertising activity and the yield you receive. An install with no return visit may produce little opportunity. A useful planning equation is served impressions divided by 1,000, multiplied by publisher eCPM. Use a net publisher yield rather than assuming the advertiser's spend is all your revenue.
For illustration, 120,000 served impressions at an assumed ₹80 eCPM produce ₹9,600. That is a hypothetical calculation, not a benchmark for a country or app category. Different audiences, formats and demand can change the result substantially. Your app's own measured data is more useful than another founder's screenshot.
Plan the experience as carefully as the placement. An ad that interrupts a critical action may reduce repeat usage. If a paid tier removes ads, exclude those users' nonexistent ad views from the forecast.
Subscriptions: sell recurring value
A subscription fits a recurring need such as ongoing access, storage, learning or a regularly used workflow. The free tier should make the product understandable while the paid tier offers a meaningful benefit. State the price, billing interval and cancellation route clearly.
The software needs an entitlement lifecycle: when access starts, what happens after payment failure, how a renewal updates access and how cancellation differs from immediate expiry. A purchase screen alone is not sufficient. Backend records should be reconciled with verified provider events, including duplicate and delayed notifications.
Plan for users moving between devices or reinstalling the app. Restoration and account matching affect whether a legitimate customer can use what they bought. These are core product behaviours, not optional cleanup after launch.
Paid features: account for future support
A one-time upgrade can be easier to understand than a subscription when the benefit is discrete. However, a lifetime promise can create costs long after the purchase. Estimate how long you must maintain the feature, store data or respond to support requests before setting the price.
Avoid using an arbitrary paywall to compensate for an unclear product. If users cannot explain the benefit, moving the payment screen earlier rarely resolves that uncertainty. Test whether the feature changes the outcome users care about.
Marketplace commissions: gross sales are not your revenue
Suppose an app processes ₹5,00,000 of monthly transactions and retains a 10% commission. Platform revenue is ₹50,000 before its expenses, not ₹5,00,000. If the platform also bears a hypothetical 2% payment cost on the entire transaction value, that costs ₹10,000 and leaves ₹40,000 before other operations.
Decide who pays each fee, who refunds the customer and what happens to the commission after a return. Maintain a ledger that can explain an order, collection, fee, refund and settlement without guessing from a single balance. Reconciliation becomes more important as transactions increase.
Store billing rules affect the implementation
Digital purchases and physical or real-world services may be treated differently. Requirements also depend on distribution platform, market and programme eligibility. Review the current Apple App Review Guidelines and Google Play payments policy for your exact flow. Do not assume that adding an external checkout button is permitted everywhere.
Calculate contribution before scaling acquisition
Start with monthly revenue, deduct payment fees and per-user service costs, then subtract fixed operations and acquisition spend. Positive revenue can coexist with negative operating profit. If each additional user costs more to serve than they contribute, acquiring more users magnifies the problem under the same assumptions.
Use our app revenue and break-even calculator to compare subscription, ad and marketplace scenarios. It shows operating profit, required active users and simple investment payback. The tool is a steady monthly model; it does not predict retention, growth or demand.
What to measure after launch
- Activation: whether a new user reaches the useful part of the product.
- Retention: whether the same users return over a defined period.
- Conversion: the share of eligible users who become paying customers.
- Refunds and cancellations: revenue lost and the reasons behind it.
- Contribution: what remains after costs that grow with usage.
- Settlement: when earned revenue becomes available cash.
Keep definitions consistent. Comparing lifetime downloads with monthly revenue or a gross transaction value with net fees can make a dashboard look strong while hiding the underlying economics.
Frequently asked questions
How much does an app earn per download?
There is no universal amount. A free install may never produce revenue. Usage, purchases, eligible advertising and costs determine the business result.
Can an app combine ads and subscriptions?
Yes. Define the paid experience clearly and avoid double-counting ad revenue from subscribers who do not see ads.
How many users are needed to break even?
Under a simple monthly model, divide fixed costs by positive contribution per active user. If that contribution is zero or negative, there is no break-even user count under those assumptions.
For implementation, explore Esperto's app monetisation development service. We scope payment events, access rules, reporting and failure cases alongside the customer experience.