> 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/screen-share-parameters/and-screensharecontenthint.md).

# \&screensharecontenthint

\=motion prioritizes screen-share frame rate; =detail prioritizes screen-share resolution

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

## Aliases

* `&sscontenthint`
* `&screensharecontenttype`
* `&sscontent`
* `&sshint`

## Options

Example: `&screensharecontenthint=detail`

<table><thead><tr><th width="177">Value</th><th>Description</th></tr></thead><tbody><tr><td><code>detail</code></td><td>will prioritize <strong>screen-share resolution</strong> over frame rate</td></tr><tr><td><code>motion</code></td><td>will prioritize <strong>screen-share frame rate</strong> over resolution</td></tr></tbody></table>

#### Additional value options

Depending on browser and version, there may be additional values you can pass, such as `text`. Please see the following link for possible options that your browser may offer:

<https://developer.mozilla.org/en-US/docs/Web/API/MediaStreamTrack/contentHint>

## Details

`&screensharecontenthint` can customize how you want VDO.Ninja to balance screen-share resolution vs screen-share frame rate, specifically when bitrate or CPU is insufficient to offer both at the same time.

The two options are `detail` or `motion`. Screen-shares generally tend towards `detail` by default, and camera sources are tend towards `motion` by default. `detail` will try to prioritize resolution over frame rate, so the frame rate may drop a lot used. `motion` will try to maximize frame rate, but may drop the resolution a lot. There's no way to force both on as there's no magic bullet if your CPU or network cannot keep up.

For more information on how to lock or maximize the resolution of a video feed, please see the following guide:

{% content-ref url="/pages/UepoQ0H3m53bjP20oEbk" %}
[How to lock the resolution](/guides/how-do-i-lock-the-resolution.md)
{% endcontent-ref %}

There is [`&contenthint`](/advanced-settings/video-parameters/and-contenthint.md) if you want the parameter to affect all kinds of video sources. You can also use both, `&screensharecontenthint` will override [`&contenthint`](/advanced-settings/video-parameters/and-contenthint.md) for just screen-shares if set also.

{% hint style="info" %}
If using [`&codec=vp9`](/advanced-settings/video-parameters/codec.md) on the viewer side, the frame rate may drop as low as even 5-fps.
{% endhint %}

{% hint style="warning" %}
This parameter has been tested on Chrome, but other browsers may vary in behavior. Safari seems to just ignore things, for example.
{% endhint %}

## Related

{% content-ref url="/pages/tfc1VW7vBfTgxA4APhyG" %}
[\&contenthint](/advanced-settings/video-parameters/and-contenthint.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/screen-share-parameters/and-screensharecontenthint.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.