> 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/faq/load-webviewer-files-no-cache.md).

# How to load updated WebViewer files without clearing cache?

World's #1 PDF SDK Library for Web, Mobile, Server, Desktop

Change the actual file location of WebViewer's lib folder for each version.

Example: If WebViewer version 5.2.8 was used:

1. Create a new folder
2. put the WebViewer files in that folder
3. then change the syntax to be something along the lines of:

{% tabs %}
{% tab title="JavaScript" %}
{% code lineNumbers="true" %}

```js
WebViewer({
  path: '5.2.8/lib'
})
```

{% endcode %}
{% endtab %}
{% endtabs %}

Example: If upgrading to WebViewer 6.0 then follow similiar instructions to above:

{% tabs %}
{% tab title="JavaScript" %}
{% code lineNumbers="true" %}

```js
WebViewer({
  path: '6.0/lib'
})
```

{% endcode %}
{% endtab %}
{% endtabs %}

Optional Step:

Modify the main html page of the app such that it won't have the caching headers from the server set for too long.

When the version is updated, the HTML page will be updated to point to a new WebViewer path which isn't cached by the users.

Reference: [https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control/)


---

# 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/faq/load-webviewer-files-no-cache.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.