> 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/design-parameters/and-rotate.md).
# \&rotate
Rotates the camera
Sender-Side Option! ([`&push`](/advanced-settings/setup-parameters/push.md))
## Options
Example: `&rotate=180`
Value
Description
(no value given) | 90
90 degree
(degree)
Rotates the camera in the specified value in degree
## Details
Applies to the publisher's side. Rotates the camera 90-deg by default, or specify `&rotate=180` or `&rotate=270` to rotate more.
Rotates your video for the guests/OBS as well. The rotation uses CSS.
{% hint style="warning" %}
CSS-based video effects will not work in full-screen mode. As well, the control-bar gets rotated with the video, when using CSS.
{% endhint %}
#### If looking to flip or mirror a video instead:
If you are looking for a form of mirroring and flipping that changes the actual video, rather than relying on CSS to achieve the effect, you can check out the sender-side [`&effects`](/advanced-settings/video-parameters/effects.md) options.\
\
`https://vdo.ninja/beta/?effects=-1`, which will flip the video `https://vdo.ninja/beta/?effects=-2`, which will flip and mirror the video\
`https://vdo.ninja/beta/?effects=2`, which will mirror the video\
\
Effects however may increase CPU/GPU usage, and could cause frame rate instability, especially if the browser tab is not in active focus.
There's also the [`&flip`](/advanced-settings/design-parameters/and-flip.md) and [`&mirror`](/advanced-settings/design-parameters/and-mirror.md) options, which use CSS, but are generally viewer-side only.
### Dedicated teleprompter tool that works for most sites
There's a dedicated tool for mirror, flipping, and rotating websites as part of VDO.Ninja as well:
In case the built-in options to mirror or flip don't work, the teleprompter app might be a good alternative.
## Related
{% content-ref url="/pages/-MZNW\_b8VrHaY-eDBYyk" %}
[\&effects](/advanced-settings/video-parameters/effects.md)
{% endcontent-ref %}
{% content-ref url="/pages/-MZNXXRU5WeDRWuoN6mB" %}
[\&flip](/advanced-settings/design-parameters/and-flip.md)
{% endcontent-ref %}
{% content-ref url="/pages/-MZOMNvQPrR\_E5e5Zxxd" %}
[\&mirror](/advanced-settings/design-parameters/and-mirror.md)
{% endcontent-ref %}
{% content-ref url="/pages/uvXdWOSj8ojhE7avv54e" %}
[\&rotatewindow](/advanced-settings/design-parameters/and-rotatewindow.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/design-parameters/and-rotate.md?ask=&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.