> 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/video-parameters/and-quality.md).

# \&quality

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

## Aliases

* `&q`

## Options

Example: `&quality=0`

| Value                   | Description                                                               |
| ----------------------- | ------------------------------------------------------------------------- |
| `0` \| (no value given) | targets about 1920x1080, depending on hardware                            |
| `1`                     | targets about 1280x720, depending on hardware                             |
| `2`                     | targets about 640x360, depending on hardware                              |
| `-1` (device's default) | useful in allowing the screen share at the same resolution as the display |

## Details

Presets the target resolution for a guest. It is not strict and is less likely to give errors than explicit resolution requests.

If `&quality` is omitted entirely, VDO.Ninja selects an initial quality tier using the device type, available CPU cores, reported memory, and whether the guest is joining a room. The default is therefore not always 720p. The camera and browser determine the actual frame rate unless [`&fps`](/advanced-settings/video-parameters/and-fps.md) or [`&maxframerate`](/advanced-settings/video-parameters/and-maxframerate.md) is set.

Without using `&quality` on the URL a guest can change the "quality" when setting up the camera:\
![](/files/kpaGjL22DafphTffcCRN)

Use [`&width`](/advanced-settings/video-parameters/and-width.md) and [`&height`](/advanced-settings/video-parameters/and-height.md) to get a higher resolution than 1920x1080.

There is a toggle in the director's room guest's invite link customization which adds `&q`:\
![](/files/DyPihQj75PpCFNYzihPJ)

## Related

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

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

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

{% content-ref url="/pages/-MZXQf0lGejWaBjc-y-Q" %}
[\&height](/advanced-settings/video-parameters/and-height.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 dynamically by asking a question.

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

```
GET https://docs.vdo.ninja/advanced-settings/video-parameters/and-quality.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.