> 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/mixer-scene-parameters/and-forceviewerlandscape.md).

# \&forceviewerlandscape

Keeps all incoming videos oriented (rotated) so that the aspect ratio is always above 1

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

## Options

Example: `&forceviewerlandscape=90`

<table><thead><tr><th width="294">Value</th><th>Description</th></tr></thead><tbody><tr><td>(value in degrees)</td><td>value, how much the video is rotated in degree</td></tr><tr><td>(no value given)</td><td><code>270</code></td></tr><tr><td><code>180</code></td><td>locked upside down</td></tr></tbody></table>

## Details

`&forceviewerlandscape` keeps all **incoming** videos oriented (rotated) so that the [aspect ratio](/advanced-settings/video-parameters/and-aspectratio.md) is always above 1, so effectively, forces landscape mode.

ie: <https://vdo.ninja/?forceviewerlandscape&view=xxx>

This normally shouldn't be needed, as the sender side should control the orientation, but the native app seems to auto rotate back to portrait when the phone is locked. Until that is fixed, this can work around the issue I think, by rotating the video when it detects its been rotated.

The parameter can take a value, the default is `270`, which is how much the video is rotated. You might want to also use `90`, or in the case you want it to be locked upside down, you can technically pass `180` I guess?

## Related

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

{% content-ref url="/pages/yMDZE7PUcZjqAT6UYESz" %}
[\&forcelandscape](/advanced-settings/mobile-parameters/and-forcelandscape.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/mixer-scene-parameters/and-forceviewerlandscape.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.