> 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/ios/compare-files.md). # Compare files - [Compare files for differences on iOS](https://docs.apryse.com/ios/compare-files/compare.md): Discover how to use Overlay To for visual document comparison by overlaying and masking. Enhance your document analysis with this powerful tool! The Apryse iOS SDK streamlines secure document processi - [Compare PDF files on iOS](https://docs.apryse.com/ios/compare-files/file-comparison-i.md): Enhance your file comparison capabilities with the Apryse SDK. Learn how to highlight differences between PDF pages and create customizable visual comparisons effortlessly. Explore the powerful featur - [PDF comparison code sample for iOS](https://docs.apryse.com/ios/compare-files/samples.md): Discover a sneak peek of a compare files sample for iOS coming soon. Stay tuned for the latest updates on this exciting new feature! The Apryse iOS SDK streamlines secure document processing and seaml - [APIs for comparing PDF differences on iOS](https://docs.apryse.com/ios/compare-files/apis.md): Compare files using utility classes in iOS with Objective-C/Swift. Learn about PTPDFDoc for efficient file comparison. Optimize your file management now! The Apryse iOS SDK streamlines secure document --- # 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/ios/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.