> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/actions/web/browser/set-browser-zoom-level.md).

# set Browser Zoom Level

This is a pre-built Action located under the **@Browser Element**. The functionality of this Action in Avo Assure is to set the browser zoom level based on the value provided. The execution status is then stored in the dynamic variable.

## Syntax

**Input Value**: `<Zoom Level>`

{% hint style="info" %}
**Note**: Use this action before the test step that requires a specific browser zoom level.
{% endhint %}

| Argument                           | Description                                            |
| ---------------------------------- | ------------------------------------------------------ |
| <p>\<Zoom Level><br>(Required)</p> | Provide the zoom level you want to set in the browser. |

**Output Value**: `<Dynamic Variable>(Optional);<Dynamic Variable>(Optional)`

| Argument                                                     | Description                                                       |
| ------------------------------------------------------------ | ----------------------------------------------------------------- |
| <p>\<Dynamic Variable>;\<Dynamic Variable><br>(Optional)</p> | Both dynamic variables store the status as **True** or **False**. |

### Example: Setting the Browser Zoom Level

In this example, we explain how to set the zoom level of the browser window.

* **Action:** set Browser Zoom Level
* **Input Value:** 125
  * The value **(125)** indicates the zoom level applied to the browser.
* **Output Value:** {ZoomStatus}
  * The execution status (e.g., True) is stored in this **{ZoomStatus}** dynamic variable with the following possible values:
    * **True:** If the zoom level is applied successfully.
    * **False:** If the zoom level cannot be applied due to an invalid value or browser limitation.
* **Logical Explanation**: The **set Browser Zoom Level** action fetches the value from the **Input Value** column **(125)** and applies this zoom level to the active browser window. After execution, the action stores the result (True) in the **{ZoomStatus}** dynamic variable.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2Fk9jzFx32bQEtOwFcZ810%2Fimage.png?alt=media&amp;token=f95796c2-60c3-4df1-b7fd-c75b7af53da4" alt=""><figcaption></figcaption></figure>

#### Knowledge Bites

Below are some examples of different zoom level scenarios:

| Zoom Levels         | Input Value | Result |
| ------------------- | ----------- | ------ |
| Minimum Zoom Level  | **50**      | True   |
| High Zoom Level     | **150**     | True   |
| Maximum Zoom Level  | **200**     | True   |
| Negative Zoom Level | **-60**     | False  |


---

# 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.avoautomation.com/avo-assure/actions/web/browser/set-browser-zoom-level.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.