> 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/pdf-file-size-limits.md).

# What are the size limits for PDF files?

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

|                        | Viewing Limit | Saving Limit |
| ---------------------- | ------------- | ------------ |
| Local                  | No limit      | 2GB          |
| Remote, non-linearized | 2GB           | 2GB          |
| Remote, linearized     | No limit      | 2GB          |

Local files are those chosen from the file system or a blob URL. Remote files are those stored on the server or elsewhere on the web.

If you try to view or save a file that's too large, an error will be shown.

The limit for saving and viewing files is a result of the JavaScript limit for blob size (2GB). If you need to save a file that is larger than the limit you should send the XFDF string to a server, merge it there and return the file data from the server to the client.


---

# 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/pdf-file-size-limits.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.