> 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/how-to-purge.md).

# How to Purge

Learn how to invalidate cached content instantly across all Medianova CDN

Purge selected cached files from a CDN Resource before their configured cache TTL expires.

You can perform purge operations from the [Medianova Control Panel](https://cloud.medianova.com) or via the API.

## Purge Cached Files

{% stepper %}
{% step %}

### Open Purge

Open the CDN Resource and select **Purge**.

The **Purge files** section provides the path field used to specify cached content for invalidation.
{% endstep %}

{% step %}

### Enter the Paths

Enter the paths of the cached files you want to purge.

Each path must:

* Start with `/`.
* Exclude the domain.
* Contain no spaces.

For example:

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

To purge multiple paths, enter one path per line or separate the paths with commas.
{% endstep %}

{% step %}

### Purge the Files

Click **Purge files** to submit the purge request.

The specified cached objects are invalidated. Subsequent requests retrieve the content again according to the CDN Resource's caching and source configuration.
{% endstep %}
{% endstepper %}

## Check Purge Results

The **Recent** section lists purge operations for the selected CDN Resource and shows the result of each submitted path.

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

{% hint style="info" %}
A purge invalidates cached content. It does not delete or modify the corresponding content at the source.
{% endhint %}

## Related Concepts

* [Purge](/products/performance-cdn/static-content-delivery/advanced-configuration/purge.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/how-to-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.