Softwr

Mobile Development · head to head

Capacitor vs Preact

Capacitor logo

Capacitor

Mobile Development

MIT-licensed native runtime bridging web apps to iOS, Android and native APIs

From
Free
Free plan
Yes
Preact logo

Preact

Web Development

3kB alternative to React with the same modern API

From
Free
Free plan
Yes

The short version

  • Both are free.
  • Only Capacitor lists native project generation; only Preact lists 3kB runtime.
  • Where Preact falls short: compatibility through preact/compat is good but not total, and some React libraries break in ways that are hard to diagnose.
  • Prices and features on this page were last checked on 20 November 2026.

How do Capacitor and Preact differ?

Capacitor and Preact differ on platforms (Web, iOS, Android against Web) and category (Mobile Development against Web Development). Only the attributes on which Capacitor and Preact actually diverge.

Attributes where Capacitor and Preact differ
AttributeCapacitorPreact
PlatformsWeb, iOS, AndroidWeb
CategoryMobile DevelopmentWeb Development

Identical on both: starting price (Free), pricing model (Open source, no licence fee), free tier (Yes).

Which features does each one have?

They share no listed features; 6 appear only for Capacitor and 4 only for Preact. Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Capacitor

  • Native project generation
  • Plugin bridge
  • Custom native plugins
  • Live Reload
  • Framework agnostic
  • Capacitor Assets and Configure CLIs

Only in Preact

  • 3kB runtime
  • preact/compat
  • Same modern API
  • Fast rendering

What is each one used for?

Preact is most often brought in for embedded widgets that load inside someone else’s page and must stay small. The jobs each tool is most often brought in to do.

Capacitor

  • A team wrapping an existing responsive web app to publish it to the App Store and Play Storenot Preact
  • A product using React or Vue that wants native device APIs without adopting a full mobile frameworknot Preact
  • A developer who wants to drop into native Swift or Kotlin code for the parts a plugin does not covernot Preact
  • A company migrating off Apache Cordova, since Capacitor was designed as a modern, actively maintained successornot Preact

Preact

  • Embedded widgets that load inside someone else’s page and must stay smallnot Capacitor
  • Marketing and content sites where JavaScript payload affects Core Web Vitalsnot Capacitor
  • Applications targeting low-bandwidth or low-powered devicesnot Capacitor

Where do Capacitor and Preact fall short?

Preact's most cited limit: behavioural differences from React exist in edge cases, particularly around event handling. Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Capacitor

  • UI still renders in a system WebView, so complex animation and heavy graphics work require more manual tuning than a natively-rendered framework provides by default
  • Every native capability not covered by an official or community plugin means writing and maintaining native Swift and Kotlin code, which erodes the single-codebase promise for device-heavy apps
  • It is maintained by the same team as Ionic, and while it does not require the Ionic UI library, its release cadence and roadmap priorities are set by a company now owned by OutSystems
  • Cordova plugins are not automatically compatible and often need adaptation, so migrating a legacy Cordova app is a real porting project, not a drop-in swap
  • App store review teams scrutinise WebView-wrapped apps more closely for "just a website" rejections, so thin wrapper apps carry more approval risk than natively-compiled alternatives

Preact

  • Compatibility through preact/compat is good but not total, and some React libraries break in ways that are hard to diagnose
  • Behavioural differences from React exist in edge cases, particularly around event handling
  • A much smaller community, so unusual problems have fewer existing answers than React

How much do Capacitor and Preact cost?

Capacitor is free to use; Preact is free to use. Plan by plan below, from each vendor's own pricing page.

Capacitor

Free
  • CapacitorFree
    • MIT licensed, unlimited apps
    • Core plugin set included
    • Community support via GitHub and Discord

Preact

Free
  • PreactFree
    • Full library
    • Commercial use permitted
    • No usage limits

Which should you pick?

Choose Capacitor if

  • You need native project generation.
  • You want to start without paying.
  • You work on Web, iOS, Android.
  • You also want plugin bridge.

Choose Preact if

  • You need 3kb runtime.
  • You want to start without paying.
  • You also want preact/compat.

Questions people ask

Is Capacitor or Preact better?
Neither clearly leads. Capacitor starts at Free and Preact at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Capacitor or Preact?
Capacitor starts at Free and Preact at Free.
Does Capacitor or Preact run on more platforms?
Capacitor runs on Web, iOS, Android. Preact runs on Web.
Can I use Capacitor for free?
Both have a free tier, so you can try either at no cost before committing.
What is Capacitor best used for?
Capacitor is most often used for a team wrapping an existing responsive web app to publish it to the app store and play store, a product using react or vue that wants native device apis without adopting a full mobile framework, a developer who wants to drop into native swift or kotlin code for the parts a plugin does not cover, a company migrating off apache cordova, since capacitor was designed as a modern, actively maintained successor. Of those, a team wrapping an existing responsive web app to publish it to the app store and play store and a product using react or vue that wants native device apis without adopting a full mobile framework are not what Preact is typically brought in for.
What can Capacitor do that Preact cannot?
Capacitor covers Native project generation, Plugin bridge, Custom native plugins, Live Reload. Preact covers 3kB runtime, preact/compat, Same modern API, Fast rendering.

Answered from the vendors’ own pages

Capacitor: Do I need Ionic components to use Capacitor?

No. Capacitor is the native runtime and plugin bridge; the Ionic UI component library is a separate, optional layer.

Preact: Is Preact free?

Yes, open source under the MIT licence.

Capacitor: Is Capacitor free for commercial apps?

Yes, it is MIT licensed with no fee for commercial use, and there is no paid tier of Capacitor itself.

Preact: Can I use React libraries with Preact?

Most, through the preact/compat layer. Compatibility is good but not complete, so libraries relying on React internals can break.

Capacitor: Is it a replacement for Cordova?

Functionally yes for most teams, though existing Cordova plugins need adaptation rather than working unmodified.

Preact: Why choose Preact over React?

Bundle size, almost always. If payload is not a binding constraint, React’s ecosystem is usually the better trade.

Share

Related pages

Other head to heads