> 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/core/print.md). # Print - [Printing Library for Server/Desktop](https://docs.apryse.com/core/print/print.md): Print a document with optimal compression by following these steps. Learn how to print a PDF to a default printer efficiently. Get started now! The Apryse Server SDK streamlines secure document proces - [Print a PDF to a printer on Server/Desktop](https://docs.apryse.com/core/print/printer.md): Learn how to print a PDF file to a default printer with sample code. Follow step-by-step instructions to easily print PDF documents. The Apryse Server SDK streamlines secure document processing with r - [Code samples for printing PDFs on Server/Desktop](https://docs.apryse.com/core/print/samples.md): Learn how to print a PDF file and perform PDF imposition with this informative guide. Discover how to combine pages and optimize printing for your documents. The Apryse Server SDK streamlines secure d - [APIs for PDF printing on Server/Desktop](https://docs.apryse.com/core/print/apis.md): Discover utility classes for printing PDF documents in various programming languages such as C++, Java, Android, .NET, iOS, Xamarin, and UWP with pdftron.PDF.Print. Optimize your PDF printing process --- # 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/core/print.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.