> 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/compare-files.md). # Compare Files This pre-built action, located under the **@Generic Element**, instructs Avo Assure to compare the contents of two specified files (e.g., .txt, .xml, .json). It calculates the number of differences between the files and stores the result in a dynamic variable.
**Syntax** **Input Value:** `;;` {% hint style="warning" %} **Note:** By default, the final argument in the above syntax is **all** and will store all file’s content in the dynamic variable and if final argument is written as **Selective** then dynamic variable will display selective data of file. {% endhint %} | Argument | Description | | -------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | |

(Required)

| Provide file path to the original file which you want to compare against | |

\
(Required)

| Provide file path that needs to be compared with the original. | |

\
(Optional)

Selective/All if provided:
• Selective → compares only specific parts
• All → compares the entire content of both files

| **Output Value:** | Argument | Description | | ---------------------------------------- | --------------------------------------------------------- | |

\
(Required)

| This variable holds the result of the content comparison. | |

\
(Optional)

| This variable stores the status as **true** or **false** | **Example 1** **Compare two files and identify differences**\ \ The **Compare Files** action takes the value from the Input Value column (e.g., **C:\Files\BaseFile.txt;C:\Files\UpdatedFile.txt;All**) and compares the original file with the file to be compared. The result of the comparison is stored in the **{Comparison}** variable, and the action status is saved in the **{Status}** variable with the following possible values: * **True** –if the files are compared successfully * **False** – if the files are not compared

**Example 2** **Performs comparison between two files to identify differences in content**\ \ The **Compare Files** action takes the value from the Input Value column (e.g., **C:\Files\original.txt;C:\Files\updated.txt;Selective**) and compares the content of the specified files. When the comparison type is set to **Selective**, only selected parts of the files (e.g., **specific lines or paragraph**) are compared. The result of the file comparison is stored in the **{Comparison}** variable, while the execution status is stored in the **{Status}** variable, with the following possible values: * **True** – if the files match based on the selected comparison mode. * **False** – if any differences are found or an error occurs.

--- # 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/compare-files.md?ask=&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.