> 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/gateway/knowledge-base/knowledge-base-articles/devolutions-gateway-recording-path.md).

# Devolutions Gateway recording path

Reference guide to configuring the Devolutions Gateway session recording destination path in Devolutions Server Console or Linux.

This topic serves as a reference for general information on Devolutions Gateway recording.

{% hint style="info" %}
The recording format is WebM and the file size is around 15 kb/s, depending on compression.
{% endhint %}

The recording path can be set in the Devolutions Server Console only.

Here are some important considerations:

* If the new path is set to a network location, like a shared folder or a UNC path, be aware that this may impact network traffic, both incoming and outgoing.
* Confirm that the account operating the gateway service has the necessary permissions to access both the gateway files and the file share.

#### Devolutions Gateway recording destination path (Linux manual configuration)

1. Open the `gateway.json` file located in the Gateway installation folder using a text editor.
2. Add the following line to the JSON file: `"RecordingPath": "<destination folder>",`
3. Be sure to use double backslashes, as in the following example:`"RecordingPath": "C:\\Recordings",`
4. Restart the Devolutions Gateway service.


---

# 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/gateway/knowledge-base/knowledge-base-articles/devolutions-gateway-recording-path.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.