After you update content, stale caches on edge nodes don't disappear instantly. Purging lets you actively clear specified caches, so the next request fetches the latest content.
Purge vs prefetch
Purge is "clear the old": mark already-cached content on the edge as invalid, so the next request triggers an origin fetch for the new version. Prefetch is "prepare the new in advance": push content to the edge before peak traffic, avoiding a slow origin fetch on first access. They're often combined — after a major release, purge first, then prefetch.
URL purge
Submit a specific URL (such as https://www.example.com/logo.png) under "Cache purge" in the console to precisely clear that one file's cache. Good for when you changed only a few files and need them live immediately. You can submit multiple URLs at once.
Directory purge
Submit a directory prefix (such as https://www.example.com/static/) to clear all cached content under it. Good for batch asset updates, or when you're unsure exactly which files changed. Directory purge has a wider blast radius, so confirm the prefix scope is correct.
Timing and tips
- A purge usually reaches edge nodes within a short time, but full global effect still takes a little while.
- Hash-fingerprinted assets (such as
app.3f9c.js) become new on rename, often needing no purge. - Frequent whole-directory purges raise origin load; prefer URL purge when you can be precise.