Softwr

Web Development · head to head

Turbopack vs Preact

Turbopack logo

Turbopack

Web Development

Incremental bundler for JavaScript written in Rust

From
Free
Rated
-
Full reviewWebsite
Preact logo

Preact

Web Development

3kB alternative to React with the same modern API

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Turbopack effectively coupled to Next.js; using it standalone is not the supported path; Preact compatibility through preact/compat is good but not total, and some React libraries break in ways that are hard to diagnose
  • They diverge on capability: Turbopack covers Incremental computation, Preact covers 3kB runtime.

Where they differ

Only the attributes on which Turbopack and Preact actually diverge.

Attributes where Turbopack and Preact differ
AttributeTurbopackPreact
PlatformsLinux, macOS, WindowsWeb

Identical on both: starting price (Free), pricing model (Open source, no licence fee), 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 Turbopack

  • Incremental computation
  • Written in Rust
  • Next.js integration
  • Fast refresh

Only in Preact

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

What people use each for

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

Turbopack

  • Large Next.js applications where rebuild time is the daily costnot Preact
  • Teams already on Vercel’s stack wanting faster local feedbacknot Preact
  • Migrating off webpack within Next.js without changing frameworksnot Preact

Preact

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

Where each one falls short

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

Turbopack

  • Effectively coupled to Next.js; using it standalone is not the supported path
  • Younger than the alternatives, and ecosystem plugin support is narrower than webpack’s
  • Benchmark claims have been contested publicly, so measure on your own project rather than trusting headline numbers
  • Being Vercel-driven ties its roadmap to one company’s framework priorities

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

Pricing, plan by plan

Turbopack

Free
  • TurbopackFree
    • Full functionality
    • Commercial use permitted
    • Community support

Preact

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

Which should you pick?

Choose Turbopack if

  • You need incremental computation.
  • You want to start without paying.
  • You work on Linux, macOS, Windows.
  • You also want written in rust.
Turbopack review

Choose Preact if

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

Questions people ask

Is Turbopack or Preact better?
Neither clearly leads. Turbopack 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, Turbopack or Preact?
Turbopack starts at Free and Preact at Free.
Does Turbopack or Preact run on more platforms?
Turbopack runs on Linux, macOS, Windows. Preact runs on Web.
Can I use Turbopack for free?
Both have a free tier, so you can try either at no cost before committing.
What is Turbopack best used for?
Turbopack is most often used for large next.js applications where rebuild time is the daily cost, teams already on vercel’s stack wanting faster local feedback, migrating off webpack within next.js without changing frameworks. Of those, large next.js applications where rebuild time is the daily cost and teams already on vercel’s stack wanting faster local feedback are not what Preact is typically brought in for.
What can Turbopack do that Preact cannot?
Turbopack covers Incremental computation, Written in Rust, Next.js integration, Fast refresh. Preact covers 3kB runtime, preact/compat, Same modern API, Fast rendering.

Answered from the vendors’ own pages

Turbopack: Is Turbopack free?

Yes, open source from Vercel.

Preact: Is Preact free?

Yes, open source under the MIT licence.

Turbopack: Can I use Turbopack without Next.js?

Not really. It is developed as the Next.js bundler, and standalone use is not the supported path.

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.

Turbopack: Is Turbopack faster than Vite?

It depends on the project, and published comparisons have been disputed by both sides. Measure on your own codebase rather than relying on headline figures.

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

More on Turbopack

More on Preact

Keep looking

Other head to heads