> 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/cli/pdf-pagemaster/faq.md). # Frequently Asked Questions Learn how to split pages in PDF into separate documents using PDF PageMaster. No third-party dependencies, easy integration with client/server applications. Contact us for more details! The Apryse CLI ### How do I split pages in PDF into separate PDF documents? The following command-line will split 'in.pdf' into separate PDF documents: `pagemaster -s in.pdf` ### Can I split PDF based on bookmarks? Split 'in.pdf' based on the destinations of the root bookmarks (usually chapters etc.): `pagemaster -s --bybookmarks 1 in.pdf` ### Does PDF PageMaster have any dependencies on third party components/software? PDF PageMaster is a completely stand-alone application and it does not include any dependencies on third-party components or software. ### What is the difference between [PDF SDK](https://apryse.com/products/core-sdk/pdf) and PDF PageMaster? PDF PageMaster is based on [PDF SDK](https://apryse.com/products/core-sdk/pdf), Apryse's own core PDF programming technology. Our PDF SDK is a comprehensive developer library for PDF creation, manipulation and rendering, offered on a wide range of platforms and programming environments. If you require functionality for integration in your own applications beyond that which is provided as part of PDF PageMaster, or need more flexibility in implementing the required functionality, please contact a [Apryse representative](https://apryse.com/contact-us). The main distinction between the two components is that PDF PageMaster is a specialized tool for simple PDF manipulations such as page splitting and merging, whereas [PDF SDK](https://apryse.com/products/core-sdk/pdf) is a general purpose Software Development Toolkit (SDK) that can be used to implement any type of manipulation on PDF documents (including splitting and merging) as well as other type of PDF functionality. The advantage of PDF PageMaster is that it is very simple to use and that it doesn't require much experience with PDF format or general programming. At the same time PDF PageMaster does not include all of the features and options that are available in [PDF SDK](https://apryse.com/products/core-sdk/pdf). ### Can I integrate PDF PageMaster with my client/server application? PDF PageMaster has a simple-to-use CLI that can be easily integrated into third-party client and server-based applications. The CLI is available as a plain executable and can be easily accessed from any programming language (including C#, VB.NET, C/C++, Java, VB6, Perl, Python, Ruby, Delphi, etc). For more information on PDF PageMaster, please contact an Apryse representative at . ### I didn't find the answer to my question in the user manual. Are there any other helpful resources? You may want to search the [Apryse Knowledge Base forum](https://apryse.com/support) or to simply forward your question to Apryse's technical support team via . --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.apryse.com/cli/pdf-pagemaster/faq.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.