Vercel deployments now show build cache size
Vercel deployment summaries now display the size of the build cache each deployment saved and how close it is to the per-build-machine limit. The same data is available in the Vercel CLI version 65.1.0 or newer via vercel inspect, and through the deployment REST API endpoint.
Why it matters
Uploading build cache counts as billable build time, and a cache exceeding the limit is discarded, so the next build starts without cache and may run slower. Visibility into cache size helps teams diagnose slow or unexpectedly costly builds.
Who should care
Teams and developers deploying Next.js or other frameworks on Vercel, especially those with large build outputs or slow builds.
What you can do
Run vercel inspect on a recent deployment with CLI 65.1.0 or newer to check its build cache size against the limit, and trim large build artifacts if it is close to the maximum.