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

# \&password

Sets a password to view a stream or to join a room

General Option! ([`&push`](/advanced-settings/setup-parameters/push.md), [`&room`](/advanced-settings/setup-parameters/room.md), [`&view`](/advanced-settings/mixer-scene-parameters/view.md), [`&director`](/advanced-settings/director-parameters/director.md))

## Aliases

* `&pass`
* `&pw`
* `&p`

## Options

Example: `&password=PASSWORD123`

<table><thead><tr><th width="335">Value</th><th>Description</th></tr></thead><tbody><tr><td>(no value given)</td><td>prompts you to select a password</td></tr><tr><td>(string)</td><td>1 to 49-characters long: aLphaNumEric-characters; case sensitive.</td></tr></tbody></table>

## Details

To make your stream or your room more secure, you can set a password by adding `&password=xxx` to the URL.

If no password value is provided via the URL parameter, the system will prompt for one when connecting.

![](https://2943598173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZHXv1G8N0MDxwotaT9%2Fuploads%2FCDBJmkNdnrNHtf410ZJo%2Fimage.png?alt=media\&token=4b4c8714-7497-4a76-aad3-215d36d23799)

You will want to add the password value to the URL if loading it into OBS.

Passwords apply to both Stream IDs and Room IDs.

Please use alphanumeric-characters only; spaces or other characters may cause the mechanism to fail.

{% hint style="info" %}
**Passwords are CASE-SENSITIVE**; mobile users should watch-out for auto-capitalization when entering them.
{% endhint %}

### Hiding passwords from server logs

For additional security, you can place the password in the URL **fragment** (after `#`) instead of the query string (after `?`). Fragment parameters are never sent to the server, keeping them hidden from Cloudflare logs:

```
https://vdo.ninja/?push=cam1#p=mysecretpassword
```

You can combine this with a hash fallback in case the fragment is stripped during URL sharing:

```
https://vdo.ninja/?push=cam1&hash=99e5#p=secret
```

If the fragment survives, `p=secret` is used directly. If stripped, the user is prompted to enter a password, which is then validated against `&hash`.

See [Fragment URL Parameters](/help/privacy-and-security-details/fragment-url-parameters.md) for more details.

### Using hashed passwords

Adding [`&hash=HASH_VALUE`](/advanced-settings/setup-parameters/and-hash.md) will act as if `&password=PASSWORD` was added.

The hash is generated from `password + salt` (salt defaults to the room name). Hash values can be 1-6 characters; shorter hashes are more secure (reveal less about the password) but more prone to false positives.

Use this link to get the hash for the password:\
<https://vdo.ninja/examples/changepass.html>

## Related

{% content-ref url="/pages/8VzuOc77WqZCOW0ZjYo7" %}
[Fragment URL Parameters](/help/privacy-and-security-details/fragment-url-parameters.md)
{% endcontent-ref %}

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

{% content-ref url="/pages/-Mexvq3U-JCKAdT6HTu-" %}
[\&codirector](/advanced-settings/director-parameters/codirector.md)
{% endcontent-ref %}

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

{% content-ref url="/pages/uEw7h7CepYSD34hobf7B" %}
[\&maindirectorpassword](/advanced-settings/director-parameters/and-maindirectorpassword.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-password.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.