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

# \&sharper

Should 'up to' double the amount of playback video resolution

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

## Aliases

* `&sharpen`
* [`&dpi=2`](/advanced-settings/video-parameters/dpi.md)

## Details

`&sharper` is now an alias of [`&dpi=2`](/advanced-settings/video-parameters/dpi.md), which should 'up to' double the amount of playback video resolution, if the dynamic resolution optimization is enabled at least, in certain cases. This is a lot like [`&scale=100`](/advanced-settings/video-parameters/scale.md), but perhaps *slightly* more efficient in some cases. This is mainly for when you intend to have a large screen-share in a scene, where you don't want the tiny guest videos to be a 100% scale, but 50% scale is fine (up from 25% scale). [`&dpi`](/advanced-settings/video-parameters/dpi.md) already exists on production, but by adding these aliases, I hope it's more discoverable.

As an alternative to `&sharper`, I've also added [`&sharperscreen`](/advanced-settings/screen-share-parameters/and-sharperscreen.md), which sets [`&scale=100`](/advanced-settings/video-parameters/scale.md), but *only* for screen-shares (virtual cameras not included). This is probably even more efficient than [`&scale=100`](/advanced-settings/video-parameters/scale.md) or `&sharper`, and it's designed for when screen-sharing a lot of text. Text looks a bit soft when streaming video at 1:1 pixel resolution.

It's recommended to only use these parameters within the context of a scene link, and not on guest links, due to the higher CPU / bandwidth it may use.

## Related

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

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