Next.js automatically determines that a page is static (can be prerendered) if it has no blocking data requirements. This determination is made by the absence of
getInitialProps in the page.
This feature allows Next.js to emit hybrid applications that contain both server-rendered and statically generated pages.
Statically generated pages are still reactive: Next.js will hydrate your application client-side to give it full interactivity.
One of the main benefits of this feature is that optimized pages require no server-side computation, and can be instantly streamed to the end-user from multiple CDN locations. The result is an ultra fast loading experience for your users.
getInitialProps is present, Next.js will use its default behavior and render the page on-demand, per-request (meaning Server-Side Rendering).
getInitialProps is absent, Next.js will statically optimize your page automatically by prerendering the page to static HTML. During prerendering, the router's
query object will be empty since we do not have
query information to provide during this phase. Any
query values will be populated client-side after hydration.
next build will emit
.html files for statically optimized pages. For example, the result for the page
pages/about.js would be:
And if you add
In development you'll know if
pages/about.js is optimized or not thanks to the included static optimization indicator.