Skip to content
AppDues
Log in
Contact salesSign up

Web Paywalls: Reusing Mobile Designs in the Browser

A paywall does not have to be rebuilt for the browser. Paywalls can now appear on the web through Web Purchase Links and Purchases.js, using the layouts and components already designed for iOS and Android. That means one place to design, test, and update subscription flows across platforms.

One paywall across mobile and web

A web paywall is not a separate object or a new paywall type. It is the browser version of the paywall you already create at the Offering level.

An Offering can contain mobile products, web products, or both. When it contains both, the same paywall layout serves mobile and web users. Structure, copy, and experiments carry over, so you design once and reuse across platforms.

This matters for teams that want a consistent subscription experience without maintaining two design systems. The paywall you tune for mobile is the same one your web visitors see.

Where web paywalls show up

There are two places a web paywall can appear, depending on how your product is set up.

Inside Web Purchase Links. Web Purchase Links are checkout URLs hosted by the platform. If a link uses the default package selection page, you can replace that step with your paywall. Visitors then meet your messaging, layout, and pricing context before checkout starts, which moves your control earlier in the flow.

Embedded in your web app with Purchases.js. Teams already using Purchases.js gain an in-app rendering path for paywalls. The call is presentPaywall; you supply the HTML element that marks the insertion point, and the remaining rendering and checkout handoff are handled for you. Because the paywall mounts where you point it and flows straight into checkout, there is no need to assemble a bespoke UI or a custom purchase flow.

Use this checklist to choose the right surface:

  • Hosted checkout URL needed? Use a Web Purchase Link and replace the default package selection page.
  • Paywall inside your own web app? Use Purchases.js and call presentPaywall with a target HTML element.
  • Need both? The same paywall layout can serve both surfaces.

Works with Web Billing and Paddle

Web paywalls support both Web Billing and Paddle.

The product list is decided by the web config bound to whichever surface is displaying the paywall. Point a Web Purchase Link at a Paddle config and Paddle products are offered; repoint that same link to a Web Billing config and the catalog switches to Web Billing products. Configuration moves the product source, while the paywall layout holds steady.

That distinction helps when troubleshooting. If the layout looks right but the products are wrong, inspect the web config attached to the surface before touching the paywall design. The paywall is not what determines the product list.

A quick example: a link showing Paddle products is switched to a Web Billing config. The layout, copy, and pricing blocks stay as designed, while the products on offer now come from Web Billing.

Change paywalls without shipping updates

Web paywalls are hosted and server driven. You can update copy, layouts, pricing blocks, and calls to action from the dashboard. When you publish, changes go live immediately.

You can also target paywalls by country, platform, app version, or custom segments. Experiments work the same way they do on mobile, so you can test pricing, layout, or messaging on the web with the same tools. When something stops converting, you can respond the same day.

A practical example: if a pricing block underperforms on web, adjust it in the dashboard and publish. There is no app release cycle to wait for, and the change applies to the web surface immediately.

Run subscriptions from one place

Web paywalls reach readers two ways: mounted inside your own app, or reached through hosted URLs. Whichever route you pick, mobile and web subscription flows are administered together in one system, drawing on the same paywalls and the same workflows.

Paywalls on the web are available now. For setup details, see the web paywalls documentation.

Frequently asked questions

Is a web paywall a separate object from my mobile paywall?

No. A web paywall is the browser version of the paywall you already create at the Offering level. It is not a separate object or a new paywall type. If an Offering includes both mobile and web products, the same paywall layout serves both.

Where can web paywalls appear?

In two places: inside Web Purchase Links, where you can replace the default package selection page with your paywall, or embedded in your web app with Purchases.js by calling presentPaywall and passing the HTML element where it should render.

Why do different products appear on the same paywall?

The products shown depend on the web config attached to the surface displaying the paywall. A Web Purchase Link connected to a Paddle config shows Paddle products; switch that link to a Web Billing config and it shows Web Billing products. The layout stays consistent while the product source changes.

Can I update web paywalls without shipping an app update?

Yes. Web paywalls are hosted and server driven. You can update copy, layouts, pricing blocks, and calls to action from the dashboard, and changes go live immediately when you publish. You can also target paywalls by country, platform, app version, or custom segments, and run experiments the same way you do on mobile.