Next.js 16.3 Cuts Dev Memory Use by 90 Percent, and That's the Real Headline

Next.js 16.3 landed with Turbopack changes that matter more than the feature list suggests. Disk caching and a new memory eviction system cut memory use during next dev by up to 90 percent, and the same disk cache makes repeat builds on CI up to 5.5 times faster. Apps that upgraded from 16.2 saw 45% fewer prefetch requests on average, and immutable static assets cut CDN requests by 17% and transferred bytes by 24% on the sites Vercel measured.

None of that is a new API you'd reach for in a component. It's the kind of update that just makes the day to day experience of working in a large Next.js codebase noticeably less painful, less waiting for the dev server to warm up, fewer CI minutes burned on a rebuild that hasn't actually changed much.

Instant Navigations is the headline feature, letting apps preserve client state across page changes and update optimistically without losing the benefits of Server Components. Worth trying, but for anyone running a sizeable Next.js project day to day, it's the memory and build time numbers that will actually change how the work feels.