Skip to main content
The CDN caches your files at edge locations around the world. When you replace a file, visitors might still see the old cached copy. purge tells Bunny to invalidate the cached copy immediately after every upload and delete.
payload.config.ts

Options

Pass purge: true for defaults, purge: false to disable, or an object to customize:

Requirements

Cache purging is an account-level operation, so it needs a Bunny account API key (not the Storage or Stream key) at the top level, as accountApiKey:
payload.config.ts
Get it from your Bunny dashboard → account menu (top-right) → Account settingsAPI → copy the API key.
Without a global accountApiKey, the config validator throws a startup error — including when only individual collections enable purge.Purging is only performed for Bunny Storage files — it doesn’t apply to Stream videos, which are served from Bunny’s video CDN and cached differently.

Alternative: timestamp-based cache busting

If you don’t want to manage an account API key, urlTransform.appendTimestamp or thumbnail.appendTimestamp add a changing query parameter to URLs instead. This is simpler to set up, but only busts the cache for browsers that re-fetch the URL — it doesn’t proactively clear Bunny’s edge cache.

Collection overrides

See Collection overrides for the full list of options you can tune per collection.