Purging the cache

Refreshing an image after you change it

CDN.MN caches the optimized copy of each image. When you replace an image at your origin but keep the same path, purge it so the next request re-pulls the new version.

When you need to purge

• You replaced an image at your origin but kept the same URL/path.

You do not need to purge to add new images or request new sizes — a path or parameter we haven’t seen is simply pulled and cached on first request.

You also don’t need to purge after changing a site’s optimization settings (quality, width list, or format toggles): those values are part of the cache identity, so new settings produce fresh variants on the next requests automatically, and the old ones fall out of the cache on their own.

How to purge

From your site in the dashboard, choose the scope that fits:

• A single image — purge one path. Available on every plan.
• A folder (prefix) — purge everything under a path prefix. Paid plans.
• The whole site — purge every cached image for the site. Paid plans.

A purge removes the cached variants for that scope. The next request for each image re-pulls the current original and re-optimizes it — so the first request after a purge is a cache miss, and the ones after are hits again.

Rate limits

Purges are rate-limited per site so an automated loop can’t turn purge-then-refetch into constant origin traffic. Folder and whole-site purges have a lower hourly limit than single-image purges, since each one clears far more. If you hit a limit, wait and retry, or purge a narrower scope.

Good practice

• Prefer a new path or filename for a genuinely new asset (e.g.hero-v2.jpg) — then there’s nothing to purge, and old links keep working.
• Purge the narrowest scope that covers your change — a whole-site purge is rarely needed.

Something not updating as expected? See Troubleshooting.