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

# \&aligntop

Align video holders to the top of their containers

Add `&aligntop` to the viewing page's URL to place the video at the top when a landscape source is displayed in a portrait window. The unused space appears below the video.

## Example

`https://vdo.ninja/?view=STREAMID&aligntop`

Replace `STREAMID` with the stream ID you want to view. This is useful for a 16:9 presentation viewed on a portrait phone or digital display.

## Details

The option applies this CSS to every video holder on that page:

```css
.holder {
    top: 0 !important;
}
```

It changes the local page layout, not the transmitted video. It overrides each holder's normal top offset, so use it where that placement is wanted for all videos on the page.

No value is required. Remove `&aligntop` to restore the normal layout; `&aligntop=0` still enables it because the option checks only whether the parameter is present.

On versions without this option, the same rule can be supplied through [`&base64css` / `&cssb64`](/advanced-settings/design-parameters/and-base64css.md).


---

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