> 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/screenshot/capture-screenshot.md).

# Capture Screenshot

This is a pre-built Action located under the **@Generic Element**. The functionality of this Action in Avo Assure is to take a screenshot of whatever is currently visible on the desktop and save it to the folder path with file name given in the input value. The execution result is stored in the dynamic variable.

## Syntax

**Input Value**: `<Input file path>;<filename>`

| Argument                                | Description                                                                                  |
| --------------------------------------- | -------------------------------------------------------------------------------------------- |
| <p>\<Input file path><br>(Required)</p> | Provide the location where the screenshot needs to be saved. For example, Downloads/Desktop. |
| <p>\<filename><br>(Required)</p>        | Provide the name of the file for the captured screenshot.                                    |

**Output Value**: `N/A`

| Argument | Description    |
| -------- | -------------- |
| N/A      | Not Applicable |

### **Example:** Capturing and Saving a Screenshot

In this example, we explain how to capture the current screen and save it to a specified location.

* **Action**: Capture Screenshot
* **Input Value**: C:\Users\Downloads;Snapshot
  * The first argument (**C:\Users\Downloads**) specifies the folder path where the screenshot is saved.
  * The second argument (**Snapshot**) specifies the file name for the captured screenshot.

**Logical Explanation**: The **Capture Screenshot** action takes the value from the **Input Value** column (**C:\Users\Downloads;Snapshot**) and captures the current screen. It then saves the screenshot in the folder (C:\Users\Downloads) with the file name (Snapshot).

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2F0ldbnrliwMGQuZmhmYxY%2Fimage.png?alt=media&amp;token=0059c41e-67b1-45b3-953a-7a78bffc1c24" 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/screenshot/capture-screenshot.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.
