Comparison
Plasmo vs ExtensionStart: a framework and a kit
These are different layers, not rivals. Plasmo is a free, open-source extension framework, an alternative to WXT. ExtensionStart is a paid starter kit built on WXT. If you're searching 'plasmo vs wxt', you're making a framework choice; this page covers both that choice and where a kit fits above it.
Facts about other products on this page were last verified in July 2026. If something is out of date, email us and we'll fix it.
Plasmo, as of July 2026
Plasmo earned its ~13,000 GitHub stars: it brought a genuinely React-first developer experience to extensions, and Itero, its hosted preview and beta-testing platform, remains something no other extension framework offers. Credit where due.
The maintenance picture is the part to weigh. Per the GitHub repository, Plasmo's last stable release (v0.90.5) was published on May 17, 2025, more than a year before this page's verification date, though the repository still receives occasional commits. WXT's comparison page puts it more bluntly: Plasmo "appears to be in maintenance mode with little to no maintainers nor feature development happening." We'd state it more neutrally: the project is alive but its release cadence has slowed substantially, and browser extension platforms don't hold still; Chrome's manifest and store requirements change yearly. If you accept that risk for Plasmo's DX and Itero, that's a legitimate choice; for a commercial product we didn't, which is why ExtensionStart is built on WXT (active releases as of July 2026).
Framework vs kit
| Plasmo (free framework) | ExtensionStart (paid kit on WXT) | |
|---|---|---|
| Category | Extension build framework (WXT/CRXJS alternative) | Starter kit: product code built on the WXT framework |
| Price | Free, MIT (Itero platform has paid tiers) | One-time purchase, full monorepo source |
| Maintenance | Last stable release May 2025; occasional commits since (as of July 2026) | Kit actively developed; underlying WXT framework releasing as of July 2026 |
| What you get | Entrypoints, bundling, HMR, multi-browser builds, Itero previews | Auth, Stripe billing, server-enforced entitlements, gate/paywall engine, hardened content-script UI, backend, publishing CI |
| Monetization | Not framework scope; bring your own | The kit's core: billing, entitlements, and paywall timing with store-policy guardrails |
| Tests | Framework's own; your app's tests are up to you | 411 unit tests + 12 Playwright e2e specs against the built extension, included |
How to actually decide
First pick your framework layer: in mid-2026 that mostly means WXT for new projects, Plasmo if Itero and its React DX outweigh the release-cadence risk for you, CRXJS if you want a thin Vite plugin. That choice costs nothing either way. Then, separately: if your extension will charge money, decide whether to build the auth/billing/paywall/testing layer yourself or buy it. ExtensionStart only makes sense at that second step, and only on WXT.
Frequently asked questions
Is Plasmo free?
Yes. The Plasmo framework is free and open source (MIT). Itero, Plasmo's hosted preview/beta-testing platform, has paid tiers, but the framework itself costs nothing.
Is Plasmo still maintained in 2026?
Its last stable release, v0.90.5, shipped on May 17, 2025, over a year before this page was last verified (July 2026). The repository still shows occasional commits, and WXT's own comparison describes Plasmo as appearing to be in maintenance mode. It works today; whether that release cadence is acceptable for a commercial product is your call.
Does ExtensionStart work with Plasmo?
No. ExtensionStart is built on WXT, and the framework layer isn't swappable: entrypoints, manifest generation, and the build pipeline are WXT's. If you're committed to Plasmo, the kit isn't for you.
Can I migrate a Plasmo extension to WXT (or to ExtensionStart)?
Yes, manually. Plasmo and WXT share a similar file-based entrypoint model and both are React-friendly, so most application code ports with mechanical changes; the framework-specific APIs (storage, messaging wrappers) need rewriting. WXT's docs cover migration from Plasmo.