Delivery
Purge content
Purging removes cached content immediately instead of waiting for its TTL to expire. It is the usual move right after a deploy or a content change, and the Purge cache screen is scoped by domain so you always know which property you are clearing.
How it works
- Purge from the dashboard by domain, or target a specific cache key
- Purge activity is reflected in cache stats so you can confirm it took effect
- Underlying payloads live under a tenant-scoped key namespace, keeping purges isolated to your workspace
Good to know
- A broad purge (Full Site) is heavier than a targeted URL purge — prefer the narrowest purge that solves the problem
- A purge can take 2-3 minutes to propagate across the edge
- Up to 10 exact URLs or tags per request
- URL purges without a query string match path-wide variants
- Full Site purges non-image proxy cache only — optimized images are purged with Specific Image URLs