> 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/setup-parameters/screenshare.md).

# \&screenshare

Disables camera-sharing as an option

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

## Aliases

* `&ss`

## Details

`&screenshare` will allow the guest to screen share by being directly asked to share a screen or window instead of being taken to the camera/screenshare selection screen.\
![](https://2943598173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZHXv1G8N0MDxwotaT9%2Fuploads%2FnFPkAP5OE77eSpzjTPYL%2Fimage.png?alt=media\&token=6fe60c9b-0d76-4216-889e-7d2adc52895c)

Starting with [v19](/releases/v19.md) of VDO.Ninja, there is also the [`&screenshare2`](/advanced-settings/setup-parameters/and-screenshare2.md) option; a minor UI variant that requires an additional button press, but more clearly preps the guest to the fact they will be sharing their screen.

#### Using `&screenshare` with the [Electron Capture App](/steves-helper-apps/electron-capture.md)

When using the Electron Capture App you have to "Elevate Privileges" to be able to share a window or screen. You can enable Elevated Privileges for the Electron App via the command line with `--node true` or in the app by right-clicking and selecting "Elevate Privileges" from the context-menu.

One unique feature about the [Electron Capture App](/steves-helper-apps/electron-capture.md) is that it can auto-select a screen or window when screen-sharing with VDO.Ninja, without user-input.\
For example:\
`&screenshare=1` for the main display\
`&screenshare=2` for the second display\
`&screenshare=discord` for the Discord application\
`&screenshare=googlechrome` for the Chrome Browser

## Related

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

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

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

{% embed url="<https://github.com/steveseguin/electroncapture>" %}


---

# 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/setup-parameters/screenshare.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.