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

# \&dpi

Overrides the automatically selected Device Pixel Ratio

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

## Aliases

* `&dpr`

## Options

Example: `&dpi=2`

| Value             | Description                 |
| ----------------- | --------------------------- |
| `1`               | Set Device Pixel Ratio to 1 |
| `2`               | Set Device Pixel Ratio to 2 |
| `3`               | Set Device Pixel Ratio to 3 |
| (integer value X) | Set Device Pixel Ratio to X |

## Details

This allows a user to override the automatically selected Device Pixel Ratio value. It is often either 1 or 2 by default, depending on your display's DPI setting.

An accurate DPI value is important for calculating the correct requested resolution of a video. For high density displays, you'll want to have a higher resolution of video, especially in the case of the Electron Capture app, where the reported resolution isn't the same as the displayed resolution.

Changing this value can provide for higher quality or lower quality video on playback, a bit like changing the [`&scale`](/advanced-settings/video-parameters/scale.md) value, but dynamic to the current window-size of the video being played back.

## Related

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

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

{% content-ref url="/pages/-MZdvi1ReqWtZ6G80iMX" %}
[\&scale](/advanced-settings/video-parameters/scale.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/video-parameters/dpi.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.