static-rendering

Pre-render Next.js pages at build time by configuring static generation with getStaticProps for data fetching and getStaticPaths for dynamic routes. This eliminates runtime server rendering overhead, delivering cacheable CDN-ready HTML with improved Time To First Byte.

Static generation pre-renders HTML at build time rather than per request. Use it for stable content like marketing pages, blog listings, and product detail pages where parameters are known during build, eliminating slow server response times and heavy client JavaScript overhead.

Yes, statically generate dynamic routes by enumerating known parameter sets using getStaticPaths or generateStaticParams. This pre-renders individual detail pages into static HTML at build time so each product page loads quickly from the CDN without runtime server work.

Yes, static rendering optionally supports Incremental Static Regeneration (ISR) for periodic content updates. ISR allows you to update static pages after the initial build without rebuilding the whole site, making it suitable for content that changes periodically but not per request.

Avoid static generation for routes that depend on per-request user state or frequently changing data. It is designed for stable content like marketing pages and product listings where parameters are known during build, not for personalized dashboards or real-time data requiring server rendering.