> 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/conversion/conversion.md).

# Convert Office, Images to PDF in a browser with JavaScript

Convert Office documents and images to PDF directly in your browser using JavaScript with WebViewer. No server-side dependencies needed. Effortlessly convert DOC, DOCX, XLS, XLSX, PPT, PPTX, JPG, PNG,

WebViewer allows client-side conversion without need for any server-side dependencies. Conversion APIs include:

[Office to PDF](/web/ms-office/convert-office.md) Convert DOC, DOCX, XLS, XLSX, PPT, PPTX to PDF in the browser without MS Office dependencies.

[Image to PDF](/web/conversion/convert-image-to-pdf.md) Convert JPG, PNG, TIF, TIFF to PDF in the browser.

[PDF to Image](/web/conversion/convert-pdf-to-image.md) Rasterize PDF to PNG, JPEG, or TIFF.

WebViewer supports a number of [formats](/web/what-is-webviewer/file-format-support.md) out-of-the-box. To get access to even more formats, you can leverage [WebViewer Server](/web/webviewer-server/wv-server-deployment.md), plug-and-play Docker image, or leverage [Windows](/core/conversion/conversion.md) or [Linux](/core/conversion/conversion.md) SDK for conversion.

## Demos

[PDF to Image Demo](https://showcase.apryse.com/pdf-to-image) [Image to PDF Demo](https://showcase.apryse.com/image-to-pdf) [MS Office to PDF Demo](https://showcase.apryse.com/office-to-pdf)

## Related blogs

[Advanced Options When Converting from HTML to PDF](https://apryse.com/blog/html-to-pdf-conversion-with-apryse-sdk) - 8/28/24


---

# 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/conversion/conversion.md?ask=<question>&goal=<user_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.