Test and improve application performance
Turbopack in Next.js 16: What Changes in Development and Builds
Learn how Turbopack affects first visits, edits, and restarts—and what the Next.js 16.3 preview says about build caching.

Turbopack is Next.js’s bundler. Its incremental compilation reuses work when source files change, but that does not make every wait during development the same kind of wait. A first route visit, an edit, a development-server restart, and a build can each exercise a different part of the workflow.
Check the version, then start development
Check the Next.js version installed in your project before applying a release-specific default. The Next.js 16.2 Turbopack update describes Turbopack as already having become Next.js’s default bundler. In that 16.2 context, the standard next dev command is the development starting point; do not assume the same default for every older version. For broader upgrade context, see our guide to what changed from Next.js 13 to 16.
A minimal package.json scripts fragment keeps development and builds separate:
{
"scripts": {
"dev": "next dev",
"build": "next build"
}
}
Earlier, the stable Turbopack development announcement documented next dev --turbo as an opt-in command. That announcement also says Turbopack supports both App Router and Pages Router. Check which version you have before copying an older command into a current workflow.
Expect a first-visit compile, then a narrower edit loop
Start development:
next dev
Visit a route that has not yet been loaded in that session. Next.js compiles routes on demand in development rather than compiling every possible route before it is needed. The first visit can therefore involve compiling that route’s entrypoint and dependencies; a quick server start does not mean every route is already compiled.
Now edit a file used by that route and observe the next refresh. Turbopack’s incremental compilation caches previous work and avoids recompiling unchanged files. Its dependency tracking lets a change trigger recomputation of affected work rather than treating the whole route as new. The incremental computation explanation describes how changes propagate through that work.
Keep the observations separate. A first visit and an edit do not start with the same available work, and neither tells you by itself what will happen after stopping the server. The time saved depends on the project and the change; one refresh is not a benchmark or a promised speedup.
A restart is a different cache check
The Next.js 16.1 release notes say Turbopack filesystem caching for next dev became stable and enabled by default. It stores compiler artifacts on disk for reuse after restarting the development server. That differs from reusing work while editing with the server still running: before 16.1, the incremental caches described by the Turbopack team were held only in memory. With the 16.1 filesystem cache, dependency graphs and intermediate results can survive a restart.
If you are using Next.js 16.1 or later, load a route, stop next dev, restart it, and revisit the same route. Compare the compilation work with the initial visit without assuming a fixed improvement. This checks reuse of compiler work, not whether your application’s fetched data is fresh.
Check builds on their own terms
Run a build separately from the development checks:
next build
Do not carry the development-cache rule over to builds without checking the version. In the Next.js 16.1 release notes, filesystem caching for next build was still something to be stabilized following that release. The Next.js 16.3 preview notes describe persistent disk caching for next build as available by default: when Turbopack finds cached work at the start of a build, it can read it before compiling new changes. That is a preview-note claim, not an assertion here about the generally available 16.3 release.
For CI runs evaluating that preview behavior, the build cache lives in .next/cache. A later run can reuse those entries only if that directory is restored between runs. Check the restore step before attributing a build-time difference to persistent caching; no hosting platform or fixed speedup is implied.
A first development visit checks on-demand route compilation. An edit checks incremental reuse in a running server. A restart checks reuse of development compiler artifacts from disk. A separate build checks build behavior—and, for the documented 16.3 preview cache in CI, whether .next/cache was restored. They are four checks, not one Turbopack speed test.




