> For the complete documentation index, see [llms.txt](https://docs.strongdm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.strongdm.com/references/cli/replay/rdp.md).

# sdm replay rdp

```shell
NAME:
   sdm replay rdp - render an RDP session in movie format from local or remote RDP session logs

USAGE:
   Render from local relay logs:
   sdm replay rdp r2tVQUuoNefeUF66r5OcfV4cCAGX

   Render from local relay logs in CSV format:
   sdm replay rdp --format csv r2tVQUuoNefeUF66r5OcfV4cCAGX

   Render from local relay logs in CSV format encrypted with a public key:
   sdm replay rdp --format csv --key local-log.key r2tVQUuoNefeUF66r5OcfV4cCAGX

   Render from specified local relay log files:
   sdm replay rdp r2tVQUuoNefeUF66r5OcfV4cCAGX logs/relay.1740434641.0.log logs/relay.1740434761.0.log

   Render from downloaded remote logs:
   sdm replay rdp --tmpdir out --download r2tVQUuoNefeUF66r5OcfV4cCAGX

   Render from downloaded remote logs encrypted with a public key:
   sdm replay rdp --tmpdir out --download --key remote-log.key r2tVQUuoNefeUF66r5OcfV4cCAGX

OPTIONS:
   --format value            file format of local relay log files ('json', 'csv', or 'logstream') (default: "json")
   --tmpdir value, -t value  path to directory for temporary storage during rendering. Longer sessions may require more temporary space (default: "/Users/youruser/.sdm/logs")
   --download                download remote session logs from StrongDM instead of using local relay logs
   --key value, -k value     path to organization private key file. Required to decrypt logs encrypted with public key encryption
```


---

# 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.strongdm.com/references/cli/replay/rdp.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.