> 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/find-image-in-pdf.md).

# Find Image in PDF

This is pre-built Action located under the **@Generic Element,** instructs the Avo Assure to check whether the expected image is present in provided PDF file based on the input value and save the result in the given dynamic variable.

### **Syntax**

**Input Value:** `<PDF filepath>;<Image file path>`

| Argument                                | Description                                                                                                          |
| --------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
| <p>\<PDF filepath></p><p>(Required)</p> | Provide the file path of the PDF in which the image search will be performed.                                        |
| <p>\<Image file path><br>(Required)</p> | <p>provide the file path of the image file that you want to search for within the PDF.<br>Supported format: .PNG</p> |

**Output value:**

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

**Example 1**

**Find a specific image within a PDF file**\
\
The **Find Image in PDF** action searches for a specified image inside a given PDF file (e.g., **C:\Documents\Sample.pdf;C:\Images\Logo.png**). The action scans each page of the PDF to determine whether the provided image appears within its contents. If found the status is stored in the **{Find}** variable, with the following possible values:

* **True** – if the image is found in the PDF
* **False** –if the image is not found in the PDF

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FHBGeQucyNI47QV6NL5kX%2Fimage.png?alt=media&amp;token=ca497bba-a4be-4fb1-81c2-a0f25117fccb" 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/find-image-in-pdf.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.