> 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/faq/external-converter.md). # What is external converter? World's #1 PDF SDK Library for Web, Mobile, Server, Desktop External converter is the use of an external app such as MS Office, MS Outlook, or other applications to request converting the source file to PDF. We offer two solutions for how the SDK utilizes external conversion. * With MS Office or MS Outlook related formats, this conversion uses an [interop](https://en.wikipedia.org/wiki/COM_Interop) to request export services from the application. * For other formats, an external application will request a print job with the PDFNet virtual printer to create a PDF. The Apryse SDK will automatically choose either of the above options based on the format type. More information on external conversion can found in our [conversion guide](/core/conversion/convert-other.md). --- # 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/faq/external-converter.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.