--- title: Next.js 16.3 released with major memory and build... description: Next.js 16.3 has been released with significant performance improvements, including up to 90% reduction in memory usage during development, faster builds,... canonical: https://daily.dev/posts/next-js-16-3-released-with-major-memory-and-build-improvements-gqb1uxokv twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Next.js 16.3 released with major memory and build improvements | daily.dev og:description: Next.js 16.3 has been released with significant performance improvements, including up to 90% reduction in memory usage during development, faster builds,... og:url: https://daily.dev/posts/next-js-16-3-released-with-major-memory-and-build-improvements-gqb1uxokv og:image: https://api.daily.dev/og/posts/gQb1uXokv.png og:image:alt: Next.js 16.3 released with major memory and build improvements og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Next.js 16.3 released with major memory and build improvements **[Collections](https://daily.dev/sources/collections)** · 4 min read · 71 upvotes · 6 comments ## Summary Next.js 16.3 has been released with significant performance improvements, including up to 90% reduction in memory usage during development, faster builds, faster type checking, faster rendering, and improved tooling. The announcement is light on technical details beyond these headline metrics. ## Content Next.js 16.3 is out, and it's a substantial release. The headline numbers are real: up to 90% less memory in the dev server, faster builds, and a new Instant Navigations feature that brings SPA-like responsiveness to server-rendered apps without requiring client-side data fetching. ## Dev server memory and build speed The most immediately noticeable change for most developers will be memory. Turbopack now ships with disk caching and memory eviction enabled by default. A 50-route app that previously consumed around 4.6GB of RAM now uses roughly 840MB. If you've ever hit a `FATAL ERROR: JavaScript heap out of memory` crash mid-development, this is the fix. Build times improve too. Filesystem caching gives CI builds a 5.5x speedup, and compilation is about 2.3x faster overall. There's also an experimental Rust-based React Compiler built into Turbopack that cuts cold build times by 34% and warm builds by 46% — opt-in for now, but worth trying. TypeScript 7 is now supported, which brings roughly 10x faster type checking. That one's hard to overstate if you're working on a large codebase. ## Instant Navigations This is the feature getting the most attention. Instant Navigations is an opt-in suite that uses runtime Partial Prerendering (PPR) and browser-side caching to make page transitions feel immediate — without rewriting your app to use client-side data fetching. The way it works: Server Component pages either stream with loading states or serve cached content, depending on what's ready. A new `cacheComponents` option controls this behavior. The Vercel team applied it to v0 using an AI agent loop — the agent wrote failing Playwright tests using a new `instant()` test helper, moved dynamic data fetches behind Suspense boundaries, and iterated until the tests passed. The result was 16 new regression tests and instant navigations across v0's homepage, chat, and settings pages. A `next-cache-components-optimizer` skill is available if you want to run the same process on your own app. There's also a new Navigation Inspector panel in DevTools for debugging prefetch behavior, which is genuinely useful when things don't behave as expected. ## Runtime performance Native Node.js streams now replace web stream conversions for SSR, giving about 22% more request throughput. Not a change you'll configure — it just works. ## Vercel platform improvements On the hosting side, Vercel reports 45% fewer prefetch requests, 17% fewer CDN requests, 24% fewer bytes transferred for static content, and roughly 2x faster p99 route resolution for large sites. Static assets are now immutable and reused across deployments, cutting re-upload time by up to 30%. The route metadata layer was rewritten using JSONL shards, resulting in about 10x fewer cache misses. PPR observability is also launching with this release, so you can see which requests are serving static vs. dynamic content. The routing metadata improvements apply to all frameworks using Vercel's Build Output API, not just Next.js. ## Agent tooling Next.js 16.3 ships with officially maintained agent skill sets and versioned docs specifically for AI coding agents. There's a `next-dev-loop` skill that lets agents verify their changes by actually interacting with a running browser session — controlling the browser, taking screenshots, reading the DOM, console, network, and React tree — rather than just checking that the code compiles. A demo shows Codex autonomously reproducing a spreadsheet-to-chart sync bug, implementing a fix, and visually confirming the result. An 'Instant Insights' feature detects caching errors and generates prompts for agents to fix them. The idea is that even if you ship slow navigations, your agent gets presented with options — like adding a `` for an instant loading shell. ## Other changes - Prefetch requests are now bundled, reducing network chatter - Immutable static asset caching is improved - Custom error boundaries with server retry are supported - Network resilience with offline support is experimental Next.js has now passed one billion downloads. The release had 90 contributors, and includes work that, according to Andrew Clark, traces back to the first Suspense prototype in 2017. ## Questions this post answers ### How much memory does Next.js 16.3 save compared to previous versions in the dev server? Next.js 16.3 reduces dev server memory usage by up to 90% through Turbopack disk caching and memory eviction enabled by default. A 50-route app that previously consumed around 4.6GB of RAM now sits at roughly 840MB. The fix targets V8 heap exhaustion that caused the notorious 'FATAL ERROR: JavaScript heap out of memory' crash on large apps. _Teams hitting memory limits on large Next.js apps track fixes like this on daily.dev before committing to an upgrade._ ### What is Instant Navigations in Next.js 16.3 and how does it work? Instant Navigations is an opt-in feature suite in Next.js 16.3 that gives server-driven apps SPA-like responsiveness without moving data fetching to the client. It combines Partial Prefetching, improved ISR, and browser-side caching via runtime partial prerendering. Pages either stream with loading shells or serve cached content immediately. It is opt-in now and will become the default in a future release. _Developers evaluating whether to adopt Instant Navigations or keep client-side fetching find the trade-offs covered on daily.dev._ ### How much faster are Next.js builds in version 16.3? Repeat builds are up to 5.5x faster in Next.js 16.3 due to incremental filesystem caching in `next build`. An experimental Rust-based React Compiler integrated into Turbopack cuts cold build times by 34% and warm builds by 46% (opt-in). TypeScript 7 integration delivers a 10x improvement in type-check times, and static assets on Vercel are now immutable and reused across deployments, cutting re-upload time by up to 30%. _Engineers deciding when to upgrade Next.js for CI speed gains follow release coverage like this on daily.dev._ ## Community discussion Top comments from developers on daily.dev. **@stephan\_\_mc** · 3 upvotes > The post title seems interesting and the contents even more. But one thing I know is that this framework will have a lot of bugs. Especially in growing projects **@apperside** · 0 upvotes > This is good news, but still next js is easy to use for small project, but it gets complicated on big ones **@matchpoint** · 0 upvotes > Hope the Memory eating issue resolved ## Similar posts on daily.dev - [Next.js 16.3: Instant Navigations, Up to 90% Less Dev Memory and Faster Builds](https://daily.dev/posts/next-js-16-3-instant-navigations-up-to-90-less-dev-memory-and-faster-builds-abksajvqx) · InfoQ · 3 upvotes · 0 comments --- Tags: [#webdev](https://daily.dev/tags/webdev), [#javascript](https://daily.dev/tags/javascript), [#nextjs](https://daily.dev/tags/nextjs) [View this post on daily.dev](https://daily.dev/posts/next-js-16-3-released-with-major-memory-and-build-improvements-gqb1uxokv) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Next.js 16.3 released with major memory and build improvements","url":"https://daily.dev/posts/next-js-16-3-released-with-major-memory-and-build-improvements-gqb1uxokv","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/next-js-16-3-released-with-major-memory-and-build-improvements-gqb1uxokv"},"datePublished":"2026-08-03T22:14:17.987Z","dateModified":"2026-08-10T16:51:24.435Z","description":"Next.js 16.3 has been released with significant performance improvements, including up to 90% reduction in memory usage during development, faster builds,...","isAccessibleForFree":true,"articleSection":"Collections","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Collections","logo":"https://media.daily.dev/image/upload/s--fk_6ycEi--/f_auto,q_auto/v1780996001/logos/collections?_a=BAMAMiWQ0","url":"https://daily.dev/sources/collections"},"commentCount":6,"discussionUrl":"https://daily.dev/posts/next-js-16-3-released-with-major-memory-and-build-improvements-gqb1uxokv","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":71},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":6}],"keywords":"webdev,javascript,nextjs","timeRequired":"PT4M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Collections","item":"https://daily.dev/sources/collections"},{"@type":"ListItem","position":3,"name":"Next.js 16.3 released with major memory and build improvements"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/next-js-16-3-released-with-major-memory-and-build-improvements-gqb1uxokv","comment":[{"@type":"Comment","text":"The post title seems interesting and the contents even more. But one thing I know is that this framework will have a lot of bugs. Especially in growing projects","datePublished":"2026-08-04T23:07:34.263Z","url":"https://daily.dev/posts/gQb1uXokv#c-kZTxd56nQ","author":{"@type":"Person","name":"Stephan Munde","url":"https://daily.dev/stephan__mc","image":"https://media.daily.dev/image/upload/s--5P4c43ol--/f_auto/v1715211786/avatars/avatar_DqDKWn8SLSk3fqkkcDizv"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":3}},{"@type":"Comment","text":"This is good news, but still next js is easy to use for small project, but it gets complicated on big ones","datePublished":"2026-08-07T02:03:43.397Z","url":"https://daily.dev/posts/gQb1uXokv#c-qqkv8Tb73","author":{"@type":"Person","name":"Apperside","url":"https://daily.dev/apperside","image":"https://avatars.githubusercontent.com/u/5955338?v=4"}},{"@type":"Comment","text":"Hope the Memory eating issue resolved","datePublished":"2026-08-07T07:33:47.570Z","url":"https://daily.dev/posts/gQb1uXokv#c-NpRfo8veA","author":{"@type":"Person","name":"Numb Code","url":"https://daily.dev/matchpoint","image":"https://lh3.googleusercontent.com/a/ACg8ocJ86YIewk804FajHaEbzIBiQa9RFZVR0fs-vBpSZ3ObyDY6Qz8=s96-c"}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/next-js-16-3-released-with-major-memory-and-build-improvements-gqb1uxokv#faq","mainEntity":[{"@type":"Question","name":"How much memory does Next.js 16.3 save compared to previous versions in the dev server?","acceptedAnswer":{"@type":"Answer","text":"Next.js 16.3 reduces dev server memory usage by up to 90% through Turbopack disk caching and memory eviction enabled by default. A 50-route app that previously consumed around 4.6GB of RAM now sits at roughly 840MB. The fix targets V8 heap exhaustion that caused the notorious 'FATAL ERROR: JavaScript heap out of memory' crash on large apps. Teams hitting memory limits on large Next.js apps track fixes like this on daily.dev before committing to an upgrade."}},{"@type":"Question","name":"What is Instant Navigations in Next.js 16.3 and how does it work?","acceptedAnswer":{"@type":"Answer","text":"Instant Navigations is an opt-in feature suite in Next.js 16.3 that gives server-driven apps SPA-like responsiveness without moving data fetching to the client. It combines Partial Prefetching, improved ISR, and browser-side caching via runtime partial prerendering. Pages either stream with loading shells or serve cached content immediately. It is opt-in now and will become the default in a future release. Developers evaluating whether to adopt Instant Navigations or keep client-side fetching find the trade-offs covered on daily.dev."}},{"@type":"Question","name":"How much faster are Next.js builds in version 16.3?","acceptedAnswer":{"@type":"Answer","text":"Repeat builds are up to 5.5x faster in Next.js 16.3 due to incremental filesystem caching in `next build`. An experimental Rust-based React Compiler integrated into Turbopack cuts cold build times by 34% and warm builds by 46% (opt-in). TypeScript 7 integration delivers a 10x improvement in type-check times, and static assets on Vercel are now immutable and reused across deployments, cutting re-upload time by up to 30%. Engineers deciding when to upgrade Next.js for CI speed gains follow release coverage like this on daily.dev."}}]} ```