Web Development · head to head
Preact vs Turbopack

Preact
Web Development
3kB alternative to React with the same modern API
- From
- Free
- Rated
- -

Turbopack
Web Development
Incremental bundler for JavaScript written in Rust
- From
- Free
- Rated
- -
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; Turbopack effectively coupled to Next.js; using it standalone is not the supported path
- They diverge on capability: Preact covers 3kB runtime, Turbopack covers Incremental computation.
Where they differ
Only the attributes on which Preact and Turbopack actually diverge.
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 Preact
- 3kB runtime
- preact/compat
- Same modern API
- Fast rendering
Only in Turbopack
- Incremental computation
- Written in Rust
- Next.js integration
- Fast refresh
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 Turbopack
- Marketing and content sites where JavaScript payload affects Core Web Vitalsnot Turbopack
- Applications targeting low-bandwidth or low-powered devicesnot Turbopack
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
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
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
Pricing, plan by plan
Preact
Free- PreactFree
- Full library
- Commercial use permitted
- No usage limits
Turbopack
Free- TurbopackFree
- Full functionality
- Commercial use permitted
- Community support
Which should you pick?
Choose Preact if
- You need 3kb runtime.
- You want to start without paying.
- You also want preact/compat.
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.
Questions people ask
- Is Preact or Turbopack better?
- Neither clearly leads. Preact starts at Free and Turbopack at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Preact or Turbopack?
- Preact starts at Free and Turbopack at Free.
- Does Preact or Turbopack run on more platforms?
- Preact runs on Web. Turbopack runs on Linux, macOS, Windows.
- 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 Turbopack is typically brought in for.
- What can Preact do that Turbopack cannot?
- Preact covers 3kB runtime, preact/compat, Same modern API, Fast rendering. Turbopack covers Incremental computation, Written in Rust, Next.js integration, Fast refresh.
Answered from the vendors’ own pages
Preact: Is Preact free?
Yes, open source under the MIT licence.
Turbopack: Is Turbopack free?
Yes, open source from Vercel.
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: 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: Why choose Preact over React?
Bundle size, almost always. If payload is not a binding constraint, React’s ecosystem is usually the better trade.
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.
Related pages
Other head to heads
- Preact vs Next.js
- Preact vs Django
- Preact vs MySQL
- Preact vs Flask
- Preact vs React
- Preact vs Vue.js
- Preact vs Tailwind CSS
- Preact vs Docusaurus
- Preact vs Laravel
- Preact vs MUI
- Preact vs Nginx
- Preact vs Remix
- Preact vs esbuild
- Preact vs npm
- Preact vs SolidStart
- Preact vs TanStack Start
- Preact vs Alpine.js
- Preact vs Astro
- Preact vs Carrd
- Turbopack vs Next.js
- Turbopack vs Django
- Turbopack vs MySQL
- Turbopack vs Flask
- Turbopack vs React
- Turbopack vs Vue.js
- Turbopack vs Tailwind CSS
- Turbopack vs Docusaurus
- Turbopack vs Laravel
- Turbopack vs MUI
- Turbopack vs Nginx
- Turbopack vs Remix
- Turbopack vs esbuild
- Turbopack vs npm
- Turbopack vs SolidStart
- Turbopack vs TanStack Start
- Turbopack vs Alpine.js
- Turbopack vs Astro
- Turbopack vs Carrd
