> 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/save-file.md).

# Save File

The Save File action in the Avo Assure is found under the **@Generic Element** is used to save a file which is opened in the new browser tab to a specified location on the system and stores the result in an dynamic variable.

### **Syntax**

**Input Value:** `<FilePath>;<FileName.extn>;<URL>(Optional)`

| Argument                              | Description                                                                                                                      |
| ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| <p>\<filepath></p><p>(Required)</p>   | Specify the folder location where the user wants to save their file.                                                             |
| <p>\<filename.extn><br>(Required)</p> | <p>Define the file format for saving the specified file<br>Supported file format: (extn: Extension)<br>.pdf, .txt, .xml, etc</p> |
| <p>\<URL><br>(Optional)</p>           | The URL from which the file should be downloaded.                                                                                |

{% hint style="warning" %}
***Note:***

* *This action is applied only for web app type.*
* *Supported file Formats: .xml, .txt, .pdf*
* Before using the Save File step, the user needs to add the Send Function Keys step to save a file opened in a new tab (eg., Ctrl+Shift+S for Internet Explorer, Ctrl + S for Chrome and Edge). The user should choose the correct keys for their browser.
  {% endhint %}

**Output Value:**

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

**Example**

**Save a file from the browser or URL to a specified location**\
\
The **Save File** action saves a file to the specified path with the given filename (e.g., **C:\sam;demo.txt;<https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf>**). Before using this step, the user must add the appropriate **Send Function Keys** action in step to open the browser's save dialog. The Save file action is completed based on the provided parameters, and the action status is stored in the **{Status}** variable with the following possible values:

* **True** – if the file is saved successfully
* **False** –if the file is not saved successfully.

<figure><img src="/files/3eTxdraTTaT0KI1ApES8" 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.avoautomation.com/avo-assure/actions/generic/file-and-folder-operations/save-file.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.