> 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/appian/get-started/faq/how-can-i-extract-document-pages-or-split-documents-in-appian.md).

# How can I extract document pages or split documents in Appian?

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

Enable `enableExtractPagesToAppian` by setting it to true. First, you need to select pages you would like to extract. To do this, open the `Left Panel` with thumbnail previews of the current document. You can select one or multiple pages by clicking on a thumbnail (hold shift to select a page range) or pass a text string of the page range at the bottom of the thumbnail panel. Then click on the `Extract Selected Pages` button on the top right of the WebViewer UI. This will open a modal that will let you name your file. You can click `Save` to create a new document with extracted pages without changing the original document you are currently viewing. Alternatively, click on `Save & Remove pages` to remove the pages from the original document and save them into the newly created one.


---

# 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/appian/get-started/faq/how-can-i-extract-document-pages-or-split-documents-in-appian.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.
