Skip to main content
Purge cached files when you need visitors to see updated content immediately rather than waiting for cache expiration. You can purge the entire Pull Zone, only files with a specific tag, or specific URLs. The dashboard supports full and tag purges. URL purges are available through the API.
Purging large zones puts temporary load on your origin server while content is re-cached. Performance may decrease briefly until edge nodes repopulate.
Bunny CDN does not monitor your origin for file changes. Once a file is cached, it stays cached until its Cache-Control lifetime expires or it’s evicted to make room for more popular content. To reflect a change immediately, purge the cache or serve the file under a new query string (such as ?v=2).

​
Dashboard

1

Open your Pull Zone

Go to your Pull Zone in the dashboard and click Purge Cache in the top right corner.
Purge cache button
2

Enter a search tag (optional)

Leave the search tag empty to purge the entire Pull Zone. If you enter a tag, only files with a matching CDN-Tag header are removed. The rest of your cache stays intact.
Purge cache by tag
3

Confirm the purge

Click Purge to clear the cache.

​
API

You can also purge cache programmatically. See the Core API reference for full details.

​
Full Pull Zone purge

Use the Purge Cache endpoint without a CacheTag to clear every cached file in the Pull Zone.

​
Purge by tag

Tag responses from your origin with the CDN-Tag header. Then use the Purge Cache endpoint with CacheTag set to purge all files matching that tag. Useful for invalidating all assets related to a specific product, user, or category without clearing your entire cache.
CDN-Tag header values are limited to 1024 bytes. Longer values are truncated.

​
Purge by URL

Use the Purge URL endpoint to purge a single file or a path prefix. The URL you send decides the purge type, which also decides the rate limit that applies:
  • Exact: a URL without wildcards, where the path does not end with / or exactPath is true. For example, https://example.com/image.png.
  • Prefix: the URL contains a *, or the path ends with / and exactPath is false. For example, https://example.com/images/* or https://example.com/assets/.

​
Rate limits

To ensure platform stability, the Purge API is protected by rate limits. These limits are designed to keep normal purge workflows fast while preventing abuse or accidental overload. Purge requests are rate-limited using a token bucket mechanism:
  • Limits are applied per account
  • Limits are applied per purge type
  • Each purge item consumes 1 token
  • Tokens refill steadily over time
Every purge counts toward one of two purge types: If a request exceeds the available rate limit, the API returns a 429 Too Many Requests response with guidance on when to retry.

​
Default rate limits

If your workload requires higher purge throughput, please contact support to discuss custom rate limits.

​
Perma-Cache behavior

If you’re using Perma-Cache:
  • Full zone purge: Clears CDN cache but Perma-Cache switches to a new directory (manually delete the old folder if needed)
  • Tag-based purging: Not supported with Perma-Cache enabled
Last modified on September 25, 2026