How to raise your iOS subscription price without killing your renewal rate

A step-by-step playbook covering Apple's opt-in vs opt-out grandfathering mechanics, how to time and size a price increase, the communication strategy that keeps subscribers on side, and the 60-day metrics that tell you whether it worked.

Raising your subscription price is probably the single highest-leverage pricing move available to an established iOS app — yet most indie developers avoid it for years. The fear is intuitive: show subscribers a larger number at renewal and they cancel. In practice, the outcome almost always looks different. Subscribers who trust a product are far less price-sensitive than developers expect, and the net revenue impact of a well-executed increase typically outweighs the attrition by a wide margin.

This guide covers the full mechanics: how Apple's price-increase infrastructure works, when to pull the trigger, how to size the change, how to communicate it, and how to measure whether it worked.

How Apple's price-increase infrastructure works

Apple treats a subscription price increase differently depending on its magnitude relative to a set of country-specific thresholds that are updated periodically in App Store Connect.

Opt-out (auto-migrated) increases apply when your increase falls within Apple's allowed band — broadly, a modest percentage step within a twelve-month window, applied no more than once per year per subscription product. In this scenario, Apple notifies existing subscribers that the price is changing and renews them at the new rate at their next billing date unless they actively cancel. No explicit consent tap is required. This route produces the highest retention of existing revenue because subscriber inertia works in your favour.

Opt-in (consent-required) increases apply to larger jumps. Apple presents subscribers with a consent sheet; those who do not actively tap “Agree” will have their subscription lapse at the next renewal. This is the higher-risk path — but it is also the correct mechanism when you are making a significant repositioning, not just adjusting for inflation or competitive pressure.

The exact thresholds vary by storefront and change when Apple updates its pricing infrastructure, so always verify current eligibility in App Store Connect before scheduling an increase. Apple's own documentation on managing price increases for auto-renewable subscriptions is the authoritative source. For a detailed breakdown of what grandfathering means for your existing subscriber base, see our post on Apple grandfathering rules for subscription price changes.

When to time the increase for minimum attrition

Timing matters almost as much as magnitude. Several factors consistently correlate with lower churn in the weeks following a price change:

• Immediately after a substantial feature release. Subscribers who just experienced new value are primed to see the price as justified. Announcing an increase on the same day as a meaningful update reframes the message from “we are charging more” to “here is what we built, and here is the price that reflects it.”
• On annual tiers before monthly ones. Subscribers on yearly plans have already committed to the long view. Data from RevenueCat community case studies broadly suggests that churn sensitivity after price increases runs materially lower among annual subscribers, because the cost is already amortised and the renewal decision is already settled for the year ahead.
• Q1 or early Q3, not late Q4. Subscribers tend to audit their active subscriptions in post-holiday periods and around mid-year. Raising prices in November or December risks your notification triggering a broader subscription audit at exactly the wrong moment.
• After at least 90 days of stable engagement data. Subscribers who reach the three-month mark without churning have demonstrated a habit. RevenueCat's 2026 benchmarks analysis found that long-term retention is strongly tied to early engagement depth — which also means the subscribers most likely to survive a price increase are the ones who are already most active in your app.

Sizing the increase: choosing the right magnitude

The right magnitude depends on your current price relative to the competitive set, whether you can stay within Apple's opt-out band, and how confident you are in subscriber loyalty. Undershooting is common: many indie developers raise by a single dollar when data would support a more meaningful step. The table below maps the main scenarios:

A useful sense-check is to look at category pricing after stripping introductory offers from visible App Store prices. If your monthly price is below the median for apps with a comparable feature set, the market effectively validates your headroom. Our pricing tools let you benchmark your current price against App Store tier equivalents across more than 170 markets simultaneously.

The communication playbook

Apple's system sends its own notification — a modal or push message from the App Store — but that notice is terse and impersonal. Your communication layer on top of it is what determines whether subscribers feel informed or blindsided.

In-app messaging (14–28 days before the change): Surface a brief, honest note inside the app itself. One short paragraph is enough. Acknowledge the change, explain what has driven it — ongoing development, new infrastructure, features shipped since they first subscribed — and express genuine appreciation for their support. Avoid defensive framing like “due to rising costs” without context; it reads as a corporate shrug rather than an honest conversation between a developer and their users.

Email (if you have subscriber addresses): A personal-sounding message from the founder or product lead consistently outperforms a transactional notice. Match your usual product voice. Keep it under 200 words. State the specific new price and the effective date so subscribers are not left guessing. A brief recap of what has shipped since they subscribed anchors the value argument without feeling like a sales pitch.

Release notes: If the increase coincides with a new version, mention it factually in the App Store release notes alongside the new features. This reinforces the narrative that the price reflects expanding value, rather than arriving out of nowhere.

What to avoid: announcing the change only in a changelog line that most users never read; framing the increase as temporary unless you genuinely plan to reverse it; over-apologising (it signals doubt); giving subscribers fewer than 14 days before the consent window closes.

Measuring impact: the 60-day read

Do not judge a price increase in the first 30 days. Subscriber behaviour in the first billing cycle after a change is noisy: some subscribers cancel preemptively on hearing the news; some who were already planning to churn do so now rather than later; some renew before they have noticed the change. A cleaner signal arrives after 60–90 days.

The metrics worth tracking:

• Renewal rate for the existing-subscriber cohort. Compare the 60-day renewal rate for this cohort against the same metric for a matching cohort from three months before the increase. This isolates the price effect from seasonal noise.
• New-subscriber conversion rate. A price increase sometimes reduces trial-to-paid conversion for new users arriving after the change. Track this separately from existing-subscriber retention — a 10% drop in new conversion offset by a 30% increase in per-subscriber revenue is still a strong net win, but you want to see both numbers clearly.
• MRR delta at day 60. The real test: is monthly recurring revenue higher than it was before the increase, accounting for the subscribers who left? In most well-executed increases on apps with strong existing retention, the answer is yes.
• Support ticket and review volume. A manageable spike in “why did my price go up?” support messages is normal and expected. A spike in refund requests or a wave of negative App Store reviews is a signal that either the communication was insufficient or the magnitude was too aggressive relative to perceived value.

App Store Connect's subscription event reports break transactions into discrete types — initial purchase, renewal, cancellation, price-increase consent, and more — making it possible to isolate exactly how many existing subscribers consented, how many lapsed, and how many cancelled before renewal even arrived. Our post on reading Apple Sales and Trends for global pricing decisions walks through how to navigate those reports efficiently and export the cohort data you need.

Sources and further reading

• Apple Developer Documentation — Managing Price Increases for Auto-Renewable Subscriptions
• Apple Developer — Auto-Renewable Subscriptions overview (pricing and price management)
• RevenueCat — The State of Subscription Apps: lessons, trends, and benchmarks for 2026
• RevenueCat — 20% of your churned users will come back — but are you ready?
• Phiture Mobile Growth Stack — subscription retention and pricing research
• AppFollow Blog — app store review and subscription management analysis