Next.js 16 Stabilizes Partial Prerendering with New Cache Components Feature

Next.js 16 has introduced Cache Components, a stable implementation of Partial Prerendering (PPR) that allows a single route to serve static, cached, and dynamic content simultaneously. The update replaces the old experimental PPR flag and the unstable_cache API with a unified cacheComponents config switch and a new use cache directive. Developers can now classify each part of a route into three buckets — static, cached, or dynamic — enabling faster page loads by streaming personalized content after the static shell renders instantly. The use cache directive works at the file, component, or function level, with Next.js automatically generating cache keys from arguments and closure variables. Built-in cache lifecycle profiles and tag-based invalidation give developers fine-grained control over how long data stays fresh.