> 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/samples/pdf-manipulation.md). # PDF manipulation samples in JavaScript Learn how to use thumbnail controls, perform page operations, assemble documents from multiple viewers, separate layers, and colors for enhanced document manipulation. Ideal for client-side PDF and Of ## Thumbnail controls Shows how to use thumbnail controls for page manipulation of documents. Note that this is only enabled for client side PDF and Office documents. Launch demo View source code ## Page operations Shows how to rotate/crop/add/delete page, change page order, insert blank pages and merge multiple documents. Launch demo View source code ## Document assembly from multiple viewers Shows how to implement a dropzone to be able to drag and drop pages from multiple viewer instances. View source code ## Layer separation Shows how to get each layer's information. You can also show/hide specific layers. Launch demo View source code ## Color separation Shows how to get each color's information. You can also show/hide specific colors. Launch demo View source code --- # 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/samples/pdf-manipulation.md?ask=&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.