Exploring the New Features of Next.js 16

Next.js 16 is a foundational release that stabilizes Turbopack, introduces Partial Prerendering as stable, and makes significant changes to async request APIs. This guide covers every major feature with practical examples.

Turbopack: Stable and Production-Ready

Turbopack is now stable and delivers significant performance improvements for both development and production builds.

Enabling Turbopack

Development server with Turbopack:

Performance Improvements

• Up to 76% faster local server startup
• Up to 96% faster code updates with Fast Refresh
• Faster production builds

Partial Prerendering (PPR): Now Stable

PPR combines static and dynamic rendering in a single route, delivering instant static shell while streaming dynamic content.

Enabling PPR

PPR Example: Product Page

Async Request APIs: Breaking Changes

Next.js 16 makes params, searchParams, cookies, headers, and draftMode async to support modern React patterns.

Before: Synchronous APIs

After: Async APIs

Cookies and Headers

New Caching Defaults

Next.js 16 changes caching defaults to be more intuitive:

• GET route handlers are no longer cached by default
• Client-side Router Cache is no longer cached by default

Migration Codemod

Next.js provides an automated codemod to handle async API migrations:

After hook: Cleanup Logic Made Easy

The new after() function lets you execute code after a response is sent, perfect for analytics and cleanup.

Next.js 16 sets a new foundation with stable Turbopack, PPR, and async APIs. While the breaking changes require migration, the performance improvements and developer experience enhancements make the upgrade worthwhile for any serious Next.js application.