> 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-screensharetype.md).

# \&screensharetype

Defines how webcam and screenshare of a guest in a room interacts which each other

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

## Aliases

* `&sstype`

## Options

Example: `&screensharetype=3`

<table><thead><tr><th width="196">Value</th><th>Description</th></tr></thead><tbody><tr><td><code>1</code></td><td>Replaces the webcam screen with the screen share</td></tr><tr><td><code>2</code></td><td>Creates a totally new connection for the screen share</td></tr><tr><td><code>3</code> (default)</td><td>Reuses the existing connection, adding a second video track</td></tr></tbody></table>

## Details

This parameter can be used to specify which type of screen sharing logic is used.

* `screensharetype=1` replaces the webcam screen with the screen share
* `screensharetype=2` creates a totally new connection for the screen share
* `screensharetype=3` reuses the existing connection, adding a second video track; also doesn't show the local screen share window

The default `&screensharetype` for screen-sharing is `3` when in a room.

As a viewer or scene link, to specify only loading the `&screensharetype=3` screen share, you can now use `&view=xxxx:s`, where `:s` is appended to the end of the stream ID. This tells the system to ignore the webcam/mic feed, and just send over the screen share. You can do `&view=xxxx,xxxx:s` to target both webcam and screen share though. I may change this syntax over time, but for now it works. The solo-links in the director's room has this `:s` applied already where needed.

{% hint style="info" %}
If using `&screensharetype=3` the parameter [`&screenshareid`](/advanced-settings/screen-share-parameters/screenshareid.md) doesn't do anything.
{% endhint %}

{% hint style="warning" %}
The type-3 screen share is still not fully cooked for use in scenes, etc, and it won't yet\
work with [`&meshcast`](/advanced-settings/meshcast-parameters/and-meshcast.md), [`&novideo`](/advanced-settings/video-parameters/and-novideo.md) or [`&noaudio`](/advanced-settings/audio-parameters/noaudio.md).
{% endhint %}

## Related

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

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

{% content-ref url="/pages/-M\_oRQSkAJFpidl8B7xd" %}
[\&screenshare](/advanced-settings/setup-parameters/screenshare.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-screensharetype.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.