> 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/uwp/conversion.md). # Conversion - [Document conversion library for UWP](https://docs.apryse.com/uwp/conversion/conversion.md): Convert documents easily with our document conversion API. Preserve text, graphics, hyperlinks, and more in high fidelity. Direct conversion between various formats. Explore our SDK benefits now! The - [Convert to PDF with virtual printer in UWP](https://docs.apryse.com/uwp/conversion/convert-other.md): Convert various file types to PDF documents with PDF Converter on Windows systems. Learn how to convert any printable document to PDF using pdftron.PDF.Convert.ToPdf method. Supported formats include - [Convert multiple file types to PDF in UWP](https://docs.apryse.com/uwp/conversion/convert-multiple.md): Convert various formats to PDF with ease using PDF Converter. Explore supported file formats and access full sample code for high-quality conversion between PDF, XPS, TIFF, JPG, and more. The Apryse u - [Convert PDF to multiple file types in UWP](https://docs.apryse.com/uwp/conversion/convert-pdf.md): Convert PDF documents to various formats with PDF Converter. No internet connection needed. Convert to DOCX, DOC, HTML, SVG, TIF, PNG, JPEG, XPS, EPUB, TXT, and more. Explore full sample code for high - [Code Samples to convert to / from PDF in UWP](https://docs.apryse.com/uwp/conversion/samples.md): Code Samples to convert to and from PDF in UWP. - [APIs to convert files to PDF in UWP](https://docs.apryse.com/uwp/conversion/apis.md): Convert PDF documents to Office formats using utility classes in UWP (C#/VB/JS) with pdftron.PDF.Convert. Learn how to use pdftron.PDF.Convert#OfficeToPDF for seamless conversion. The Apryse uwp SDK s --- # 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/uwp/conversion.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.