Superwall review (2026): the paywall tool that only bills on paywall revenue

Superwall splits its product into two layers and bills them differently. The subscription infrastructure — the purchase SDK, entitlements, charts, webhooks and raw data access — is, in Superwall's words, "Free on every plan including the free tier. No tracked-revenue threshold, no per-event fee, no charge for raw data access." The paywall layer is what you pay for.

Two consequences that matter when you move an existing app over. Superwall's pricing page says "Subscriptions purchased outside Superwall are free" and "Imported & pre-integration users are never billed." So your existing subscribers don't start costing you anything on day one — only new revenue through Superwall paywalls does.

Two things stand out. The Indie bill jumps from $0 to about $100 the month you cross $10k, rather than growing smoothly. And the paid tiers are never cheaper than Indie: they add a fixed fee on top of the same 1%. Upgrade when you need surveys, multiple collaborators or localization in the paywall editor — not to cut costs. For the same revenue levels on RevenueCat, see our RevenueCat vs Superwall fee comparison.

• Campaigns. Superwall's docs describe campaigns as three concepts: placements (moments in your app), audiences (who), and paywalls (what) — including "no paywall (a.k.a. a holdout)" as a control group.
• A paywall editor. Build from scratch or start from a template; there's also an AI chat builder. Superwall says paywalls render from a single web-standards-based runtime and "are preloaded on-device and cached locally".
• No app update to change a paywall. Its pricing page states: "New paywall features ship without an app store release."
• Purchases and entitlements without another SDK. Since its next-generation SDKs in February 2025 (iOS SDK v4), Superwall handles purchasing with full StoreKit 2 support and cross-platform entitlements.
• Works with RevenueCat. Superwall's recommended setup is to put RevenueCat in observer mode, so you keep your existing purchase stack.
• Web checkout. Stripe-powered web checkout, and an App2Web flow that opens Stripe checkout in Safari for customers on the US App Store storefront.
• Your data, queryable. A SQL query API over your subscription data, "included on every plan".

Superwall reports "10,000+ Apps on Superwall" and "$1.5B+ ARR tracked" on its pricing page. Those are its own figures. The company was founded in 2021, went through Y Combinator's Summer 2021 batch, and announced $7.5 million raised to date in July 2026.

1. 01

   Create products in App Store Connect

   Subscriptions in one group, with prices, and the Paid Apps agreement active.

2. 02

   Add the SDK

   Install SuperwallKit with Swift Package Manager and configure it once at launch with your public API key.

3. 03

   Register placements where paid features start

   Wrap each gated action in a placement. The dashboard then decides whether a paywall shows there, for whom.

4. 04

   Build the paywall and a campaign

   Pick a template, set your products, and attach it to the placement in a campaign — with a holdout if you want a control group.

5. 05

   Test the whole path in sandbox

   Fresh install, purchase, restore and cancel, including with the device offline.

import SuperwallKit

// At launch
Superwall.configure(apiKey: "pk_your_public_key")

// Where a paid feature starts. The dashboard decides if a paywall shows;
// the closure runs if the user has access or purchases.
func pressedWorkoutButton() {
    Superwall.shared.register(placement: "StartWorkout") {
        navigation.startWorkout()
    }
}

Whatever renders it, the paywall still has to meet App Review's subscription rules — the billed price shown most prominently, plan length, and Terms of Use and privacy links. Our Guideline 3.1.2 page lists them.

• SDK size. Superwall says the iOS SDK adds "approximately 7.7 MB" to your install size.
• Offline first launch. Superwall's changelog notes that if the device is offline, the paywall configuration hasn't been fetched yet and the user isn't subscribed, presenting a paywall throws a presentation error. Handle that case — and if you use local image or video assets, they need iOS SDK v4.13.0 or later.
• Open SDK issues. At the time of writing, Superwall's iOS repository had open reports of paywall preloading hanging the main thread on iOS 26, delayed or unexpectedly dismissed paywalls on SDK 4.16.1, and failed analytics events not being retried — which matters, because attribution is what you're billed on. Check the issue tracker against your SDK version.
• Offers can cross App Review's line. Superwall's own compliance FAQ warns that "showing the same 'one-time offer' repeatedly to users who declined it previously could result in App Store rejection or removal."
• Web checkout is US-only in the app. App2Web applies to the US storefront, and Superwall's docs say not to open Stripe checkout in an in-app browser or web view. Elsewhere, in-app purchase rules apply — see Guideline 3.1.1.