{"id":23021,"date":"2026-08-04T18:11:52","date_gmt":"2026-08-04T18:11:52","guid":{"rendered":"https:\/\/scannn.com\/next-js-16-3-next-js\/"},"modified":"2026-08-04T18:11:52","modified_gmt":"2026-08-04T18:11:52","slug":"next-js-16-3-next-js","status":"publish","type":"post","link":"https:\/\/scannn.com\/lv\/next-js-16-3-next-js\/","title":{"rendered":"Next.js 16.3 | Next.js"},"content":{"rendered":"\n
\n

Last month we published a preview release of 16.3 that let you try out SPA-like navigations<\/a>, better AI tooling<\/a>, and a much<\/em> less memory-hungry dev server<\/a>.<\/p>\n

Today, we’re excited to announce that Next.js 16.3 is here!<\/p>\n

This release is packed with improvements for all existing Next.js apps:<\/p>\n

It also includes Instant Navigations<\/strong>, an opt-in suite of tools that brings the responsiveness of client-driven SPAs to Next.js, without sacrificing the benefits that come with its server-driven model:<\/p>\n

The behaviors behind Instant Navigations will become the default in a future major version, as they’re part of our work over the last year to simplify Next.js back to its roots: dynamic by default, with no hidden or implicit caching.<\/p>\n

16.3 also includes experimental features<\/a> you can try today, such as the Rust-based React Compiler and network resilience.<\/p>\n\n

This is our biggest update to the framework since Next.js 16.0 came out last November, and we can’t wait for you to try it.<\/p>\n

Upgrade by installing the latest version of next<\/code> from npm:<\/p>\n

…and keep reading to learn about everything that’s new!<\/p>\n

Improvements for today’s apps<\/g><\/svg><\/span><\/a><\/h2>\n

Next.js 16.3 includes improvements for all existing projects, including lower dev server memory usage, faster rendering, and better runtime performance, all with zero changes to your application code.<\/p>\n

We recommend all apps upgrade to 16.3 to start getting these benefits today.<\/p>\n

Less memory usage in dev<\/g><\/svg><\/span><\/a><\/h3>\n

In 16.3, Turbopack uses up to 90% less memory<\/strong> when running next dev<\/code>. The reduction comes from two new features that are now enabled by default: disk caching for dev (first introduced in 16.1), and memory eviction.<\/p>\n

We’ve been hearing great reports<\/svg><\/span><\/a> from early adopters, and we’re excited to bring these performance improvements to all Next apps.<\/p>\n
\n

Memory usage after compiling 50 routes<\/span><\/p>\n

\n
\n

vercel.com (dashboard)<\/span>~90% smaller<\/span><\/p>\n<\/div>\n<\/div>\n<\/figure>\n

Learn more about Turbopack’s new memory eviction features<\/a>.<\/p>\n

Faster builds<\/g><\/svg><\/span><\/a><\/h3>\n

The disk caching feature that’s been speeding up dev since 16.1 now works with next build<\/code> and is enabled by default. We’ve been dogfooding this in production at Vercel for months and are seeing some projects with 5.5x faster builds<\/strong> on CI.<\/p>\n

\n

Turbopack compile time for `next build`<\/span><\/p>\n

\n
\n

vercel.com\/home<\/span>~1.4\u00d7 faster<\/span><\/p>\n<\/div>\n

\n

vercel.com\/geist<\/span>~5.5\u00d7 faster<\/span><\/p>\n<\/div>\n<\/div>\n<\/figure>\n

Learn more about setting up Turbopack’s new FileSystem Cache<\/a>.<\/p>\n

Faster type checking with TypeScript 7<\/g><\/svg><\/span><\/a><\/h3>\n

Typescript 7<\/svg><\/span><\/a> was released last month, which is a 10x faster native port of TypeScript with much faster type checking.<\/p>\n

To start using TypeScript 7 for type checking during next build<\/code>, just bump your project’s local dependency:<\/p>\n