> For the complete documentation index, see [llms.txt](https://clients.medianova.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clients.medianova.com/products/performance-cdn/static-content-delivery/advanced-configuration/purge.md).

# Purge

Instantly invalidate outdated cache entries across all Medianova CDN cache layers to ensure the latest content is delivered globally without waiting for TTL expiration.

**Purge** removes selected cached objects from CDN caches so that subsequent requests can retrieve the current content from the configured source.

Use Purge when cached content must be refreshed before its normal cache expiration time.

You can trigger purge operations from the [Medianova Control Panel](https://cloud.medianova.com) or via the [API](/api-documentation/performance-cdn/purge.md).

## How Purge Works

When you purge a cached path:

1. A purge request is submitted for the selected CDN Resource.
2. Cached objects matching the specified path are invalidated across the CDN.
3. The invalidated cached content is no longer served.
4. A subsequent request retrieves the content again according to the resource's caching and source configuration.

Purge changes the state of cached objects. It does not modify or delete the source content.

## When to Use Purge

Purge cached content when:

* An updated asset must be delivered before its existing cache TTL expires.
* Outdated content must no longer be served from CDN cache.
* Content has changed at the source while an older version remains cached.
* A deployment requires selected cached assets to be refreshed.

{% hint style="info" %}
Prefer purging only the affected paths. This limits unnecessary cache refills and additional requests to your source.
{% endhint %}

## Path Format

Enter paths without a domain and start each path with `/`.

For example:

```
/myimages/subfolder/image.png
```

Multiple paths can be submitted in the same purge operation. Enter one path per line or separate paths with commas.

## Recent Purges

The **Recent** section displays purge operations performed for the selected CDN Resource and the result of each path.

Use **Refresh** to retrieve the latest purge results.

## Related Concepts

* [How to Purge](/products/performance-cdn/static-content-delivery/advanced-configuration/purge/how-to-purge.md)
* [Edge Cache Expiration](/products/performance-cdn/static-content-delivery/advanced-configuration/caching/edge-cache-expiration.md)
* [Purge API](/api-documentation/performance-cdn/purge.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://clients.medianova.com/products/performance-cdn/static-content-delivery/advanced-configuration/purge.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.