> 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/server/knowledge-base/how-to-articles/download-or-view-a-recording-session.md).

# Download or view a recording session

Download or view Devolutions Server WebM session recordings using Remote Desktop Manager or the Devolutions Server web interface entry logs.

It is possible to download Devolutions Server WebM recordings using Remote Desktop Manager. However the Devolutions Server web interface only lets you view the recording.

{% hint style="info" %}
Make certain the [***Recording server*** ](/server/knowledge-base/how-to-articles/configure-recording-server.md)is already configured correctly. The topic also has the complete list of recording types that are supported with the ***Recording server***.
{% endhint %}

### Remote Desktop Manager

Ensure that Remote Desktop Manager has access to the correct Devolutions Server workspace.

1. Navigate to the vault where the entry is and click on that entry.
2. Click on the ***Logs*** tab in the ***Dashboard***.
3. Click on the ***Recording*** button to download it.
4. Choose where to save the recording and click ***Save***.

### Devolutions Server web interface

1. In Devolutions Server web, navigate to the vault where the entry is and click on that entry.
2. Click on the ***Logs*** tab.
3. Click on the play button to view the recording.


---

# 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/server/knowledge-base/how-to-articles/download-or-view-a-recording-session.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.