> 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/what-is-webviewer/browser-support.md).

# Browser support for WebViewer

Discover comprehensive browser support for WebViewer across Chrome, Firefox, Safari, Edge, and more. Ensure seamless web functionality with this detailed breakdown. The Apryse Web SDK streamlines secu

WebViewer supports the **last 3 major versions** of each browser, in line with industry standard. This keeps compatibility predictable without requiring ongoing maintenance of this page.

| Browser        | Client only | WebViewer Server | Custom server |
| -------------- | ----------- | ---------------- | ------------- |
| Chrome         | ✓           | ✓                | ✓             |
| Firefox        | ✓           | ✓                | ✓             |
| Safari         | ✓           | ✓                | ✓             |
| Edge           | ✓           | ✓                | ✓             |
| Android Chrome | ✓           | ✓                | ✓             |

{% hint style="info" %}
**What "last 3 major versions" means:** As browsers release new versions, support automatically shifts forward. This matches the policy used by most major platforms and frameworks — no manual updates to this page are required.
{% endhint %}

{% hint style="warning" %}
Changed in WebViewer version 12.0: We previously listed specific minimum version numbers per browser. That table has been replaced with the last-3-versions policy above. If you were relying on an older browser version, please review your compatibility requirements.
{% endhint %}


---

# 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/what-is-webviewer/browser-support.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.