> 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/guides/how-to-mirror-a-video-while-full-screen-for-ipads-and-teleprompters.md).

# How to mirror a video while Full-Screen - For iPads and Teleprompters

Mirror VDO.Ninja video in fullscreen for teleprompters and iPads using browser fullscreen and effects parameters.

To get a video to mirror while full-screened, you have a few options.

One is to just full screen the browser itself; F11 on most desktops. The video itself may not be fullscreen, but the browser will be and should be pretty close to perfect. Adding [`&hideheader`](/advanced-settings/design-parameters/and-hideheader.md) can hide any menu bars, if there are any.

Another option that is undergoing experimental testing as of Sept 23rd 2020 is to use the [`&effects`](/advanced-settings/video-parameters/effects.md) option, with `&effects=2` applying a mirrored effect to the video before publishing the video.

**Push Link**\
<https://vdo.ninja/?push=SOMESTREAMID&effects=2>

**View Link**\
<https://vdo.ninja/?view=SOMESTREAMID>

So by adding `&effects=2`, the video will be mirrored in a way that can be full screened. There are some limitations with this approach still, but I'm curious to get your feedback.


---

# 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/guides/how-to-mirror-a-video-while-full-screen-for-ipads-and-teleprompters.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.