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

# Convert HTML to PDF

Convert HTML pages to PDF with ease using WebViewer Server. Integrate with WebViewer or use GetPDF API directly. Check out our GitHub repository for web-to-pdf conversion. The Apryse Web SDK streamlin

## WebViewer Server

You can convert HTML pages using [WebViewer Server](/web/webviewer-server/wv-server-deployment.md). You can either configure [WebViewer to work together](/web/webviewer-server/wv-server-setup.md#webviewer-integration) with WebViewer Server and then load HTMLs through [loadDocument API](/web/open-save-document/open/url.md) or just directly call WebViewer Server [GetPDF API](/web/webviewer-server/wv-server-usage.md#getpdf) to convert HTML and get the resulting PDF without WebViewer integration.

## Using Windows or Linux SDKs

Another approach similar to [GetPDF API](/web/webviewer-server/wv-server-usage.md#getpdf), is to leverage Windows or Linux SDKs (Node.js, .NET, .NET Core, JAVA, Python and others). You can refer to the [full sample](/core/get-started/samples/html2pdftest.md) and get started with [Windows](/core/get-started/platforms/windows.md) or [Linux](/core/get-started/platforms/linux.md) solutions to get started.


---

# 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/html/convert-html.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.