← Library
RevenueCat Report Breakdown

Subscription Billing Period: 82% of Games Go Weekly, 68% of Fitness Apps Go Annual

Subscription Billing Period: 82% of Games Go Weekly, 68% of Fitness Apps Go Annual
TL;DR

There is no single best subscription billing period. Match the cadence to how your product delivers value, and your category has effectively already voted. RevenueCat's State of Subscription Apps 2026 (115,000 apps): Gaming is 82% weekly, Productivity 77% monthly, Health & Fitness 68% annual, and the revenue concentrates harder still (Productivity 90.7% from monthly, Health & Fitness 59.2% from annual). On revenue per install, yearly-dominant apps lead at $0.36 (D14) and $0.46 (D60), about 2x monthly's $0.18 and $0.29; weekly ($0.19 / $0.32) rides alongside monthly; lifetime trails at $0.24 by D60 because it never renews. The honest tension: a separate 20,000-app Adapty dataset finds a single weekly plan converts 2 to 7x better than annual, so weekly wins the conversion event while annual wins revenue per install and fits compounding, sustained-journey products. The deciding variable is your value shape. Impulse and utility apps take weekly, months-long journeys can force annual. And ignore the herd: annual's share of durations fell 41.4% to 33.6% year over year (Daphne Tideman: "commitment issues in the current economic climate"), a market behavior, not a target.

The short answer: there's no universal best, your category already voted

Should your app subscription be weekly, monthly, or annual? There is no universal best subscription billing period. The right cadence matches how your product delivers value, and your category has effectively already voted. RevenueCat's State of Subscription Apps 2026 (115,000 apps) shows the split cleanly: Gaming is 82% weekly, Productivity is 77% monthly, Health & Fitness is 68% annual.

Same subscription model, opposite strategies. Guest contributor Thomas Petit calls it "Same model, three completely different strategies." So pick the cadence that fits your value delivery, then read the revenue and retention trade-offs before you lock it in. The rest of this piece is those trade-offs.

Your category voted, and the money follows the vote

The plan-duration mix is not random. It tracks how each category cashes value. Gaming pays off in quick sessions, so 82% go weekly. Productivity is a steady utility you keep on, so 77% go monthly. Health & Fitness is a months-long journey, so 68% go annual (SOSA 2026).

Revenue concentrates even harder than the plan mix. Productivity earns 90.7% of its revenue from monthly plans. Health & Fitness earns 59.2% from annual. The dominant cadence is not just the common one in a category. It's where the money actually is. Cadence is one packaging lever; how many plans you show is the other one worth testing.

The revenue-per-install trade-off: yearly monetizes about 2x better

Revenue per install (RPI) is where the cadences separate. SOSA 2026 classifies each app by its most-sold plan, then measures RPI. Yearly-dominant apps earn $0.36 at D14 and $0.46 at D60. Monthly earns $0.18 then $0.29. Weekly earns $0.19 then $0.32. Yearly monetizes installs about 2x better than monthly at D14.

Weekly and monthly land almost on top of each other, so weekly is not a revenue-per-install loser. Lifetime is the weak one over time: $0.19 at D14 and just $0.24 at D60, because a one-time purchase can't renew. One in four apps still offers a lifetime plan, usually as a small one-time-purchase add-on sitting next to the subscriptions, not as the main plan.

The tension: weekly converts far better, annual earns more per install

Here the datasets disagree, and the honest answer lives in the disagreement. A separate 20,000-app dataset from Adapty finds a single weekly plan converts 2 to 7x better than annual. By that read, leading with annual leaves conversions on the table.

SOSA 2026 pulls the other way. Health & Fitness clusters on annual and earns 59.2% of its revenue there, and yearly-dominant apps carry roughly 2x the RPI of monthly at D14. Both can be true. Weekly wins the conversion event. Annual wins revenue per install and fits products whose value compounds.

The deciding variable is your product's value shape. Impulse and utility apps take the weekly default. A compounding, sustained-journey product can rationally force annual and trade some conversion for cash up front. Yazio, a calorie tracker at $35M ARR, leans on a discounted annual plan and dangles 83% off on a spin wheel. A language app like Duolingo, where value builds over months, fits the same annual shape. Test it, don't assume it.

The market is drifting to shorter terms, and that's a behavior not a best practice

Annual is losing share fast. Its slice of all subscription durations fell from 41.4% to 33.6% year over year, while monthly and weekly rose (SOSA 2026). Prices stayed stable, so this is not a pricing story. Guest contributor Daphne Tideman reads it as "commitment issues in the current economic climate."

Treat the drift as market behavior, not a target. If your product genuinely suits annual, the herd moving to shorter terms doesn't change your economics. It may even leave the annual position less crowded. Decide from your value shape and your price ceiling, not from what the average app happened to do this year.

How to choose your billing period

Building the paywall with an AI coding agent? tasu's MCP is the conversion-expertise layer it calls while it builds, so these billing-period benchmarks arrive sourced, right inside your editor.

  • Start from value shape. Impulse or quick-payoff product, default weekly. Steady utility, monthly is defensible. Value that compounds over months, annual
  • Use your category's vote as a prior (Gaming 82% weekly, Productivity 77% monthly, Health & Fitness 68% annual), then test against it
  • Price the RPI trade-off in. Yearly monetizes installs about 2x better than monthly at D14, so choosing weekly for conversion has a revenue-per-install cost
  • Offer lifetime only as a small add-on. Its RPI trails at D60 ($0.24) because it never renews
  • Don't follow the drift to shorter terms by default. Annual falling from 41.4% to 33.6% is commitment aversion, not a signal your product should drop annual

FAQ

Should my app subscription be weekly, monthly, or annual?

There is no universal best. Match the cadence to how your product delivers value. RevenueCat's State of Subscription Apps 2026 (115,000 apps) shows the category priors: Gaming 82% weekly, Productivity 77% monthly, Health & Fitness 68% annual. Impulse and utility apps default to weekly; a product whose value compounds over months can rationally force annual. Use your category's vote as a starting point, then test against it.

What subscription billing period makes the most money?

On revenue per install, yearly leads. SOSA 2026 (apps classified by most-sold plan): yearly-dominant apps earn $0.36 at D14 and $0.46 at D60, about 2x monthly's $0.18 and $0.29. Weekly ($0.19 / $0.32) rides alongside monthly, and lifetime trails at $0.24 by D60 because it never renews. But a 20,000-app Adapty dataset finds weekly converts 2 to 7x better than annual, so weekly can win more total payers even at lower RPI. Cadence follows your value shape, not one universal winner.

Why are fewer apps offering annual plans?

Annual's share of all subscription durations fell from 41.4% to 33.6% year over year while monthly and weekly rose (SOSA 2026). Prices stayed stable, so it's not a pricing change. Guest contributor Daphne Tideman reads it as "commitment issues in the current economic climate." Treat it as market behavior, not a best practice. If your product suits annual, the herd shortening terms doesn't change your economics.

Should I add a lifetime plan?

Only as a small add-on. One in four apps offers a lifetime plan (SOSA 2026), but its revenue per install trails the others over time: $0.19 at D14 and just $0.24 at D60, because a one-time purchase can't renew. It suits a hybrid model sitting next to subscriptions, not the main plan for a recurring-value product.

Sources

From the tasu brain

Every claim above carries its source and its date. tasu serves the same knowledge over MCP, inside Claude Code and Cursor. Ask while you build.