> 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-locked.md).
# \&locked
Will force a the VDO.Ninja's mixer output keep the mixed render contained to a specific aspect-ratio, regardless of the browser's window size
Viewer-Side Option! ([`&scene`](/advanced-settings/mixer-scene-parameters/scene.md))
## Options
Example: `&locked=portrait`
Value
Description
landscape | (no value given)
16:9 aspect ratio
portrait
9:16 aspect ratio
square
1:1 aspect ratio
1.77777
aspect ratio
## Details
`&locked` will force a the VDO.Ninja's mixer output keep the mixed render contained to a specific aspect-ratio, regardless of the browser's window size. (as seen in photo)\
You'll get black bars (or whatever the background color is) as padding on the sides to force the inner video elements into the desired aspect ratio
When using `&locked`, the default aspect ratio is 16:9, but you can pass a floating point value for different aspect ratios, or use `landscape` (instead of `1.77777`) / `portrait` / `square` as presets if needed.
Padding is centered, so the rendered video will be in the center of the screen. (tho using [`&widget`](/advanced-settings/settings-parameters/and-widget.md) mode might break things though).
This `&locked` option is added to the [Mixer App](/steves-helper-apps/mixer-app.md)'s WHIP/**Twitch publishing output option**, so regardless of window size, you'll get a 16:9 video render.
## Related
{% content-ref url="/pages/9cz57gsDjoS4UT6rIXEj" %}
[\&structure](/advanced-settings/design-parameters/and-structure.md)
{% endcontent-ref %}
{% content-ref url="/pages/3SOPDc5TkuiOpThaDHMN" %}
[\&aspectratio](/advanced-settings/video-parameters/and-aspectratio.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-locked.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.