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

# \&webcam

Disables screen-sharing as an option

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

## Aliases

* `&wc`

## Details

Automatically selects the Share your Camera option and hides the screen-share button in the control bar.\
![](https://2943598173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZHXv1G8N0MDxwotaT9%2Fuploads%2FZQJwL86X7xwuOuS7BoEb%2Fimage.png?alt=media\&token=82d5d8bd-c340-48b3-a5ba-dcb844f3860a)

{% hint style="danger" %}
Do not use while on a director page to autostart a camera; `&autostart&vd=video_device` should handle that.
{% endhint %}

If you would still like the guest to have access to the screen-sharing button once they have joined the call, you can force it to appear with the [`&ssb`](/advanced-settings/buttons-and-control-bar-parameters/and-screensharebutton.md) option. The [`&webcam`](/advanced-settings/setup-parameters/and-webcam.md) option by default will hide the screen-share button otherwise.

Starting with [v19](/releases/v19.md) of VDO.Ninja, there is also the [`&webcam2`](/advanced-settings/setup-parameters/and-webcam2.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 webcam.

## Related

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

{% content-ref url="/pages/XueNVvQLR9l3bCQjn5bh" %}
[\&webcam2](/advanced-settings/setup-parameters/and-webcam2.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/setup-parameters/and-webcam.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.