# Fragment URL Parameters

## Overview

VDO.Ninja supports placing URL parameters in the **fragment** portion of the URL (after `#`) instead of the query string (after `?`). Parameters placed in the fragment are never sent to the server, keeping them hidden from Cloudflare and other intermediaries. This works for any parameter: passwords, stream IDs, room names, tokens, and more.

## How It Works

When you load a URL, your browser sends the query string (`?param=value`) to the server, but the fragment (`#param=value`) stays entirely client-side. This means:

| URL Format            | Server Visibility                          |
| --------------------- | ------------------------------------------ |
| `?push=cam1&p=secret` | Cloudflare sees `push=cam1` AND `p=secret` |
| `?push=cam1#p=secret` | Cloudflare sees only `push=cam1`           |

{% hint style="info" %}
Fragment parameters take **precedence** over query parameters. If the same parameter appears in both places, the fragment value is used.
{% endhint %}

## Use Cases

This works for **any URL parameter**, not just passwords. Stream IDs, room names, tokens, and any other parameter can be placed in the fragment.

### Hiding Passwords

Instead of:

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

Use:

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

### Hiding Stream IDs and Room Names

```
https://vdo.ninja/?view=streamid#room=secretroom
```

### Hiding Multiple Parameters

```
https://vdo.ninja/?push=cam1#p=secret&token=abc123&key=xyz
```

Multiple parameters can be placed after the `#`.

## Fallback Behavior

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

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

In this example:

* If the fragment survives URL sharing: `p=secret` is used directly
* If the fragment is stripped (some platforms do this): the user is prompted to enter a password, which is then validated against `&hash=99e5`

This keeps the real password hidden in the fragment while providing hash-based validation as a fallback.

## Limitations

### Screen Sharing Visibility

The fragment is still visible in the browser's address bar. If you share your screen showing the browser, the fragment values will be visible. Consider using [`&hash`](/advanced-settings/setup-parameters/and-hash.md) for passwords if screen sharing is a concern.

### URL Sharing

Some platforms and messaging apps may strip or modify the fragment portion when sharing URLs. Test your sharing workflow to ensure fragments are preserved.

## Technical Details

* Fragment parameters are parsed client-side using the same logic as query parameters
* Standard URL encoding applies (`%20` for spaces, etc.)
* Parameters can use `=` for values or be flags without values
* The same parameter aliases work (`&p`, `&pw`, `&pass`, `&password`)

## Related

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

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

{% content-ref url="<https://github.com/steveseguin/vdo.ninja/blob/gitbook/help/privacy-and-security-details/README.md>" %}
<https://github.com/steveseguin/vdo.ninja/blob/gitbook/help/privacy-and-security-details/README.md>
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.vdo.ninja/help/privacy-and-security-details/fragment-url-parameters.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.