> 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/android/compare-files.md). # Compare files - [Compare files for differences in Android](https://docs.apryse.com/android/compare-files/compare.md): Compare documents visually with Overlay To, a tool that overlays and masks for easy comparison. Enhance your document review process now! The Apryse Android SDK streamlines secure document processing - [File comparison in Android](https://docs.apryse.com/android/compare-files/file-comparison-a.md): Visually compare pages with ease using the resolution-independent comparison tool. Integrate UI components in your app with Standalone activity and Comparison options dialog. Follow Android best pract - [PDF comparison sample for Android](https://docs.apryse.com/android/compare-files/samples.md): Learn how to compare two pages with this sample app. Explore the demo by selecting the Compare page sample under Creation in the app. The Apryse Android SDK streamlines secure document processing and - [APIs for comparing PDF differences in Android](https://docs.apryse.com/android/compare-files/apis.md): Compare files using utility classes in Android (Java/Kotlin) with com.pdftron.pdf.PDFDoc. Enhance your file comparison process efficiently. The Apryse Android SDK streamlines secure document processin --- # 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/android/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.