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

# Search

- [Text & image search library for Android](https://docs.apryse.com/android/search/search.md): Looking to search and replace text or images in a PDF? Learn how to efficiently search for and replace content in your PDF files with this helpful guide. The Apryse Android SDK streamlines secure docu
- [Text search](https://docs.apryse.com/android/search/text.md): Learn how to add text search functionality to your Android viewer with this comprehensive guide. Implement UI components and API for efficient text searching. The Apryse Android SDK streamlines secure
- [Replacing text & images in PDFs with Android](https://docs.apryse.com/android/search/replace.md): Learn how to find and replace text or images in a PDF using pdftron.PDF.ContentReplacer. Get a full code sample for searching and replacing text strings and images in existing PDFs like business cards
- [Code samples for searching PDF text or images in Android](https://docs.apryse.com/android/search/samples.md): Learn how to search PDF files for text, replace text or images, and explore UI samples in this Android showcase app using PDFTron SDK. The Apryse Android SDK streamlines secure document processing and
- [APIs for searching PDF documents in Android](https://docs.apryse.com/android/search/apis.md): Discover utility classes for searching PDF documents in Android using Java or Kotlin with com.pdftron.pdf.TextSearch and com.pdftron.pdf.ContentReplacer. Optimize your PDF document search now! The Apr


---

# 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/search.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.
