What is Capacitor? How it turns a web app into an iOS and Android app, and when not to use it

    Capacitor is the open-source tool most often suggested for putting a web app into the App Store and Google Play. It wraps your web app in real iOS and Android projects and gives it access to the phone through plugins. This guide explains how it works, what you need to run it, and when a native app is the better route.

    The short answer. Capacitor is an open-source “cross-platform native runtime for web apps,” made by Ionic and “Released under MIT License.” You add it to an existing web project, and it creates an Xcode project for iPhone and an Android Studio project for Android. Inside each, your web app runs in the phone’s WebView, and Capacitor plugins let your JavaScript use the camera, push notifications, location and other native features. It is free. You need a Mac with Xcode 26 for the iPhone build, and you submit the apps to the stores yourself.

    What Capacitor does

    Capacitor’s docs: “Capacitor is a cross-platform native runtime that makes it easy to build performant mobile applications that run natively on iOS, Android, and more using modern web tooling.” Ionic’s own explanation is shorter: “Capacitor takes your existing web application and runs it as a native app on each platform.”

    In practice, three parts make up a Capacitor app:

    A native project per platform. A real Xcode project and a real Android Studio project live in your repository, in folders called ios and android. You can open, edit and build them like any native app.

    A WebView that loads your web app. On iPhone, “Capacitor uses WKWebView, not the deprecated UIWebView.” Your HTML, CSS and JavaScript are bundled into the app and shown full screen.

    Plugins that connect the two. “Plugins in Capacitor enable JavaScript to interface directly with Native APIs.” Your code calls a JavaScript function, and the plugin runs the Swift or Kotlin code on the device.

    How a Capacitor app is put together. Our diagram.

    Who makes Capacitor

    Capacitor is built by Ionic, the company behind the Ionic Framework. OutSystems announced on 7 November 2022 that it “has acquired Ionic”. The code is on GitHub under the MIT licence.

    Capacitor 8 was announced on 8 December 2025. The current release on 29 October 2026 is 8.6.0 (28 October 2026), and a Capacitor 9 beta came out the same day.

    When Ionic stopped selling its commercial products in February 2025, it wrote: “Ionic's open source software, including Ionic Framework and Capacitor, will remain free and open source.”

    What you need to use Capacitor

    From Capacitor’s environment setup page, for Capacitor 8:

    Node.js 22 or later. “you will need NodeJS 22 or higher installed.”

    A Mac and Xcode 26 for iPhone. “To build iOS apps, you will need macOS.” and “Capacitor 8 requires a minimum of Xcode 26.0.” Apps run on iOS 15 and later. Swift Package Manager is now the default for iOS dependencies; CocoaPods was the default in Capacitor 7 and earlier.

    Android Studio for Android. “Capacitor 8 requires a minimum of Android Studio 2025.2.1,” with the Android SDK for API 24 or later.

    A web app that builds to static files. Capacitor copies your built web bundle from a folder you name (webDir, for example dist) into the native projects.

    Store accounts. An Apple Developer account (99 USD a year) and a Google Play account (US$25 once). Capacitor builds the apps; it does not submit them.

    How to add Capacitor to a web app

    The commands below are from Capacitor’s getting started docs. Run them in your web project’s folder.

    1. Install Capacitor. npm i @capacitor/core and npm i -D @capacitor/cli.

    2. Initialise it. npx cap init asks for the app name and the app ID (for example com.yourcompany.yourapp), which becomes the bundle ID in the stores.

    3. Add the platforms. npm i @capacitor/android @capacitor/ios, then npx cap add android and npx cap add ios.

    4. Build the web app and sync. Build your web app as usual, then run npx cap sync, which “will copy your built web bundle expected to be found in `webDir`” into both native projects and installs plugin code. Run it again after every web build.

    5. Open and run the native projects. npx cap open ios opens Xcode; npx cap open android opens Android Studio. npx cap run ios runs the app on a simulator or device.

    6. Add plugins. Install the ones you need (for example @capacitor/camera or @capacitor/push-notifications), call them from your JavaScript, and add the permission texts each plugin’s page lists to the native projects.

    7. Build and submit. Archive the iPhone app in Xcode and upload it to App Store Connect; build an Android App Bundle in Android Studio and upload it to Google Play Console. How to publish an app on the App Store covers the Apple side.

    If your web app was built with Lovable or Base44, export it to GitHub first and run these steps on the exported code.

    Capacitor plugins

    Official plugins are “maintained by the Capacitor Team.” The list in the docs includes Camera, Geolocation, Push Notifications, Local Notifications, Haptics, Filesystem, Preferences, Share, Splash Screen, Status Bar, Barcode Scanner, Google Maps, Keyboard, Network and an in-app browser.

    Community plugins are “maintained by the Capacitor Community”, a GitHub organisation (capacitor-community) with plugins for features the official set does not cover. For anything else, you can write your own plugin in Swift and Kotlin.

    Push notifications need setup outside your code. From the plugin’s docs: “On iOS you must enable the Push Notifications capability,” and on Android you create a Firebase project and add its google-services.json file to the app.

    Updates after the app is in the stores

    Every change to the web code needs a new web build, npx cap sync, and a new store release, unless you add a live update service that downloads new web bundles to installed apps.

    Ionic’s own service for this was Appflow. On 11 February 2025, Ionic wrote: “Today, we have discontinued new customer sales for all Ionic commercial products and services,” and told existing customers “You'll continue to have access through December 31, 2027.”

    The best-known third-party option is Capgo, which describes itself as an “AI-ready platform to build, ship, and live-update Capacitor apps.” Read Apple’s and Google’s rules on downloaded code before you rely on one.

    Capacitor vs Cordova

    Cordova is the older tool for the same job. Capacitor’s docs: “In spirit, Capacitor and Cordova are very similar.” and “Both manage a Web View and provide a structured way of exposing native functionality to your web code.” Ionic says Capacitor “was built initially to replace Cordova.”

    The main practical difference is the native projects. Capacitor “considers each platform project a source asset instead of a build time asset”: you check the Xcode and Android Studio projects into source control and edit them directly. It also “does not use a global CLI.” Moving over can be gradual; the migration guide says “you don't technically have to remove Cordova, since Capacitor works alongside it.”

    Capacitor vs React Native

    Both let a JavaScript team ship iOS and Android apps, but they draw the screen differently. Ionic’s comparison: “React Native provides an abstraction through React that controls platform UI controls directly,” while a web-based app “will simply perform more work in a native WebView control.”

    In other words, a React Native app’s buttons and lists are native views driven by JavaScript; a Capacitor app’s buttons and lists are web elements inside a WebView. Ionic argues that “Capacitor is also far less complex than React Native,” and says React Native “may be a better fit” for teams with native experience that only target iOS and Android.

    The practical difference is where you start. With a working web app, Capacitor reuses it. React Native means rewriting the interface in React Native components.

    When not to use Capacitor

    Capacitor is a good fit when the web app already works well on a phone, the team knows web development, and the phone app mainly adds a store listing, push notifications and a few device features.

    It is a poor fit when one of these is true:

    The app is the product. Users open it every day, and scrolling, gestures and speed decide whether they stay. A WebView interface behaves like a website, not like the other apps on the phone.

    You need features that live outside the WebView. Home Screen widgets, Live Activities, Apple Watch, long background work, or offline use with a local database. Each needs its own native code next to the web app.

    Apple might see it as a website. Guideline 4.2: “Your app should include features, content, and UI that elevate it beyond a repackaged website.” A Capacitor app that only loads your site is the case that rule describes.

    Nobody on the team can maintain native projects. Capacitor saves writing the interface twice, but the Xcode and Android Studio projects, signing, plugin updates and store releases still need someone.

    The alternative is a native app: Swift and SwiftUI for iPhone, Kotlin and Jetpack Compose for Android. Modaal builds both from one project: you describe the app, using your web app as the reference, Modaal turns it into a spec per feature, and your own AI agent writes the code on your Mac. Your backend stays where it is. The Free plan covers one project on one platform; Pro (€9 per user per month billed annually) adds both platforms, TestFlight and automated App Store publishing.

    Left: a web screen in a Capacitor app. Right: the same screen in SwiftUI. Our capture.

    Capacitor next to the other routes

    CapacitorConverter service (Median, Despia)React NativeNative (Swift + Kotlin)
    What draws the screensYour web app in a WebViewYour live website in a WebViewNative views driven by JavaScriptSwiftUI and Jetpack Compose
    Reuses your web appYes, the codeYes, the live siteLogic only; the interface is rewrittenAs the reference; rewritten
    Who sets it upYou or a developerThe vendor’s tool or teamYou or a developerYou, a developer or a tool such as Modaal
    Cost of the toolFree (MIT)The vendor’s planFree (MIT)Free (Xcode, Android Studio) plus the tool or developer
    Mac needed for iPhoneYesNo, the vendor builds itYes, or a cloud build serviceYes

    Capacitor facts from capacitorjs.com and Ionic, read 29 October 2026. Store fees (Apple 99 USD a year, Google Play US$25 once) apply to every route.

    Frequently asked questions

    Keep reading

    Native iPhone and Android apps. Start free.

    One project, two native apps: Swift for iPhone, Kotlin for Android.