# Purge and prefetch

After content changes, purge makes nodes drop old cache; prefetch pulls popular content to nodes ahead of time.

Go to Site Management › Purge & Prefetch.


## Purge
Nodes delete their cache and fetch from the origin again on the next visit.
- **URL purge**: enter full addresses, one per line; only those files are purged.
- **Directory purge**: enter a directory address; all cache under it is purged.

Use it when the origin content has changed and you don't want to wait for the cache to expire.

## Prefetch
Nodes pull content from the origin into the cache ahead of time, so the first visitor already gets a hit.
- **URL prefetch**: enter full addresses, one per line. Prefetching before releasing a large file or campaign page avoids an origin spike at launch.

:::tip
Before prefetching large files, make sure the origin has enough bandwidth; administrators can raise the prefetch timeout and per-node prefetch concurrency in the system settings.
:::

## Daily limits
Cache purge, prefetch, unlock and log download each have a daily limit set by the administrator. Over the limit you are asked to try later or contact the administrator.

:::warn
A purge sends the next wave of visits all the way to the origin. On large sites avoid frequent whole-directory purges and prefer URL purge.
:::

How long content is cached is decided by [cache rules](https://www-sa2.kuxitong.com/en/guide/cache).