> 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/get-started/guides/learn-more-overview.md).

# Learn more about WebViewer

Discover the power of WebViewer for seamless document processing on web. View, annotate, and collaborate effortlessly with this versatile library. Embed it in your web app for a seamless user experien

WebViewer can help you solve your document processing needs on the web.

It is the ultimate library for document viewing, annotation, or collaboration. Working with all major web platforms, the viewer can be directly embedded and customized within any web application. The content can be instantly accessed from any browser or device.

## Get started

[Inside WebViewer](/web/what-is-webviewer/wv-inside.md) An introduction to the inner workings of the WebViewer app.

[Framework compatibility](/web/get-started/libraries-and-frameworks/frameworks.md) An introduction to using WebViewer with other web frameworks.

[Deployment options](/web/what-is-webviewer/deployment-options.md) To deploy pure client-side, WebViewer Server, or a custom server.

[Best practices](/web/best-practices/best-practices.md) To create the best results for most use cases.

[WebViewer events](/web/events/viewer-events.md) To go over the order of events when WebViewer is instantiated.

[Viewer optimized PDF](/web/best-practices/viewer-optimized-pdf.md) An introduction to using viewer optimized PDF files in WebViewer.


---

# 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/get-started/guides/learn-more-overview.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.