Paywall placement: when and where to show it in your app
Where the paywall appears often matters more than how it looks. A good screen at the wrong moment converts poorly and annoys people; an average screen at the right moment can do well. The right placement depends on how quickly your app delivers value and what you are selling. For the screen itself, see paywall design.
The common placements
1. Hard paywall at launch. The user must pay (or start a trial) before using the app. It works when the value is obvious from the store page and the audience already wants it, such as a well-known utility. It loses people who wanted to look first, and it makes your first-day numbers hard to read. It is also the placement most likely to produce angry reviews if the store page did not make clear that payment is required.
2. Paywall at the end of onboarding. After a short flow that explains the benefits and perhaps collects a goal, the user sees the offer. It is popular for habit, fitness and learning apps because the setup makes the promise personal ("Your plan to learn Spanish in 6 months"). Keep the flow short and honest, and let people skip if your model includes a free tier.
3. Soft paywall with a free tier. The app is usable for free and some features are locked. The paywall appears when the user taps a locked feature. This is the friendliest option and fits many tools. The risk is that the free tier is so good that nobody upgrades, or so poor that nobody stays.
4. Usage limit. A free quota (five exports, three projects, ten messages) and the paywall when it runs out. People have felt the value before being asked to pay. Make the limit visible before it hits, so it never feels like a trap.
5. After a result. The user completes something and sees a result, then the offer to unlock more or remove limits. A good moment because value just arrived.
6. Passive entry points. A settings entry, a banner on a locked screen, a small "Upgrade" label. They rarely convert alone but they catch people who decide on their own time.
How to choose
Ask two questions:
- How fast can a new user feel the value? If it takes a minute, you can show the paywall after the first result. If it takes days (a habit app), the paywall may need to come earlier in the form of a trial, or you need a strong onboarding to set expectations.
- How much does your app cost you per free user? Server costs, content licences or AI calls may force a limit. If it costs almost nothing, a generous free tier builds goodwill and reviews.
Most apps end up with a mix: a feature gate or usage limit as the main trigger, a paywall after onboarding for people who are ready, and a permanent entry in settings.
Rules of thumb
- Never show a paywall in the first seconds of the very first launch unless it is a deliberate hard-paywall model.
- Never interrupt a task in progress to sell something.
- Let people dismiss it, and do not show it again immediately.
- Do not stack paywall, rating prompt and notification permission on the same screen. See when to ask for app reviews.
- Make sure the store listing sets the right expectation. A free-looking app that blocks everything at launch invites one-star reviews.
Measure it
Track the share of users who reach the paywall, the share who start a trial or buy, and, importantly, retention and refunds by placement. A placement that converts well but increases day-7 churn or refund requests is not a win. Test one placement change at a time; see how to test a paywall.
Checklist
- Decide how quickly users feel value.
- Choose one primary trigger (gate, limit, after onboarding).
- Add a permanent entry in settings.
- Never interrupt tasks.
- Make sure the store listing matches the model.
- Measure conversion, retention and refunds per placement.
Need testers for your app? Open a test group on AppReviewX. Start free