This is an internal limitation for build size

We do not recommend pre-rendering 30K static pages, as this will linearly increase all build times (you appear already to be approaching the half hour mark for a build)

Instead, move page compilation out of the build process, which means you no longer have to deploy to update content nor will build time scale along with the size of your content library

The easiest solution is to use https://vercel.com/docs/incremental-static-regeneration to create a persistent content cache across builds that you can revalidate at any time

vercel.com

Incremental Static Regeneration (ISR)

ISR serves cached static pages while regenerating content in the background. Vercel's CDN provides fully managed caching and routing for ISR with modern frameworks.

Hi @jacobparis ,

thanks for the info.

I am aware of the drawbacks of generating so many static pages on build. My website has a page for every major city in the world, for multiple languages. That combination makes it reach such numbers easily. The first-hit page performance is very important to me due to SEO reasons. Therefore I prefer SSG to ISG (although I employ ISR for smaller cities of course).

I guess my main question is, what exactly is this limit and why it’s not documented anywhere. I want to know the exact limit, so I can develop the most appropriate mitigation strategy myself (decrease the number of statically generated city pages, decrease the number of languages, upgrading my plan, etc.)