Next.js 16 (beta)

Next.js 16 (beta) is now available. This early release provides access to the latest improvements to Turbopack, caching, and the Next.js architecture ahead of the stable release. Highlights for this release include:

• Turbopack (stable): Default bundler for all apps with up to 5-10x faster Fast Refresh, and 2-5x faster builds
• Turbopack File System Caching (beta): Even faster startup and compile times for the largest apps
• React Compiler Support (stable): Built-in integration for automatic memoization
• Build Adapters API (alpha): Create custom adapters to modify the build process
• Enhanced Routing: Optimized navigations and prefetching with layout deduplication and incremental prefetching
• Improved Caching APIs: New updateTag() and refined revalidateTag()
• React 19.2: View Transitions, useEffectEvent(), <Activity/>
• Breaking Changes: Async params, next/image defaults, and more

We encourage you to try the beta and share your feedback. Your testing helps us identify issues and improve Next.js before the stable release. Please report any bugs or issues you encounter on GitHub.

Upgrade to the beta:

# Use the automated upgrade CLI
npx @next/codemod@canary upgrade beta
 
# ...or upgrade manually
npm install next@beta react@latest react-dom@latest
 
# ...or start a new project
npx create-next-app@beta

Developer Experience

Turbopack (stable)

Turbopack has reached stability for both development and production builds, and is now the default bundler for all new Next.js projects. Since its beta release earlier this summer, adoption has scaled rapidly: more than 50% of development sessions and 20% of production builds on Next.js 15.3+ are already running on Turbopack.

With Turbopack, you can expect:

• 2–5× faster production builds
• Up to 10× faster Fast Refresh

We're making Turbopack the default to bring these performance gains to every Next.js developer, no configuration required. For apps with custom webpack setups, you can continue using webpack by running:

next dev --webpack
next build --webpack

Turbopack File System Caching (beta)

Turbopack now supports filesystem caching in development, storing compiler artifacts on disk between runs for significantly faster compile times across restarts, especially in large projects.

Enable filesystem caching in your configuration:

const nextConfig = {
  experimental: {
    turbopackFileSystemCacheForDev: true,
  },
};
 
export default nextConfig;

All internal Vercel apps are already using this feature, and we’ve seen notable improvements in developer productivity across large repositories.

We’d love to hear your feedback as we iterate on filesystem caching. Please try it out and share your experience.

Simplified create-next-app

create-next-app has been redesigned with a simplified setup flow, updated project structure, and improved defaults. The new template includes the App Router by default, TypeScript-first configuration, Tailwind CSS, and ESLint.

Build Adapters API (alpha)

Following the Build Adapters RFC, we've worked with the community and deployment platforms to deliver the first alpha version of the Build Adapters API.

Build Adapters allow you to create custom adapters that hook into the build process, enabling deployment platforms and custom build integrations to modify Next.js configuration or process build output.

const nextConfig = {
  experimental: {
    adapterPath: require.resolve('./my-adapter.js'),
  },
};
 
module.exports = nextConfig;

Share your feedback in the RFC discussion.

React Compiler Support (stable)

Built-in support for the React Compiler is now stable in Next.js 16 following the React Compiler's 1.0 release. The React Compiler automatically memoizes components, reducing unnecessary re-renders with zero manual code changes.

The reactCompiler configuration option has been promoted from experimental to stable. It is not enabled by default as we continue gathering build performance data across different application types. Expect compile times in development and during builds to be higher when enabling this option as the React Compiler relies on Babel.

const nextConfig = {
  reactCompiler: true,
};
 
export default nextConfig;

Install the latest version of the React Compiler plugin:

npm install babel-plugin-react-compiler@latest

Core Features & Architecture

Enhanced Routing and Navigation

Next.js 16 includes a complete overhaul of the routing and navigation system, making page transitions leaner and faster.

Layout deduplication: When prefetching multiple URLs with a shared layout, the layout is downloaded once instead of separately for each Link. For example, a page with 50 product links now downloads the shared layout once instead of 50 times, dramatically reducing the network transfer size.

Incremental prefetching: Next.js only prefetches parts not already in cache, rather than entire pages. The prefetch cache now:

• Cancels requests when the link leaves the viewport
• Prioritizes link prefetching on hover or when re-entering the viewport
• Re-prefetches links when their data is invalidated
• Works seamlessly with upcoming features like Cache Components

Trade-off: You may see more individual prefetch requests, but with much lower total transfer sizes. We believe this is the right trade-off for nearly all applications. If the increased request count causes issues, please let us know. We're working on additional optimizations to inline data chunks more efficiently.

These changes require no code modifications and are designed to improve performance across all apps.

PPR and Cache Components

Next.js 16 removes the experimental Partial Pre-Rendering (PPR) flag and configuration options. PPR is being integrated into Cache Components.

Starting with Next.js 16, you can opt into PPR using the experimental.cacheComponents configuration. There are differences in the implementation and Cache Components brings additional features and behaviors that will be documented and announced ahead of Next.js Conf and the Next.js 16 stable release.

If your application relies on PPR (experimental.ppr = true): Stay on the pinned version of Next.js canary you currently use. If you have trouble migrating, stay on your current version for now, and we will provide a migration guide ahead of the stable release.

Improved Caching APIs

Next.js 16 introduces refined caching APIs for more explicit control over cache behavior.

revalidateTag() (updated)

revalidateTag() now requires a cacheLife profile as the second argument to enable stale-while-revalidate (SWR) behavior:

import { revalidateTag } from 'next/cache';
 
// ✅ Use built-in cacheLife profile (we recommend 'max' for most cases)
revalidateTag('blog-posts', 'max');
 
// Or use other built-in profiles
revalidateTag('news-feed', 'hours');
revalidateTag('analytics', 'days');
 
// Or use an inline object with a custom revalidation time
revalidateTag('products', { revalidate: 3600 });
 
// ⚠️ Deprecated - single argument form
revalidateTag('blog-posts');

The profile argument accepts built-in cacheLife profile names (like 'max', 'hours', 'days') or custom profiles defined in your next.config. You can also pass an inline { revalidate: number } object. We recommend using 'max' for most cases, as it enables background revalidation for long-lived content. When users request tagged content, they receive cached data immediately while Next.js revalidates in the background.

Use revalidateTag() when you want to invalidate only properly tagged cached entries with stale-while-revalidate behavior. This is ideal for static content that can tolerate eventual consistency.

Migration guidance: Add the second argument with a cacheLife profile (we recommend 'max') for SWR behavior, or use updateTag() in Server Actions if you need read-your-writes semantics.

updateTag() (new)

updateTag() is a new Server Actions-only API that provides read-your-writes semantics, expiring and immediately refreshing cached data within the same request:

'use server';
 
import { updateTag } from 'next/cache';
 
export async function updateUserProfile(userId: string, profile: Profile) {
  await db.users.update(userId, profile);
 
  // Expire cache and refresh immediately - user sees their changes right away
  updateTag(`user-${userId}`);
}

This ensures interactive features reflect changes immediately. Perfect for forms, user settings, and any workflow where users expect to see their updates instantly.

refresh() (new)

refresh() is a new Server Actions-only API for refreshing uncached data only. It doesn't touch the cache at all:

'use server';
 
import { refresh } from 'next/cache';
 
export async function markNotificationAsRead(notificationId: string) {
  // Update the notification in the database
  await db.notifications.markAsRead(notificationId);
 
  // Refresh the notification count displayed in the header
  // (which is fetched separately and not cached)
  refresh();
}

This API is complementary to the client-side router.refresh(). Use it when you need to refresh uncached data displayed elsewhere on the page after performing an action. Your cached page shells and static content remain fast while dynamic data like notification counts, live metrics, or status indicators refresh.

React 19.2 and Canary Features

The App Router in Next.js 16 uses the latest React Canary release, which includes the newly released React 19.2 features and other features being incrementally stabilized. Highlights include:

• View Transitions: Animate elements that update inside a Transition or navigation
• useEffectEvent: Extract non-reactive logic from Effects into reusable Effect Event functions
• Activity: Render "background activity" by hiding UI with display: none while maintaining state and cleaning up Effects

Learn more in the React 19.2 announcement.

Breaking Changes and Other Updates

Version Requirements

Removals

These features were previously deprecated and are now removed:

Behavior Changes

These features have new default behaviors in Next.js 16:

Deprecations

These features are deprecated in Next.js 16 and will be removed in a future version:

Additional Improvements

• Performance improvements: Significant performance optimizations for next dev and next start commands
• Node.js native TypeScript for next.config.ts: Run next dev, next build, and next start commands with --experimental-next-config-strip-types flag to enable native TypeScript for next.config.ts.

We'll aim to share a more comprehensive migration guide ahead of the stable release in our documentation.

Feedback and Community

Share your feedback and help shape the future of Next.js:

• GitHub Discussions
• GitHub Issues
• Discord Community

Contributors

Next.js is the result of the combined work of over 3,000 individual developers. This release was brought to you by:

• The Next.js team: Andrew, Hendrik, Janka, Jiachi, Jimmy, Jiwon, JJ, Josh, Jude, Sam, Sebastian, Sebbie, Wyatt, and Zack.
• The Turbopack team: Benjamin, Josh, Luke, Niklas, Tim, Tobias, and Will.
• The Next.js Docs team: Delba, Rich, Ismael, and Joseph.

Huge thanks to @mischnic, @timneutkens, @unstubbable, @wyattjoh, @Cy-Tek, @lukesandberg, @OoMNoO, @ztanner, @icyJoseph, @huozhi, @gnoff, @ijjk, @povilasv, @dwrth, @obendev, @aymericzip, @devjiwonchoi, @SyMind, @vercel-release-bot, @Shireee, @eps1lon, @dharun36, @kachkaev, @bgw, @yousefdawood7, @TheAlexLichter, @sokra, @ericx0099, @leerob, @Copilot, @fireairforce, @fufuShih, @anvibanga, @hayes, @Milancen123, @martinfrancois, @lubieowoce, @gaojude, @lachlanjc, @liketiger, @styfle, @aaronbrown-vercel, @Samii2383, @FelipeChicaiza, @kevva, @m1abdullahh, @F7b5, @Anshuman71, @RobertFent, @poteto, @chloe-yan, @sireesha-siri, @brian-lou, @joao4xz, @stefanprobst, @samselikoff, @acdlite, @gwkline, @bgub, @brock-statsig, and @karlhorky for helping!