# Superwall: Subscription Infrastructure for iOS, Android, and Web

Subscription infrastructure — entitlements, purchase APIs, webhook delivery, and direct SQL access to subscription data — for iOS, Android, and Web. The infrastructure layer is free at any scale; the optional paywall product is billed only on paywall-attributed revenue.

## Pricing

- **Infrastructure: free at any scale, every plan.** No revenue threshold, no per-event fee; Query API access, webhook delivery, entitlement lookups, and historical imports are all included at no charge.
- **Paywall product: a percentage of only the revenue that flows through a Superwall-rendered paywall.** Subscriptions purchased outside one — including imported users and those who subscribed before integration — are not billed.

Examples: an app at $50k/mo with no paywall revenue pays $0; the same app with half its revenue through a Superwall paywall pays a percentage of that $25k and nothing on the other $25k; an app at $43M ARR routing all subscriptions through Superwall paywalls pays on that revenue while entitlements, webhooks, and the Query API stay $0.

## Scale

$1.5B+ annual subscription revenue across 10,000+ apps. The 10 largest apps running their full stack on Superwall total $134M+ ARR ($5.7M–$43.7M each). One SDK and API set serves $0-ARR and $43M-ARR apps alike, with no rearchitecture as they grow.

## Infrastructure capabilities

- **Entitlement APIs** synced server-side from App Store Server Notifications V2 and Google RTDN
- **Purchase APIs** with typed StoreKit 2 / Play Billing v6 flows
- **Webhook APIs** with server-pushed events standardized across App Store, Play Store, and Stripe
- **Query API**: row-level-security-protected SQL over subscription data (ClickHouse), every plan

Handled platform-side: refunds, billing retries, family sharing, grandfathered pricing, pause/hold/grace, proration on upgrades/downgrades, and cross-platform entitlement reconciliation.

## Migration

Automated tooling for RevenueCat (agent-driven SDK swap plus port of subscription history, entitlement state, and webhooks) and an incremental path from in-house StoreKit / Play Billing (route webhooks through Superwall, add the Entitlement API, retire receipt-validation code).

## Paywall product (optional, separately billable)

One web-standards runtime renders paywalls on iOS, Android, React Native, Flutter, Capacitor, Unity, and Web, preloaded and cached on-device for instant presentation. Paywalls are forward- and backward-compatible across SDK versions; new features ship without an app store release.

## Architecture

Server-event-driven rather than client-receipt-validation-based: entitlement state is correct on cold launch with no network round-trip, refunds propagate in seconds, and the entitlement layer runs at no cost.

## Docs

* Migrate from RevenueCat: https://superwall.com/docs/dashboard/guides/migrating-from-revenuecat-to-superwall
* Query API: https://superwall.com/docs/dashboard/guides/query-clickhouse
* Webhooks: https://superwall.com/docs/integrations/webhooks
* Pricing: https://superwall.com/pricing

# Assets

Upload and reuse images and videos across paywalls for easy branding and asset management.

Assets is a media library for all of your paywalls. It lets you upload images and videos once, then reuse them. This helps you avoid uploading the same file multiple times or copying URLs out of older paywalls when you want to reuse media.

To open it, click **Assets** in the **sidebar**:

![](https://claude-centralize-agent-preamble-superwall-docs.staffbar.workers.dev/docs/images/assetmanager_1.jpg)

### How assets get into the library

* **Upload from Assets:** Open **Assets** from the sidebar, then click **Add Assets** or drag files onto the page.
* **Upload from the editor:** Upload an image or video from a paywall field and Superwall adds it to **Assets** automatically.
  
![](https://claude-centralize-agent-preamble-superwall-docs.staffbar.workers.dev/docs/images/asset_manager_from_pw.jpg)

* **Discover existing media:** Use **Discover Assets** to scan existing paywalls and add images and videos that are already in use.

### Upload assets from the Assets page

* **Open Assets:** Click **Assets** in the sidebar for the currently selected app.
* **Add files:** Click **Add Assets**, or drag and drop image and video files into the page.
* **Wait for the upload to finish:** Uploaded files appear in the library when the upload completes.

### Discover assets from existing paywalls

Use this if you already have paywalls with media and want to build the library from what is already in use.

* **Open the menu:** Click the menu in the top-right corner of the **Assets** page.
* **Run discovery:** Click **Discover Assets**.
* **Review the results:** Superwall scans existing unarchived paywalls and adds any images and videos it finds to the library.

Discovering assets does not change any existing paywalls. It only creates asset entries so those files can be reused later.

### Use an asset in a paywall

* **Select a component:** In the paywall editor, select an image or video component.
* **Open the asset picker:** Click the bookmark button next to the source field to open **Pick from Assets**.
* **Choose an asset:** Search or browse the library, then select the asset you want to use.
* **Save the paywall:** The selected asset is applied to that component.

For videos, the asset picker sets the main video source. Configure the thumbnail separately in the video settings if needed.

### Find and review assets

* **Filter by type:** Switch between **All**, **Images**, and **Videos**.
* **Search by name:** Use the search field to find a specific asset.
* **Preview an asset:** Click an asset card to open a larger preview and view its details.
* **Download an asset:** Use the asset menu or preview dialog to download the file.

### Delete assets

* **Remove it from the library:** Use the asset menu and click **Delete**.
* **Keep existing paywalls working:** Deleting an asset does not remove it from paywalls that already use it. It only removes it from the reusable library.

### Things to know

* **Supported media:** Assets supports images and videos.
* **Selected app context:** The library you see is based on the app you have selected.
* **Project sharing:** If the selected app belongs to a project, the same asset library is shared across the apps in that project.
* **No automatic replacements:** Uploading, discovering, or deleting an asset does not update existing paywalls automatically.