> For the complete documentation index, see [llms.txt](https://docs.pylenium.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pylenium.io/configuration/viewport.md).

# Viewport

## The Viewport Settings

Let's take a look at the default viewport settings inside of <mark style="color:orange;">**pylenium.json**</mark>

```javascript
"viewport": {
    "maximize": true,
    "width": 1440,
    "height": 900,
    "orientation": "portrait"
}
```

By default, Pylenium will open each browser window in "maximized mode", meaning that the browser window will take up the entire screen that it's running on.

{% hint style="info" %}
With <mark style="color:purple;">`"maximize": true`</mark>, Pylenium ignores the <mark style="color:yellow;">`width`</mark>, <mark style="color:yellow;">`height`</mark>, and <mark style="color:yellow;">`orientation`</mark> values
{% endhint %}

### maximize

* <mark style="color:purple;">`true`</mark> (default) - The browser window will take up the entire screen
* <mark style="color:purple;">`false`</mark> - Use the <mark style="color:yellow;">`width`</mark>, <mark style="color:yellow;">`height`</mark>, and <mark style="color:yellow;">`orientation`</mark> values to set the brower window dimensions

### width & height

These are useful if you want all tests to use the same dimensions instead of dynamically changing to the current screen. For example, running tests locally will probably be different than when running them in your Continuous Integration pipeline.

{% hint style="success" %}
Another useful scenario is for testing your website on different mobile device sizes!
{% endhint %}

{% hint style="info" %}
Make sure <mark style="color:purple;">maximize</mark> is set to <mark style="color:yellow;">`false`</mark>
{% endhint %}

### orientation

* <mark style="color:purple;">`"portrait"`</mark> (default)
* <mark style="color:purple;">`"landscape"`</mark>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pylenium.io/configuration/viewport.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.