The Next.js site has a new look! We've redesigned the homepage, /docs, /blog, and more, with a consistent design that keeps the focus on the content. nextjs.org A few highlights ↓

Next.js 16.4 • Cache Components by default in new apps • Static output guarantees and more control over prefetching • Agent-guided upgrades and feedback • 20–25% smaller Turbopack disk cache • Faster development and smaller bundles nextjs.org/blog/next-16-4

The Next.js September security release is planned for September 30, 2026. It will address nine vulnerabilities, including one critical and two high-severity issues, with fixes in 16.3.7 and 15.5.27. Upgrade once they are available. nextjs.org/blog/upcoming-nex…

The September 22 out-of-band Next.js security update is now available. It addresses a critical upstream issue affecting Next.js 16. Next.js 15 is not affected, but 15.5.26 adds hardening. ▲ ~/ npm install next@16.3.6 ▲ ~/ npm install next@15.5.26 nextjs.org/blog/nextjs-secur…

An out-of-band Next.js security update is planned for September 22, 2026. It addresses a critical issue in an upstream dependency. Upgrade to Next.js 16.3.6 or 15.5.26 as soon as they are available. nextjs.org/blog/upcoming-nex…

Excited to formally introduce Vercel Labs. vercel.com/labs is the home for the in-public research and experimentation arm of Vercel. 247 million downloads in, we wanted to, also in public, share what we're supporting, what we're researching, and what experiments didn't pan out. Kudos to @ctatedev and @cramforce for shaping this great initiative and iterating in public.

We’ve resolved 1500 issues, reducing duplicates, already fixed issues, and issues that no longer reproduce in the latest version. Incredibly excited about the research and work Marcos did to consistently investigate and reproduce new issue reports. Learn more in the post!

If you intern at Vercel, you can work on incredible projects like this one. Improving Next.js chunking can yield massive efficiency improvements at internet scale. Excellent writeup by @sam_poder

Your next design system is… Markdown. We wrote about how 𝙳𝙴𝚂𝙸𝙶𝙽.𝚖𝚍 is helping solve the hardest problem in AI today: slop. And how you can truly, finally scale design taste within a large organization.

I rebuilt an older Vercel book search demo with Next.js 16.3 Instant Navigations: next-books.dev Instant Navigations lets server-rendered routes respond immediately when you click, even on a throttled connection: 𝚌𝚘𝚗𝚜𝚝 𝚗𝚎𝚡𝚝𝙲𝚘𝚗𝚏𝚒𝚐 = { 𝚌𝚊𝚌𝚑𝚎𝙲𝚘𝚖𝚙𝚘𝚗𝚎𝚗𝚝𝚜: 𝚝𝚛𝚞𝚎, 𝚙𝚊𝚛𝚝𝚒𝚊𝚕𝙿𝚛𝚎𝚏𝚎𝚝𝚌𝚑𝚒𝚗𝚐: 𝚝𝚛𝚞𝚎 }; Cache Components prerenders static, cached, and fallback UI. Partial Prefetching brings that reusable route UI to the browser before navigation. Add 𝚙𝚛𝚎𝚏𝚎𝚝𝚌𝚑={𝚝𝚛𝚞𝚎} when a link should also resolve its URL-dependent content before the click. Anything still missing loads on the server and streams into its Suspense boundary. The filters use 𝚞𝚜𝚎𝚃𝚛𝚊𝚗𝚜𝚒𝚝𝚒𝚘𝚗 to fade the catalog while the server updates and 𝚞𝚜𝚎𝙾𝚙𝚝𝚒𝚖𝚒𝚜𝚝𝚒𝚌 to apply the next filter values immediately. Rebuilding the demo also improved initial loading. First Contentful Paint was 44% faster and Largest Contentful Paint was 33% faster than the original. See the source and learn more below ↓

We’ve moved the scheduled August Next.js security release forward to today, August 25, to include a fix for an additional critical severity vulnerability. nextjs.org/blog/nextjs-secur… Next.js 16.3.3 and 15.5.24 will include fixes for both vulnerabilities. Upgrade once they are available.

We're the Next.js team. Ask us anything! We recently shipped Next.js 16.3, and we’re excited to talk about what’s new, how we approached the release, where we are going, and what we’ve learned while building and maintaining Next. Ask us anything about Next 16.3, App Router, React Server Components, performance, caching, upgrading your applications, contributing to the framework, or what it’s like to work on Next.js.

Instant Navigations in Next.js 16.3 lets you achieve snappy, app-like UX without giving up the benefits of Server Components. See how Cache Components and Partial Prefetching come together in a music player, social feed, calendar, and team chat. nextjs.org/blog/building-app…

Next.js team AMA is live now! teddit.net/r/nextjs/comments…

I've been using React's <𝚅𝚒𝚎𝚠𝚃𝚛𝚊𝚗𝚜𝚒𝚝𝚒𝚘𝚗> throughout my Next.js SPA series to make the demos smoother and more alive. Here are the patterns I use most: 1. Suspense reveals 2. Morphing content into place 3. Page transitions See each pattern, plus the guide and Skill ↓

Navigations in v0 got ~3.5× faster with Next.js 16.3. An agent ran this loop on each slow nav: 1. Write a failing 𝚒𝚗𝚜𝚝𝚊𝚗𝚝() test 2. Apply a fix from the Skill 3. Re-run the test 4. Repeat 2–3 until it passes nextjs.org/blog/making-v0-na…

I created a series centered on Instant Navigations in Next.js 16.3, showing how you can build apps that feel like SPAs while still rendering and fetching data on the server. See the full series below ↓ What would you like to learn more about? Which demo apps or real-world patterns are missing?

Building SPA-like experiences with Next.js (9) With Instant Navigations in Next.js 16.3, you can build complex, authenticated apps that feel like SPAs while still rendering and fetching data on the server. Turn on 𝚌𝚊𝚌𝚑𝚎𝙲𝚘𝚖𝚙𝚘𝚗𝚎𝚗𝚝𝚜 and 𝚙𝚊𝚛𝚝𝚒𝚊𝚕𝙿𝚛𝚎𝚏𝚎𝚝𝚌𝚑𝚒𝚗𝚐. Cache reusable reads with '𝚞𝚜𝚎 𝚌𝚊𝚌𝚑𝚎' or stream uncached data behind Suspense. <𝙻𝚒𝚗𝚔> components in view then share one prefetched App Shell per route, and 𝚙𝚛𝚎𝚏𝚎𝚝𝚌𝚑={𝚝𝚛𝚞𝚎} can also include URL-dependent content. Add as much client-side interaction as the interface needs with '𝚞𝚜𝚎 𝚌𝚕𝚒𝚎𝚗𝚝'. Transitions and optimistic updates keep mutations responsive while Server Functions write changes and call 𝚞𝚙𝚍𝚊𝚝𝚎𝚃𝚊𝚐 for affected cached data. Live demo, source code, and docs below ↓

Building SPA-like experiences with Next.js (7) With Suspense, you can stream your page in so it loads fast (LCP) and stays stable (CLS). Sometimes you don't know the size of your content until it loads. If you split it into separate boundaries, they resolve independently and push each other around as they land. Instead, you can nest the boundaries. Everything still starts loading at once, so it's just as fast as splitting them up. Nesting waits to show a section until the one above it is in place, so the page settles from the top down. <𝚂𝚞𝚜𝚙𝚎𝚗𝚜𝚎 𝚏𝚊𝚕𝚕𝚋𝚊𝚌𝚔={<𝙿𝚘𝚜𝚝𝚂𝚔𝚎𝚕𝚎𝚝𝚘𝚗 />}> <𝙿𝚘𝚜𝚝 /> <𝚂𝚞𝚜𝚙𝚎𝚗𝚜𝚎 𝚏𝚊𝚕𝚕𝚋𝚊𝚌𝚔={<𝚁𝚎𝚙𝚕𝚒𝚎𝚜𝚂𝚔𝚎𝚕𝚎𝚝𝚘𝚗 />}> <𝚁𝚎𝚙𝚕𝚒𝚎𝚜 /> </𝚂𝚞𝚜𝚙𝚎𝚗𝚜𝚎> </𝚂𝚞𝚜𝚙𝚎𝚗𝚜𝚎> Live demo, source code, and docs below ↓

Next.js 16.3 is out with next/root-params 🥹🥹🥹 I've literally waited years for this! Use it today with next-intl 🔗↓