Turbopack is now Next.js’s default bundler for both development and production builds in Next.js 16. It is an incremental bundler written in Rust and integrated into Next.js—not a separate framework. The shift began with production builds entering beta in Next.js 15.5; Next.js 16 made them stable. The Next.js team reports faster builds, but the gains vary by project, so teams should check output and performance against their own workloads.
What Turbopack does in Next.js
The Next.js API Reference describes Turbopack as “an incremental bundler optimized for JavaScript and TypeScript, written in Rust, and built into Next.js.” Incremental bundling means it can focus work on what has changed rather than rebuilding everything after each edit. For developers, that can mean quicker feedback during development; for production, it is the system that compiles the application for deployment.
As an Amazon Associate I earn from qualifying purchases.
Because Turbopack is built into Next.js, adopting it is a bundler choice within the framework, not a move to another framework. The official documentation is at Next.js Turbopack documentation.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
How Turbopack became the default
| Release | What changed |
|---|---|
| Next.js 13, October 25, 2022 | Turbopack debuted as an alpha for development through next dev --turbo. |
| Next.js 15, October 21, 2024 | Turbopack for development became stable. |
| Next.js 15.5, August 18, 2025 | Production builds with Turbopack entered beta through next build --turbopack. |
| Next.js 16, October 21, 2025 | Turbopack became stable for production builds and the default bundler for new projects. Teams could still select webpack with --webpack. |
As of October 7, 2026, the official Next.js blog index references Next.js 16.3.3 as Active LTS in an August 2026 security notice and includes later Turbopack updates. Support status and release details can change; check the Next.js blog for current announcements.
#1 Best Overall
How much faster is it?
The Next.js team’s Next.js 16 announcement gives expected improvements of 2–5× faster production builds and up to 10× faster Fast Refresh. Those are vendor-reported figures, not independent benchmarks or a promise that every application will see those gains. Fast Refresh is the development feedback loop that applies code changes while an app is running.
The team’s earlier Next.js 15.5 beta post reported these selected compilation comparisons:
Rank #2
| Test context | Reported improvement |
|---|---|
| 4-core machine | 2× faster |
| 14-core machine | 2.2× faster |
| Small site, 10K modules | 4× faster |
| Medium site, 40K modules | 2.5× faster |
| Large site, 70K modules | 5× faster |
These figures describe the Next.js team’s selected comparisons, not a universal result for projects with the same module count. The team said smaller projects or machines could see marginal or neutral build-time improvement, in part compared with webpack’s persistent cache. Read the Next.js 15.5 announcement and Next.js 16 announcement for the original qualifications and release context.
What to check before switching a project
Next.js 16’s default matters most for teams whose builds or development feedback are slow. The default alone does not establish that every app will compile faster or produce identical bundles. Evaluate it with your own codebase and deployment workflow.
- Build time: Compare repeated production builds under the same machine, cache, and environment conditions. A single run can be distorted by caching or other machine activity.
- Development feedback: Check how quickly edits appear through Fast Refresh in the parts of the app where your team spends time.
- Bundle output: The 15.5 beta announcement noted edge cases where webpack produced more optimized bundles. Inspect output size and behavior rather than treating build speed as the only measure.
- CSS behavior: Different CSS side-effect heuristics can change concatenation order. If styles rely on ordering, test rendered pages for visual regressions.
- Custom webpack setup: If your project depends on webpack-specific configuration, test the migration before changing the default. Next.js 16 retained webpack selection through the
--webpackflag.
When to keep using webpack
There is no need to treat the default as a forced migration. A team with a custom webpack configuration, an output difference it cannot accept, or no measurable improvement in its own workload can continue with webpack in Next.js 16 using --webpack. Revisit that choice when project needs or Next.js releases change.
For projects without those constraints, Turbopack is the stable default in Next.js 16 for both development and production. The practical decision is whether it works correctly and delivers a useful improvement for your application—not whether a headline speed multiplier applies to your setup.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Free tools Windows power users keep installed
One-click scans. No signup required.
