> For the complete documentation index, see [llms.txt](https://docs.arcware.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arcware.cloud/unreal-engine-setup/set-up-pixel-streaming-in-your-own-project/core-settings/camera-aspect-ratio.md).

# Camera Aspect Ratio

Set up Pixel Streaming in your own project - Core Settings

Disable aspect ratio constraints on your in-game cameras for a responsive web experience. \
To allow for the best user experience while streaming on a variety of different devices, we recommend unticking **’Constrain Aspect Ratio‘** on your cameras, this will allow your application to use the whole screen of the device and will allow for portrait screen orientations to work properly.&#x20;

* Firstly locate where your cameras are being used (your camera could be in your **Player Pawn** or a **Cinematic Camera** for movie sequences).&#x20;
* With the camera selected look in the '**Details'** panel for the option **‘Constrain Aspect Ratio‘** and disable it.

![( Example of a Player pawn with Camera Component )](https://451842398-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxeRHVvCMHTEw8OnxbYIg%2Fuploads%2FZUJicU4O43m548M43Uwz%2F4.Aspect_Ratio.jpg?alt=media\&token=37ed2cd2-cbe7-44f5-b095-8644ec7da42f)


---

# 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.arcware.cloud/unreal-engine-setup/set-up-pixel-streaming-in-your-own-project/core-settings/camera-aspect-ratio.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.
