> 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/image/verifywebimages.md).

# verifyWebImages

This is a pre-built Action located under the captured image element. The functionality of this action in Avo Assure is to compare an image captured from the application with the reference image provided in the input path. The result is stored in the given dynamic variable for further use during test execution..

## **Syntax**

**Input Value**: `<image path>`

| Argument                              | Description                                                                      |
| ------------------------------------- | -------------------------------------------------------------------------------- |
| <p>\<image path></p><p>(Required)</p> | Provide the path of the image which you want to compare with the captured image. |

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

| Argument                                                     | Description                                                       |
| ------------------------------------------------------------ | ----------------------------------------------------------------- |
| \<Dynamic Variable>(Optional);\<Dynamic Variable> (Optional) | Both dynamic variable stores the status as **True** or **False**. |

### **Example: Verifying Similarity Between Captured and Reference Images**

In this example, we explain how to verify whether the currently captured image from the web page matches the reference image path provided in the input.

* **Action**: VerifyWebImages
* **Input Value**: C:\Users\John.smith\test\sample.png
  * The first argument (**C:\Users\John.smith\test\sample.png**) specifies the file path of the reference image stored in the local system.
* **Output Value**: {Status}
  * The result of the image comparison is stored in the **{Status}** dynamic variable with the following possible values:
    * **True**: If the comparison is successfully.
    * **False**: If the comparison is not successfully.
* **Logical Explanation**: The **VerifyWebImages** action reads the reference image path from the **Input Value** column (**C:\Users\John.smith\test\sample.png**). The action captures the current image from the web page during test execution and compares it with the provided reference image. Based on the similarity between both images, the action determines the final status of the verification. The result of this comparison (**True**) is stored in the **{Status}** variable.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FpnSqhwDy8tWSQS6hMsFu%2Fimage.png?alt=media&amp;token=0f5afd75-32b1-44e4-959a-885af8761537" alt=""><figcaption></figcaption></figure>


---

# 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/image/verifywebimages.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.
