What is Incremental Static Regeneration (ISR)?

Incremental Static Regeneration is a hybrid rendering strategy that combines the speed of static-site-generation with the freshness of server-side-rendering. Pages are pre-rendered, cached at the edge and re-built in the background after a configurable TTL or after a webhook signals a content change. ISR is the workhorse strategy for large headless catalogs.

Definition

With ISR, the first request to a route returns the cached static HTML, while a regeneration job runs server-side to produce a new version. Subsequent requests receive the refreshed page once it is ready. Next.js popularized ISR with revalidate intervals and on-demand revalidation via webhooks, and similar models exist in Nuxt, SvelteKit and Astro. The cached HTML lives at the edge of a content-delivery-network-cdn or in an edge worker like Vercel Edge or Cloudflare Workers, giving TTFB comparable to pure SSG.

Why it matters

For commerce sites with millions of PDPs, building everything at once is impractical and rebuilding the whole site on each content change is wasteful. ISR lets teams treat the catalog as an evolving dataset: high-traffic pages stay warm in cache, cold pages regenerate on demand and inventory or pricing updates propagate within seconds via revalidation hooks. The result is excellent LCP and TTFB across the long tail, without sacrificing the editorial agility of a headless CMS, and with predictable infrastructure cost.

Use cases

Composable-commerce stacks use ISR for category and product pages where price, badges and stock change frequently but personalization is not strictly required. A typical flow: Hygraph, Contentful or Sanity emit webhooks on publish, the storefront in Next.js or Nuxt revalidates the affected slugs on Vercel or Netlify, and the new HTML is pushed across the edge network. ISR is often layered with Edge Rendering for personalized fragments and with image-optimization pipelines so static shells stay cacheable. It is also a key enabler when migrating from a monolithic-architecture to headless-commerce because it keeps performance budgets stable during incremental rollouts.

Related

Explore Composable Headless Frontend · Performance and Core Web Vitals.