> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/screen-recorder/record-and-capture/screen-recording/video-annotation.md).

# Video annotation

Draw on your screen during recording to highlight key details.

Draw on the page while recording to highlight a button, workflow, or area you want to explain.

## Annotate a recording

1. Open Screendesk and choose **Record Tab**, or set the record area to **Desktop** and choose **Record Desktop**.
2. Start recording and select **Draw** in the recording controls.
3. Draw on the page to highlight the area you want to explain.
4. End the recording, review it, and choose **Upload**.

Drawings fade after a few seconds. They are added while recording; you cannot add them to the recorded video afterward.

For desktop recording, page annotations are only visible in the saved video when that page is part of the surface you selected. They do not draw over other desktop applications.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.screendesk.io/screen-recorder/record-and-capture/screen-recording/video-annotation.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 `build a script that syncs our docs to a CMS` 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.