> For the complete documentation index, see [llms.txt](https://docs.bugbug.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugbug.io/workflow-tips/changing-the-test-screen-size.md).

# Changing the test screen size

Browser window size in BugBug tests: Desktop and Mobile sizes, changing them in project settings, choosing one per test, why there's no full screen or zoom, what Mobile does and doesn't emulate, and w

Every test runs in a browser window of a fixed size. Different sizes can show your website differently, for example a menu that collapses on smaller screens.

{% hint style="info" %}
**In short**

* A project has two sizes: **Desktop** (default 1366 × 786) and **Mobile** (default 500 × 750). Change them in **Project settings → Screen sizes**.
* Each test uses one of the two. Choose it when you create the test or in the test's settings.
* The size is the size of the whole browser window, not of the page area.
* There's no full screen, maximized window or zoom, by design: a fixed window size makes tests behave the same on every screen. To test a bigger screen, set a bigger **Desktop** size.
* **Mobile** only makes the window smaller. It doesn't emulate a phone.
  {% endhint %}

## Choose the screen size of a test

When you create a new test, choose **Desktop** or **Mobile** in the **Screen size** menu.

<figure><img src="https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FLwCSbznwjBpZC01N772o%2FNew%20test.png?alt=media&amp;token=a762bacf-e6bb-413a-9e25-f9cb7743b7dc" alt="Screen size menu when creating a new test"><figcaption><p>Choose the screen size when you create a test</p></figcaption></figure>

To change it later, open the test's menu, choose **Test settings** and change **Screen size**.

<figure><img src="https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FHm0tfu2847JtIZPd1tvS%2Ftest%20setting.png?alt=media&amp;token=47a45c71-362f-48e8-ba92-efb80179c2e5" alt="Test settings in the test menu"><figcaption><p>Open the test menu and choose Test settings</p></figcaption></figure>

<figure><img src="https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FDTuGlBa0RC6MMBrVZo9Z%2Ftest%20setting2.png?alt=media&amp;token=57305fdb-4a6a-4db5-a909-bd0b24824b53" alt="Screen size field in test settings"><figcaption><p>Choose Desktop or Mobile</p></figcaption></figure>

Desktop and mobile tests can be in the same project. See [Mobile version testing](https://docs.bugbug.io/workflow-tips/mobile-version-testing.md).

## Change the Desktop and Mobile sizes

The sizes are set for the whole project, in **Project settings → Screen sizes**. You can also open them with **Change default screen sizes** in the **Screen size** menu of a test.

<figure><img src="https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FhzqaMNmrwyXpiY7VaOlA%2Fproject%20setting.png?alt=media&amp;token=da3540bd-4be2-4358-ae90-1c6d71569559" alt="Screen sizes tab in project settings"><figcaption><p>Project settings, Screen sizes tab</p></figcaption></figure>

<figure><img src="https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FeS8Tk69NLY44ykMbLtRB%2Fproject%20setting2.png?alt=media&amp;token=6ae6c9f2-85d3-4e86-9c50-2628d601b5b0" alt="Change default screen sizes link in the Screen size menu"><figcaption><p>Quick link from the Screen size menu</p></figcaption></figure>

* **Minimum 500 px.** Width and height can't be smaller than 500 px, because of Chrome limitations.
* **Whole window.** The width and height are the size of the browser window, including the browser's toolbars, so the page area is a bit smaller.
* **Recording and runs.** The same size is used when you record and when the test runs, locally and in the cloud.
* **Two sizes per project.** A test can use only Desktop or Mobile. To test more sizes, duplicate the project and set other sizes there.

## Full screen and zoom

BugBug doesn't support full screen or a maximized window, by design. Their size depends on the screen of the computer, so the same test would see a different layout on a laptop, on a large monitor and in the cloud, and could pass on one and fail on another. That's why every test has a defined window size: the page looks the same in every run, and the test is deterministic.

BugBug always opens the test window in normal mode, at the size from project settings. On macOS, if Chrome opens the window in full screen, BugBug changes it back to the normal size.

There's no zoom setting for tests. To see more of the page, set a bigger **Desktop** size, for example 1920 × 1080.

## What Mobile does

**Mobile** opens a smaller window, so your site shows its layout for small screens. It doesn't emulate a phone: there are no touch events, and the browser keeps its normal user agent. If your site chooses the mobile version by the user agent, set a mobile **User agent** in [Project settings → Browser](https://docs.bugbug.io/preventing-failed-tests/project-settings.md#browser). It applies to all tests in the project.

## See the screen size of tests and runs

* The tests list has a **Screen** column with the size of each test. The icon is shown only when the project has tests with both sizes.

<figure><img src="https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FA9AjsJsyq71k5xHBk0eB%2FTest%20list.png?alt=media&amp;token=7ead6478-27e1-462c-b980-d2c5befdce80" alt="Screen column in the tests list"><figcaption><p>The icon is shown when tests use different screen sizes</p></figcaption></figure>

* **Runs history** shows the screen size of each run.

<figure><img src="https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FNM8n9hBleO8L39Sp9u0P%2Frun%20history.png?alt=media&amp;token=ba871b19-4e08-4082-ae37-e0b048f0b324" alt="Screen size in runs history"><figcaption></figcaption></figure>

## FAQ

<details>

<summary>Can tests run in full screen or in a maximized window?</summary>

No, by design. A full screen or maximized window has a different size on every computer, so the same test could behave differently. The window always opens in normal mode, at the **Desktop** or **Mobile** size from project settings, so every run sees the same layout. To test a bigger screen, set a bigger Desktop size.

</details>

<details>

<summary>Can I zoom the page in a test?</summary>

There's no zoom setting. Change the window size in **Project settings → Screen sizes** instead.

</details>

<details>

<summary>How do I test at 1920 × 1080?</summary>

Set **Desktop** to 1920 × 1080 in **Project settings → Screen sizes**. The size is the whole browser window, so the page area is a bit smaller.

</details>

<details>

<summary>Can one test use its own custom size?</summary>

No. Each test uses the project's Desktop or Mobile size. For other sizes, duplicate the project and change its screen sizes.

</details>

<details>

<summary>Does Mobile emulate an iPhone or Android device?</summary>

No. It only makes the window smaller. There are no touch events and no device emulation. To get the mobile version of a site that checks the user agent, set a mobile **User agent** in project settings.

</details>


---

# 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.bugbug.io/workflow-tips/changing-the-test-screen-size.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.
