> For the complete documentation index, see [llms.txt](https://weekerp.gitbook.io/image/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://weekerp.gitbook.io/image/resources/cache.md).

# Caching

#### **Caching Policy**

Weekerp CDN caches transformed images for **up to one year** after the first request.\
When the same request (same URL and parameters) is repeated,\
the cached image is instantly served to maximize delivery speed.

***

#### Cache Duration

* Transformed images are stored on CDN edge servers for **up to 1 year**.
* The same combination of **URL and parameters** always references the same cache.
* After expiration, the first subsequent request automatically regenerates and updates the cache.

***

#### Cache Key Criteria

Cache entries are distinguished based on the **entire request path + parameters**.\
For example, the following two requests generate **separate cache entries**:

```
/image/cat.jpg?w=800
/image/cat.jpg?w=800&fit=cover
```

***

#### Cache Purge

Currently, **no official cache purge feature** is provided.\
However, if you urgently need to remove cached content, please contact [Need Help?](/image/getting-started/support.md)

***

#### Versioning (Recommended)

Instead of manually purging cache,\
you can append a **version parameter (`v`)** to the image URL\
to achieve the same effect safely and instantly.

```
/image/cat.jpg?w=800&v=2
```

Changing the `v` value creates a **completely new cache entry**,\
allowing the latest image to be served immediately without touching existing caches.

💡 **Tip:**\
Use a **timestamp** or **build version** for the `v` parameter\
to safely refresh caches on every new release.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://weekerp.gitbook.io/image/resources/cache.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.