Comparison
WXT vs ExtensionStart: the framework and the kit built on it
This is not a versus page. ExtensionStart is built on WXT; if you buy the kit, you are using WXT. The real question is what the free framework already gives you and what's left to build for a paid extension.
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.
What WXT is
WXT is a free, MIT-licensed framework for building browser extensions: the layer that turns a modern TypeScript project into a working MV3 extension. It's actively maintained (10,000+ GitHub stars; releases shipping as of July 2026, per the repository) and it's excellent at its job: file-based entrypoints, manifest generation per browser, dev-mode HMR, auto-imports, and zip/submit tooling for Chrome, Firefox, and Edge. If you're choosing between WXT, Plasmo, and CRXJS in 2026, we think WXT is the right call, which is why the kit is built on it.
What a framework deliberately doesn't include
WXT ships zero product code, correctly; it's a framework, not a template. Everything specific to a monetized extension is on you: OAuth that works inside an MV3 service worker (web-style Firebase sign-in never will), Stripe checkout and webhooks, an entitlement model the client can't forge, a paywall that won't get your listing rejected, tests for all of it, and a store publishing process. That's the kit's layer.
| WXT (free framework) | ExtensionStart (paid kit, built on WXT) | |
|---|---|---|
| Category | Build framework: entrypoints, manifest generation, HMR, browser targets | Product codebase on top of WXT: monorepo with app, packages, backend, site |
| Price | Free, MIT | One-time purchase; your code after purchase |
| Auth | Not included (framework scope) | Google sign-in via web-auth-flow with offscreen fallback, email/password, anonymous-first account linking |
| Billing | Not included | Stripe checkout, portal, webhook pipeline; server-authoritative entitlements; Hono backend for Cloud Functions |
| Paywall/gates | Not included | Gate engine with timing presets, cooldowns, chaining, and Chrome Web Store policy guardrails |
| Content-script UI | createShadowRootUi primitive | Hardened shadow mounts (rem→px, theme isolation, portals), SPA nav handling, DOM observer, page bridge; e2e-tested against a hostile page |
| Tests | Framework's own tests; testing your app is up to you | 411 unit tests and 12 Playwright e2e specs against the built extension, shipped as part of the kit |
| Publishing | wxt zip / submit commands | CI release pipeline using them: test gates, Chrome staged rollout, Firefox, Edge Partner Center |
| Docs for agents | Framework docs | AGENTS.md encoding MV3 pitfalls, llms.txt, markdown docs mirror |
The honest framing
You'll use a framework either way, and it costs nothing. Whether the kit is worth paying for depends entirely on whether your extension charges money: if it doesn't, WXT plus a free starter (see our Extro comparison) is likely all you need. If it does, the auth/billing/entitlements/paywall/testing layer is months of MV3-specific work; the home page shows the actual repository you'd be buying instead.
Frequently asked questions
Is WXT free?
Yes. WXT is a free, MIT-licensed open-source framework, and buying ExtensionStart changes nothing about that; the kit is application code built on top of WXT, the same way a SaaS starter kit is built on Next.js.
Do I need ExtensionStart to use WXT?
No. WXT alone is a complete framework for building extensions. The kit is for the specific case where your extension charges money: it adds the auth, Stripe billing, server-enforced entitlements, paywall gate engine, test suite, and publishing CI that WXT deliberately leaves to you.
If I buy the kit, am I locked into ExtensionStart's APIs?
You get the full monorepo source and it becomes your codebase. The core packages are framework-free TypeScript with thin React bindings, and the extension app is a standard WXT project; removing a module you don't want is deletion, not ejection.
Does ExtensionStart keep up with WXT releases?
Yes. Tracking WXT updates (and browser breakage generally) is part of the kit's updates policy. WXT is actively developed, which is one of the reasons the kit is built on it rather than on an alternative framework.