> 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/generic/file-and-folder-operations/verify-file-images.md).

# Verify File Images

This is pre-built Action located under the **@Generic Element**, instructs the Avo Assure to check whether both the images are same whose image path is provided in Input Value and save the result in the dynamic variable.

### **Syntax**

**Input Value:** `<image1path>;<image2path>`

| Argument                              | Description                                                                                                               |
| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| <p>\<image1path></p><p>(Required)</p> | <p>Provide the image path to be compared with the second image.<br>Supported file types: .png, .jpeg, .jpg.,</p>          |
| <p>\<image2path><br>(Required)</p>    | <p>Provide the path of the second image to compare with the first image.<br>Supported file types: .png, .jpeg, .jpg.,</p> |

**Output Value:**

| Argument                                                    | Description                                              |
| ----------------------------------------------------------- | -------------------------------------------------------- |
| \<Dynamic Variable>(Optional);\<Dynamic Variable>(Optional) | This variable stores the status as **true** or **false** |

**Example**

**Verify if two images are visually identical**\
\
The **Verify File Image** action takes the value from the Input Value column (e.g., **C:\Images\Base.png;C:\Images\Output.png**) and compares the two image files to check for visual similarity. The verification result is stored in the **{Status}** variable with the following possible values:

* **True** – if the images match successfully
* **False** – if the images do not match

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FwEqMTgCGKL5kMMtLgkKn%2Fimage.png?alt=media&amp;token=2302cb8c-a0b0-40ed-8130-5bb3396781e3" 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/generic/file-and-folder-operations/verify-file-images.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.