Content
Try for free

Hard Paywall vs Soft Paywall: Which Converts Better?

A hard paywall blocks the product until the user starts a trial or pays. A soft paywall can be dismissed, and the user keeps a limited version of the app. Neither converts better in every case. A hard paywall usually gives you a higher share of paying users among the people who see it, but fewer people get past it. A soft paywall keeps more users in the product and converts some of them later.

A working rule for subscription apps: if the value is clear before the user touches the product (a quiz result, a personalized plan) and you pay for traffic, start with a hard paywall and test a soft variant against it. If value only shows up after some use, or your growth is mostly organic and habit-driven, start with a soft or contextual paywall. The rest of this article covers definitions, a side-by-side comparison, how to measure paywall conversion, timing, freemium, and how to test.

What are hard, soft, contextual and metered paywalls?

Hard paywall. The user cannot use the core product without a trial or a payment. There is no close button that leads to a free version. Some apps allow a free trial behind the hard paywall, which is still a hard paywall because a payment method is required to continue.

Soft paywall. The paywall has a close or skip option. The user lands in a limited version of the app and may see the paywall again later. Soft paywalls are common in apps that also run ads or have a free tier.

Contextual paywall. The paywall appears when the user tries something that is part of the paid plan: exporting a result, opening a locked lesson, starting a second AI conversation. It is a soft paywall tied to a specific action, so the offer explains exactly what the user gets by paying.

Metered paywall. The user gets a fixed amount of free usage, such as a number of sessions or generations, and the paywall appears when it runs out.

These types are not exclusive. Many apps run a hard paywall at the end of onboarding and contextual paywalls inside the app for users who skipped or churned.

Hard paywall vs soft paywall: side-by-side comparison

The factors below are the ones that usually decide the choice. The statements describe tendencies, not fixed outcomes; your own data should overrule them.

Access before payment

  • Hard paywall: none, or a trial that requires a payment method
  • Soft paywall: limited free version
  • Contextual paywall: free until the user reaches a paid feature
  • Freemium: permanent free tier with feature limits

Share of users who see a payment screen and pay

  • Hard paywall: usually higher, because paying is the only way forward
  • Soft paywall: usually lower at first view, with a second chance later
  • Contextual paywall: depends on how close the trigger is to a moment of need
  • Freemium: lowest at first view, spread over a longer period

Number of users who reach the product

  • Hard paywall: smaller, since some users leave at the paywall
  • Soft paywall: larger
  • Contextual paywall: larger
  • Freemium: largest

Refund and churn risk

  • Hard paywall: higher if the paywall promises more than the product delivers
  • Soft paywall: lower, because users who pay have usually tried the product
  • Contextual paywall: lower for the same reason
  • Freemium: depends on whether the free tier is enough for the user

Cost to run

  • Hard paywall: one screen and one flow to build and test
  • Soft paywall: same screen plus the limited-access logic in the app
  • Contextual paywall: triggers in the app code for each paid feature
  • Freemium: feature gating across the product, plus support for free users

Which paywall converts better?

The honest answer is that it depends on what you count. A hard paywall tends to win on conversion from paywall view to paid. A soft paywall can win on total revenue per visitor if the users it keeps convert later, or if the extra product exposure reduces refunds and early churn. Published benchmarks vary by category and traffic source, so use your own numbers.

To compare paywall conversion fairly, measure every variant on the same base: all users who entered the funnel or installed the app, not only those who saw the paywall. Compute these from your own data:

  • Paywall view to trial or purchase: trials started or purchases divided by paywall views.
  • Entry to paid: paying users divided by everyone who started the funnel or installed.
  • Revenue per entering user: total revenue in the cohort divided by the number of users who entered.
  • Paid retention: the share of payers still active after the first renewals.
  • Refund rate: refunded revenue divided by total revenue in the cohort.

Revenue per entering user is the number to decide on, because it includes both the users you lose at the paywall and the revenue you earn from those who stay. A variant with a lower view-to-purchase rate can still win on this metric. Check the paid retention and refund rate before declaring a winner, since a hard paywall that converts more users into short-lived subscribers can look better in week one and worse after the first renewals.

When should the paywall appear? Smart paywall timing

Timing matters as much as paywall type. The question is not how early you can show a paywall, but when the user has seen enough value to pay for the rest.

After onboarding, before the product. Works when onboarding itself produces something valuable: a plan, a score, a recommendation. The user has answered questions and wants to see the result. This is the usual position for a hard paywall.

After a first result. Works for apps where the first use is quick, such as a translated phrase, a first workout or one AI answer. Show the paywall after the user has seen what the product does.

At the limit. Metered and contextual paywalls fit here. The user runs out of free sessions or taps a locked feature, and the paywall appears at the moment of need.

On return. Users who dismissed a soft paywall can see it again on the second or third session, when they have more reasons to pay. Cap the frequency, and check whether repeat prompts lead to more purchases or more uninstalls.

A smart paywall is one where timing and content follow the user's behavior. A simple version: pick two or three trigger points, send each user to the right one based on what they did, and test the order. You do not need machine learning to start; you need event data on what users did before they saw the paywall. Your analytics setup should record paywall views, dismissals and the event that triggered each view.

Freemium vs hard paywall: how to choose

Freemium makes sense when the product has real value at zero cost to you, and when free users bring something back: content, referrals, data, or a larger pool of future payers. It fits apps with low serving costs and a clear line between basic and advanced features.

A hard paywall fits when each user costs you something (AI inference, paid acquisition, human support) and when the product result is the same for everyone who pays. If you buy installs, a free user who never pays is a cost, and the hard paywall pushes the decision to the start.

Questions that help:

  1. What does one free user cost per month in infrastructure and support?
  2. Do free users bring in other users, or only use the product?
  3. What share of free users convert within 30 or 60 days, and is that enough to cover acquisition cost?
  4. Can you define a free tier that is useful but still leaves a reason to upgrade?

If you cannot answer the third question yet, a soft paywall is a safer first step than a full freemium tier. It gives you data on how many users want to pay without building a free product around the answer.

Paywalls in web2app funnels

In a web2app funnel the paywall sits on the web, before the install. The usual sequence is ad, landing page or quiz, personalized plan, paywall, payment, then app download and login. That position changes the hard vs soft question. The user has already answered the quiz and seen a plan, so a hard paywall is the natural default, and the soft options become exit paths: a lower-priced plan, a shorter trial, or a free-tier install for users who decline.

The store side matters here. Apple charges up to 30% commission on in-app purchases (15% under the Small Business Program), and web2app funnels sell subscriptions on the web, outside the app store, where that is allowed. Rules differ by region, change over time, and depend on the app category and how you link the web purchase to the app. Check the current App Store Review Guidelines and Google Play policy for your markets, and read our web2app funnel compliance guide before you change how users pay. Nothing here is legal advice, and a policy that applies today may not apply next quarter.

web2wave is one option for building this layer: a no-code builder for web2app funnels with quiz flows, a paywall builder, payments through Stripe and other providers, and integrations with subscription tools such as RevenueCat, Adapty, Qonversion, Superwall and Apphud. Over 3,000 active web funnels run on it. If you already have a paywall in the app, you can keep it for contextual prompts and use the web funnel for the first purchase.

How to test hard vs soft paywalls

Test one change at a time and keep the audience split random. A clean order of experiments:

  1. Paywall type. Hard against hard with a close button that leads to a limited version. Measure revenue per entering user, not only purchases.
  2. Timing. Same paywall shown at two points: right after onboarding versus after the first result.
  3. Offer. Trial length, plan order and price display, once you know which paywall type and timing work.
  4. Exit path. What happens when a user declines: nothing, a discount, a free tier, or an email sequence.

Decide the sample size and the stopping rule before the test starts, run it across at least one full billing cycle where renewals matter, and compare cohorts by traffic source, since users from different ad channels behave differently. Paywall tests also depend on clean attribution, so pass campaign and creative data into the funnel. For test design, our guide to A/B testing covers the setup in more detail. In web2wave you can run A/B experiments on funnel and paywall variants and read the results next to your attribution data, but the same method works in any tool that splits traffic and records revenue by cohort.

Keep a log of each test: the hypothesis, the variants, the audience, the dates and the result. After a few tests you will see whether your users respond more to paywall type, timing or offer, and that tells you where to spend the next test.

FAQ

Is a hard paywall better than a soft paywall?

Not in every case. A hard paywall usually converts a higher share of the users who see it, while a soft paywall keeps more users in the product and may earn revenue later. Compare revenue per entering user, paid retention and refund rate for each variant before deciding.

What is a contextual paywall?

A contextual paywall appears when the user tries a paid feature or reaches a usage limit, instead of at a fixed point such as app launch. The message can name the exact feature the user wanted, which makes the offer more specific than a generic upgrade screen.

When is the best time to show a paywall?

When the user has seen enough value to judge the product. That is often right after onboarding if onboarding produces a result, after the first successful use in apps with fast results, or at a usage limit in metered products. Test two or three points and compare revenue per entering user.

Should I choose freemium or a hard paywall?

Choose freemium if free users cost little to serve and bring referrals or content. Choose a hard paywall if each user has a real cost, such as paid acquisition or AI usage, and the product delivers value quickly. If you are unsure, test a soft paywall first.

Can I sell subscriptions outside the app store?

It depends on the store, the region, the app category and how the purchase is linked to the app. Rules change, so check the current App Store Review Guidelines and Google Play policy, and read the compliance guide before you launch a web payment flow.

If you want to build and test paywalls in a web2app funnel, you can book a demo or start free.

Share this Article

Build your web funnel with web2wave

Start using web funnels: Launch faster, convert better, and keep more revenue with no app store limitations