> For the complete documentation index, see [llms.txt](https://guide.prismlive.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.prismlive.com/desktop/guides/features/others/live-drawing-on-screen.md).

# Live Drawing on Screen

Windows, Mac

You can draw directly on the screen by activating the Drawing Mode icon on the sidebar.

Customize the brush size and color or use various shapes to decorate the screen. The drawing content appears on the LIVE screen in real time.

However, when Studio Mode is enabled, drawing content is only visible in the EDIT scene area. To display it on the actual LIVE screen, you need to click the **→** icon at the top of the screen to switch scenes.

Drawing content remains on the screen of its respective scene, even when switching between scenes.

<figure><img src="https://1019928184-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlISC5rfB4Hnmbsjf8phq%2Fuploads%2FF0yOZJAWxVCvj9E6x9fq%2FGroup%206.png?alt=media&amp;token=5df3a578-18a0-4d59-82af-807f342c1de4" alt=""><figcaption><p>Activate the <strong>Drawing Mode</strong> icon on the sidebar to draw on the screen.</p></figcaption></figure>

[Desktop](/desktop/overview.md), [Guides](/desktop/guides.md), [Features](/desktop/guides/features.md), [Others](/desktop/guides/features/others.md)


---

# 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://guide.prismlive.com/desktop/guides/features/others/live-drawing-on-screen.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.