> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/clear-web-browser-cache.md).

# Clear web browser cache

Clear the web browser cache in Remote Desktop Manager by renaming or deleting the EO.WebBrowser.Cache and WebView2.Cache folders.

By deleting a folder, you are able to clear the web browser cache in the application folder of Remote Desktop Manager. Go to ***File – Settings – Advanced*** and click the ***Information*** tab to access the application folder. If your Remote Desktop Manager is in **Program Files**, you should find the ***EO.WebBrowser.Cache*** and ***WebView2.Cache*** folders in the **localappdata**.

1. Close your Remote Desktop Manager application.
2. In the application folder, locate the ***EO.WebBrowser.Cache*** and ***WebView2.Cache*** folders. Depending on your Remote Desktop Manager version, you may only have one of those folders.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>If you do not find either of those folders, the folder where the configuration files are stored may have been changed using an <strong>override.cfg</strong> file. See <a href="/rdm/getting-started/installation/client/configuration-file-location.md#override-the-default-path">Configuration file location</a> for more information.</p></div>
3. Rename or delete the folder(s). The best practice is to rename the folders, as in this case you do not lose any data.
4. Restart Remote Desktop Manager.


---

# 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://docs.devolutions.net/rdm/knowledge-base/how-to-articles/clear-web-browser-cache.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.