> For the complete documentation index, see [llms.txt](https://docs.vdo.ninja/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vdo.ninja/advanced-settings/screen-share-parameters/and-screensharehide.md).

# \&screensharehide

Hides the publisher's local screen-share preview window when screen sharing in a room

Sender-Side Option! ([`&push`](/advanced-settings/setup-parameters/push.md))

## Aliases

* `&sshide`
* `&hidescreenshare`
* `&hidess`

## Details

This hides the publisher's local screen-share preview window that appears when screen sharing in a room. You can use this if you want to screen share in a room, but you don't want to see your own screen share.

This does not hide incoming screen shares on viewer or scene links. To prevent a scene or viewer from loading remote screen shares, use [`&noscreenshare`](/advanced-settings/screen-share-parameters/and-noscreenshare.md).

Using [`&screensharetype=3`](/advanced-settings/screen-share-parameters/and-screensharetype.md) also hides the local screen-share window.

## Example

```
https://vdo.ninja/?room=ROOMNAME&screenshare&hidescreenshare
```

This lets the publisher screen share into the room without showing their own local screen-share preview.

## Related

{% content-ref url="/pages/-M\_oRQSkAJFpidl8B7xd" %}
[\&screenshare](/advanced-settings/setup-parameters/screenshare.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MZXcdoEcsFtTudaolWn" %}
[\&screenshareid](/advanced-settings/screen-share-parameters/screenshareid.md)
{% endcontent-ref %}

{% content-ref url="/pages/CGcri2JHEp7BuaSi6gXN" %}
[\&screensharetype](/advanced-settings/screen-share-parameters/and-screensharetype.md)
{% endcontent-ref %}

{% content-ref url="/pages/Pu9zYqvWHZ1WXWEOxi37" %}
[\&noscreenshare](/advanced-settings/screen-share-parameters/and-noscreenshare.md)
{% endcontent-ref %}


---

# 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.vdo.ninja/advanced-settings/screen-share-parameters/and-screensharehide.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.