> 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/whip-parameters/and-whepshare.md).

# \&whepshare

Share an external WHEP source to viewers

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

## Aliases

* `&whepsrc`

## Options

Example:

`&whepshare=https%3A%2F%2Fwhep.example.com%2Fpath` or prompt without a value

| Value | Description                   |
| ----- | ----------------------------- |
| URL   | WHEP source endpoint to share |

## Details

* Instead of sending your local camera/mic, instructs viewers to fetch and play the specified WHEP endpoint as your published media.
* Use with [`&whepsharetoken`](/advanced-settings/whip-parameters/and-whepsharetoken.md) if the WHEP source requires a bearer token.
* If no value is provided, you’ll be prompted to enter the WHEP URL on join.
* WHEP URLs must be `https://`, except `http://localhost` for local testing.
* If the URL is invalid, it is ignored and a warning is shown.
* In non-clean layouts, a small WHEP status card appears with copy/open actions and can be dismissed.
* Use with `&dataonly` when you want to advertise an external WHEP feed without publishing local camera/mic.
* `&nowhep` / `&nomeshcast` disables advertising the WHEP URL to peers.
* Use [`&autowhep`](/advanced-settings/whip-parameters/and-autowhep.md) when you want VDO.Ninja to try deriving this WHEP URL from a configured WHIP output URL.

## Related

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

{% content-ref url="/pages/X7sqFepAc8lYZLoLcTi4" %}
[\&whepsharetoken](/advanced-settings/whip-parameters/and-whepsharetoken.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/whip-parameters/and-whepshare.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.