> 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/ms-office.md). # MS Office - [Convert & view MS Office files (Word, Excel & PowerPoint) with Server/Desktop](https://docs.apryse.com/core/ms-office/office.md): Convert MS Office files to PDF and vice versa without third-party tools. Learn how to optimize document conversion with Apryse and various programming languages. Create PDFs from Microsoft Office file - [Compare Word documents in a DOCX file](https://docs.apryse.com/core/ms-office/compare-docx.md): Here is your guide explaining how to perform a semantic comparison on MS Word files using Apryse SDK. - [Code samples for converting Word, Excel, PowerPoint to PDF on Server/Desktop](https://docs.apryse.com/core/ms-office/samples.md): Convert MS Office files to PDF with ease using this sample code. Learn how to convert Word, Excel, and PowerPoint files to PDF effortlessly. The Apryse Server SDK streamlines secure document processin - [APIs for MS Office (docx, xlsx, pptx, rtf, msg, eml) to PDF conversion on Server/Desktop](https://docs.apryse.com/core/ms-office/apis.md): Discover utility classes for converting MS Office files to PDF in various programming languages like C++, Java, Android, JavaScript, Node.js, .NET, iOS, Xamarin, and UWP. Optimize your workflow with t --- # 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/ms-office.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.