Purging & Browsing the Cache

Purging clears nsin’s saved copy, so the next visitor gets a fresh version — in your domain’s Caching section.

Purge everything

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

Caution

Big sites take a few seconds; the panel marks it queued. After a full purge, each page’s next visitor waits for your server — for a small change, purge just that page.

Purge one page or file

1. Open Caching → Cached items, filter to find the row.
2. Click Purge.

Delete or refresh?

Mode	What happens
Delete	Removed, row gone, fresh fetch next visit.
Refresh	Copy dropped, row stays listed, next visit re-fills it — keeps it cached with new content.

Browse what’s cached

The Cached items list shows each object’s:

• host and path
• size
• edge location
• when it was cached and when it expires

Filter by host, path (/assets/* works), or edge location; sort by size, date or path. Totals show items and space per location.

Tip

Sort by size for the biggest files, or filter by path to check what’s cached.

Need the files? See Downloading Your Cached Files.

Developer mode

Developer mode bypasses the cache domain-wide, showing your server’s live output, errors included: a 5xx reaches the browser as-is, not nsin’s. See Custom Error Pages.

1. Open the domain’s dashboard.
2. Turn on Developer mode at the top.

It switches off automatically after three hours, so sites won’t stay uncached by accident.

Common questions

I purged but still see the old page. Your browser caches too — try a private window or a hard reload.

Do I need to purge after every deploy? Only for changed file contents at the same address — versioned filenames (app.4f3c1.js) never need it; new name, new entry.

Which pages get cached? Your cache rules decide; see the caching overview for defaults.