Purging the CDN cache
Purging the CDN cache
When you update your site's content or assets, the CDN may serve older cached versions until those cached copies expire. Purging forces the edge to fetch fresh content from your origin immediately.
When to purge
Purge the cache when you:
- Updated CSS, JavaScript, or image files and need changes to show immediately
- Fixed a bug and want to clear the broken version from the edge
- Replaced an uploaded image or media file
- Made changes to a page and want them live globally right now
How to purge
Go to Performance → CDN on your site, then scroll to the Purge cache card.
Purge a single URL
- Enter the full URL in the field (e.g.
https://yourdomain.com/path/to/page) - Click Purge
- Success: "Purged https://yourdomain.com/path/to/page."
Purge the entire site
Leave the URL field blank and click Purge. Success: "Full cache purged."
Cache TTL settings
The Cache TTLs card controls how long content stays cached:
| Setting | What it controls | Default |
|---|---|---|
| Edge TTL (seconds) | How long Kapsule CDN holds content before fetching from your origin | 3600 (1 hr) |
| Browser TTL (seconds) | How long visitors' browsers cache the content locally | 3600 (1 hr) |
Lower values mean fresher content but more load on your origin. Higher values mean better performance but staler content until purged.
Image optimisation
In the Image optimisation card, two settings are available:
- On-the-fly image optimisation, automatically resizes and compresses images on first request, then caches the result at the edge
- Serve WebP to supported browsers, detects browser support and delivers WebP format instead of JPEG/PNG, typically 25–35% smaller
Both are recommended for best page load performance.
Was this article helpful?
Back to Help Centre