Purging & Browsing the Cache

When you change your site, nsin may still be serving the saved copy it made earlier. Purging tells nsin to throw that copy away so the next visitor gets the fresh version.

You’ll find all of this in the Caching section of your domain.

Purge everything

The simplest option: clear every cached copy for the domain.

1. Open Caching.
2. Click Purge everything.
3. Confirm.

Big sites can hold a lot of cached items, so the sweep runs in the background — the panel tells you it was queued, and the count settles a few seconds later.

Caution

After a full purge, the next visitor to each page waits for your server instead of getting an instant cached copy. For a small change, purge just that page.

Purge one page or file

1. Open Caching → the Cached items list.
2. Find the row you want (see filtering below).
3. Choose Purge on that row.

Delete or refresh?

Every purge has two modes:

Mode	What happens
Delete	The copy is removed and the row disappears from the list. The next visitor causes a fresh fetch from your server.
Refresh	The stored copy is dropped but the item stays listed. The next visitor re-fills it. Use this when you want the item to stay cached, just with new content.

Browse what’s cached

The Cached items list shows each stored object with:

• the host and path the visitor requested,
• its size,
• the edge location that stored it,
• when it was cached and when it expires.

You can filter by host, path (/assets/* works), or edge location, and sort by size, date or path. The totals above the list show how many items are stored and how much space they take, broken down per location.

Tip

Sort by size to find the handful of large files eating most of your cache space, or filter by path to check that a section of your site is being cached at all.

Developer mode

While you’re actively working on the site, purging after every change gets tedious. Developer mode temporarily bypasses the cache for the whole domain, so you always see what your server just produced.

1. Open the domain’s settings.
2. Turn on Developer mode.

It switches itself off automatically after a short period, so you can’t leave your site uncached by accident. Turn it off yourself when you’re done.

Common questions

I purged but still see the old page. Your own browser also caches. Try a private/incognito window, or a hard reload.

Do I need to purge after every deploy? Only for files whose contents changed under the same address. Files with a version in their name (app.4f3c1.js) never need purging — a new name is a new cache entry.

Which pages are being cached in the first place? That’s decided by your cache rules. The caching overview explains the defaults.