> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/xamarin/compare-files.md).

# Compare files

- [Compare files for differences in Xamarin](https://docs.apryse.com/xamarin/compare-files/compare-files.md): Compare documents visually with Overlay To, a tool that overlays and masks for easy comparison. Enhance your document analysis now! The Apryse Xamarin SDK streamlines secure, serverless document proce
- [Compare files with overlay](https://docs.apryse.com/xamarin/compare-files/overlay.md): Compare files visually using overlays with Apryse SDK for Xamarin.Android. Learn how to integrate UI components for file comparison in your app. Find differences quickly and efficiently. The Apryse Xa
- [Samples for PDF comparison in Xamarin](https://docs.apryse.com/xamarin/compare-files/samples.md): Discover UI samples in Xamarin.Android and Xamarin.iOS showcase sample app. Compare Files feature showcases SDK capabilities. Explore demos now! The Apryse Xamarin SDK streamlines secure, serverless d
- [APIs for comparing PDF differences in Xamarin](https://docs.apryse.com/xamarin/compare-files/apis.md): Discover utility classes for comparing files in Xamarin.Android and Xamarin.iOS using C# with pdftron.PDF.PDFDoc. Enhance your file comparison capabilities now! The Apryse Xamarin SDK streamlines secu


---

# 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.apryse.com/xamarin/compare-files.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.