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

# \&leaveorientationflag

Reference for the \&leaveorientationflag URL parameter in VDO.Ninja including behavior examples and related options.

#### **Description**

Preserves the video orientation metadata in the WebRTC stream, preventing automatic orientation corrections.

#### **Sender-Side Option**

This parameter prevents VDO.Ninja from removing the 3GPP video orientation extension from the SDP.

#### **Usage**

* **`&leaveorientationflag`** - Preserves orientation metadata

#### **Examples**

```
https://vdo.ninja/?push=streamID&leaveorientationflag
https://vdo.ninja/?room=roomname&leaveorientationflag
```

#### **Technical Details**

* Preserves `a=extmap:3 urn:3gpp:video-orientation` in SDP
* By default, VDO.Ninja removes this flag
* Affects how video rotation is handled
* Important for certain mobile streaming scenarios

#### **What It Does**

When enabled:

* Raw orientation data is passed through
* Receiving applications handle rotation
* No automatic orientation correction
* Preserves original mobile device orientation

When disabled (default):

* VDO.Ninja handles orientation
* Automatic rotation for mobile sources
* Consistent orientation across platforms

#### **Use Cases**

* Custom applications that handle rotation
* Debugging orientation issues
* Preserving raw mobile video streams
* Integration with systems expecting orientation data

#### **Platform Considerations**

* **Mobile devices**: May affect portrait/landscape handling
* **Desktop**: Usually no visible effect
* **OBS**: May impact how mobile sources are displayed
* **Custom receivers**: Can read orientation metadata

#### **Notes**

* Advanced parameter for specific use cases
* Most users should use default behavior
* Can affect mobile video display
* Test thoroughly when enabling

#### **Related Parameters**

* [`&forcelandscape`](https://docs.vdo.ninja/advanced-settings/mobile-parameters/and-forcelandscape.md) - Forces landscape orientation
* [`&forceportrait`](https://docs.vdo.ninja/advanced-settings/mobile-parameters/and-forceportrait.md) - Forces portrait orientation
* [`&rotate`](https://docs.vdo.ninja/advanced-settings/design-parameters/and-rotate.md) - Rotates video display


---

# 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-leaveorientationflag.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.
