> 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/web/documentviewer.md). # DocumentViewer - [Overview of the DocumentViewer](https://docs.apryse.com/web/documentviewer/documentviewer.md): Discover how to work with documents using the DocumentViewer object in WebViewer SDK. Learn about manual instantiation, adjusting layout and zoom, and more. Start optimizing your document viewing expe - [Working with documents using the Document Viewer](https://docs.apryse.com/web/documentviewer/working-with-documents.md): Discover how to work with documents using the Document Viewer object. Learn about common APIs for tasks like getting page information, starting text searches, and more. Dive into functions like getDoc - [Adjusting layout and zoom using the Document Viewer](https://docs.apryse.com/web/documentviewer/adjusting-layout-zoom.md): Discover how to adjust layout and zoom effortlessly with the Document Viewer. Explore APIs for changing display modes, setting zoom levels, and enhancing your viewing experience. The Apryse Web SDK st - [Interacting with tools with the Document Viewer](https://docs.apryse.com/web/documentviewer/interacting-with-tools.md): Enhance your document viewing experience with the ability to interact with various tools within the Document Viewer. Discover how tools in the Core.Tools namespace enable you to create annotations, se - [Right To Left (RTL) Language Support in DocumentViewer](https://docs.apryse.com/web/documentviewer/rtl-support.md): Review how right to left language support works within DocumentViewer. --- # 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/web/documentviewer.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.