> 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/screenshareid.md).

# \&screenshareid

Pre-sets the screenshare stream id for a screen share if its a secondary stream

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

## Aliases

* `&ssid`

## Options

Example: `&screenshareid=SomeID`

<table><thead><tr><th width="180">Value</th><th>Description</th></tr></thead><tbody><tr><td>(no value given)</td><td>If no value is passed, the system will automatically add the suffix of "_ss" to the existing stream ID that the user might be using.</td></tr><tr><td>(string)</td><td>Pre-sets the screenshare ID. Useful to automate or prepare stuff in advance.</td></tr></tbody></table>

## Details

When screen sharing as a guest in a group room, in `&sstype=2` screen sharing mode, the screen share will now create a second stream for the screen share, keeping your webcam also.

`&screenshareid` will preset the ID the screen share will have, making the stream ID for the screen share easier to predict and prep for.

Example (`&room=roomname&sstype=2&push=streamid&screenshareid`)\
![](https://2943598173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZHXv1G8N0MDxwotaT9%2Fuploads%2FfPIA3g0newqo5X0ToCCk%2Fimage.png?alt=media\&token=e418295c-ce05-4a3d-a95d-b44ef1bbd092)

Without this, the screen share ID in `&sstype=2` mode is random, which is a decision made to increase security. This complication will be addressed in the future.

There is a toggle in the director's room which adds `&ssid` to the guest's invite link.\
![](https://2943598173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZHXv1G8N0MDxwotaT9%2Fuploads%2FifHsyYl9oIn1gi1Kkz8R%2Fimage.png?alt=media\&token=fb1e3e27-3570-40f9-ac13-909289142ccb)

{% hint style="info" %}
`&screenshareid` doesn't work with [`&screensharetype=3`](/advanced-settings/screen-share-parameters/and-screensharetype.md). When using `&screensharetype=3` the screen share gets the appendix `:s` added to the stream ID of the guest.\
\
As of VDO.Ninja [v23](/releases/v23.md),`&screensharetype=3` is default, but you can revert back to `&screensharetype=2` or use the new `&screensharetype=3` method post-fix `:s` method of identify screen shares.
{% endhint %}

## Related

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

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

{% content-ref url="/pages/-MbrBM0\_6rweLjhZuPpP" %}
[\&screensharequality](/advanced-settings/screen-share-parameters/screensharequality.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/screenshareid.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.