Softwr

Web Development · head to head

Preact vs Qwik

Preact logo

Preact

Web Development

3kB alternative to React with the same modern API

From
Free
Rated
-
Full reviewWebsite
Qwik logo

Qwik

Web Development

Framework for edge computing with instant interactivity and minimal JavaScript

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Preact compatibility through preact/compat is good but not total, and some React libraries break in ways that are hard to diagnose; Qwik different mental model than React requires learning new patterns
  • They diverge on capability: Preact covers 3kB runtime, Qwik covers Resumability.

Where they differ

Only the attributes on which Preact and Qwik actually diverge.

Attributes where Preact and Qwik differ
AttributePreactQwik
Pricing modelOpen source, no licence feeopen-source
PlatformsWebWeb, Edge

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated), category (Web Development).

What each one covers

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 Preact

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

Only in Qwik

  • Resumability
  • Minimal JavaScript
  • Lazy JavaScript execution
  • Edge deployment support
  • Qwik Optimizer
  • Vite integration
  • JSX support

What people use each for

The jobs each tool is most often brought in to do.

Preact

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

Qwik

  • Building ultra-fast web applications with instant page loadsnot Preact
  • Edge-computing-first applications requiring minimal JavaScriptnot Preact
  • Performance-critical applications targeting mobile usersnot Preact
  • Projects requiring sub-second Time to Interactive on slow networksnot Preact

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

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

Qwik

  • Different mental model than React requires learning new patterns
  • Smaller ecosystem and community compared to established frameworks
  • Limited third-party component library support
  • Fewer examples and tutorials in documentation

Pricing, plan by plan

Preact

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

Qwik

Free

No published plan breakdown. See the Qwik review.

Which should you pick?

Choose Preact if

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

Choose Qwik if

  • You need resumability.
  • You want to start without paying.
  • You work on Web, Edge.
  • You also want minimal javascript.
Qwik review

Questions people ask

Is Preact or Qwik better?
Neither clearly leads. Preact starts at Free and Qwik at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Preact or Qwik?
Preact starts at Free and Qwik at Free.
Does Preact or Qwik run on more platforms?
Preact runs on Web. Qwik runs on Web, Edge.
Can I use Preact for free?
Both have a free tier, so you can try either at no cost before committing.
What is Preact best used for?
Preact is most often used for embedded widgets that load inside someone else’s page and must stay small, marketing and content sites where javascript payload affects core web vitals, applications targeting low-bandwidth or low-powered devices. Of those, embedded widgets that load inside someone else’s page and must stay small and marketing and content sites where javascript payload affects core web vitals are not what Qwik is typically brought in for.
What can Preact do that Qwik cannot?
Preact covers 3kB runtime, preact/compat, Same modern API, Fast rendering. Qwik covers Resumability, Minimal JavaScript, Lazy JavaScript execution, Edge deployment support.

Answered from the vendors’ own pages

Preact: Is Preact free?

Yes, open source under the MIT licence.

Qwik: How does Qwik achieve instant interactivity without hydration?

Qwik uses resumability, serializing application state and component tree, then deserializing directly into memory without re-executing component code.

Source
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.

Qwik: What is the typical JavaScript bundle size for a Qwik application?

Qwik applications boot with approximately 1kb of JavaScript regardless of complexity, with additional code loaded on-demand.

Source
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.

Qwik: Can Qwik be deployed to edge computing platforms?

Yes, Qwik supports deployment to Cloudflare Workers, Netlify Edge, Vercel Edge, AWS Lambda, and many other edge platforms.

Source
Share

Related pages

More on Preact

More on Qwik

Keep looking

Other head to heads