The default that works for most subscription apps: show the paywall at the end of onboarding, after a personalization loop has made the value concrete, and before the user settles into a free experience. Motivation peaks right after install and decays with every session; a paywall placed after "I can see this working for me" and before that decay is the highest-converting moment most apps have.
Why placement beats design
Teams burn weeks polishing paywall layouts and minutes deciding where the paywall goes. The order should be reversed. A plain paywall at the right moment outperforms a beautiful one shown before the user understands what they would be paying for. Design is worth testing, but placement and framing set the ceiling.
The subscription data backs the urgency. In RevenueCat's State of Subscription Apps 2026, built on over 115,000 apps, conversion is heavily front-loaded in the first session and the first days after install. If your paywall strategy assumes users will discover it in week two, most of them were never going to see it.
The three placements that work
- End of onboarding (the default). The personalization loop builds a concrete picture of value, the paywall lands as its natural conclusion. Works across most categories.
- On the locked feature. The user reaches for something premium and the paywall explains exactly what unlocks. Highest intent, lower traffic. Best as a second surface, not the only one.
- On app open (hard paywall). No free tier at all. Aggressive, but the same RevenueCat report found apps that ask for money upfront convert about 5x better than freemium (10.7% vs 2.1% median). It fits apps whose value is obvious before use; it punishes apps that need sessions to prove themselves.
Most strong subscription apps combine the first two: an onboarding paywall for everyone, feature-gate paywalls for the users who dismissed it. If you are choosing between free trial, hard paywall, and freemium as a model, that decision comes first: see free trial, hard paywall, or freemium.
Match trial framing to your category
Whether your paywall should lead with "try free for 7 days" or with the price is not a matter of taste; it varies enormously by category. Directional estimates from a July 2026 snapshot of PaywallPro's Open Paywall Gallery, a public dataset of 910 top iOS subscription apps, put the share of trial-led paywalls at:
- Business: about 77% of paywalls lead with a trial.
- Education: about 73%. Utilities: about 71%. Productivity: about 66%.
- Health & fitness: about 52%. Split down the middle.
- Social networking: about 25%. Entertainment: about 24%. Content apps mostly sell access directly.
These are third-party estimates, not our measurements, but the spread is the point: copying a fitness app's trial framing into an entertainment app means adopting a convention its users never see elsewhere. Start from your category's norm, then test against it.
Respect the Day 0 effect
One more finding worth internalizing from the same RevenueCat report: 55% of all 3-day trial cancellations happen on Day 0, the day the trial starts. Users start a trial and immediately cancel to avoid forgetting. This is not a failure of your paywall; it is how a large share of users consume trials. It means your trial experience, not just your trial screen, does the converting: the first session after the paywall has to prove the subscription is worth keeping.
Test placement, not pixels
Because placement is the highest-leverage variable, it should be the first thing you A/B test: end-of-onboarding vs feature-gate, trial-led vs price-led framing, one screen earlier or later in the flow. These are structural tests, and running them through app releases is painful enough that most teams never do it. With Setgreet, paywall and upgrade screens are native flows you can move, reframe, and A/B test without shipping a build, at a flat MAU price that never takes a cut of your revenue.
The second-chance surfaces most apps forget
The onboarding paywall converts a minority of viewers even when it is working well, which means most of your users dismissed it. What they see next is a placement decision too, and it is usually left to chance. The strong patterns:
- Feature gates with specific offers. When a free user hits a locked capability, the paywall should name that capability, not restate the generic pitch they already declined.
- Progress-triggered offers. After a streak, a completed workout, a finished project: moments where the product just proved itself are second motivation peaks.
- Win-back placement. A returning user who lapsed for weeks is closer to a fresh install than to an active user; showing them the onboarding paywall again, sometimes with a discount, is fair game.
- The settings page. Boring, but users with purchase intent go looking for it. Make the upgrade entry point findable in two taps.
Each surface deserves its own framing, because the user's context differs at each one. The mistake is shipping one paywall screen and routing every trigger to it: the message that fits a motivated Day 0 user reads as noise to a Day 30 free user who has seen it five times.
Frequently asked questions
Should the paywall be skippable?
If you run a free tier, yes, with a visible but quiet close affordance. Hiding the close button buys a little conversion and costs trust and reviews. If you run a hard paywall, there is nothing to skip to; just be sure your category can carry it.
Is showing a paywall during onboarding too aggressive?
No. It is the norm among top subscription apps, and users expect it. What reads as aggressive is a paywall before any personalization or value framing, or one that reappears on every tap after being dismissed.
Where should the paywall go for a freemium app?
Still show it at the end of onboarding as a soft offer, then rely on feature-gate paywalls at the moments free users hit limits. The onboarding paywall sets the anchor that a paid tier exists; the gates convert when intent is proven.