Build caching
Improve Pages build times by turning on build caching to restore dependencies and build output between builds. The first build to occur after enabling build caching on your Pages project will save to cache. Every subsequent build will restore from cache unless configured otherwise.
Build caching requires the V2 build system or later. To update from V1, refer to the V2 build system migration instructions.
To enable build caching in the Cloudflare dashboard:
- Log in to the Cloudflare dashboard ↗ and select your account.
- In Account Home, select Workers & Pages.
- In Overview, select your Pages project.
- Go to Settings > Build > Build cache and select Enable.
The build cache can be cleared for a project if needed, such as when debugging build issues. To clear the build cache:
- Log in to the Cloudflare dashboard ↗ and select your account.
- In Account Home, select Workers & Pages.
- In Overview, select your Pages project.
- Go to Settings > Build > Build cache.
- Select Clear Cache to clear the build cache.
When enabled, the build cache will automatically detect and cache data from each build. Refer to Frameworks to review what directories are automatically saved and restored from the build cache.
Package manager caches are automatically saved to the build cache to speed up dependency installation. Pages will cache the global cache directories of the following package managers:
Caching the build output from frameworks can speed up subsequent build times. The build cache supports the following frameworks:
| Framework | Directories cached |
|---|---|
| Astro | node_modules/.astro |
| Docusaurus | node_modules/.cache, .docusaurus, build |
| Eleventy | .cache |
| Gatsby | .cache, public |
| Next.js | .next/cache |
| Nuxt | node_modules/.cache/nuxt |
The following limits are imposed for build caching:
- Retention: Cache is purged seven days after its last read date. Unread cache artifacts are purged seven days after creation.
- Storage: Every project is allocated 10 GB. If the project cache exceeds this limit, the project will automatically start deleting artifacts that were read least recently.