Can the WeasyPrint API convert Word or PowerPoint files to PDF?

No. It converts HTML to PDF and nothing else. Api2Pdf converts Office files with LibreOffice and can merge PDFs (https://www.api2pdf.com/, as of Sep 2026). On pagespool, the Gotenberg engine converts Office files with the same key.

Can I choose the rendering engine per request?

Yes, by the path. /v1/weasyprint/render always runs WeasyPrint 70, and each other engine here has a path of its own. At Api2Pdf the engine is part of the endpoint path too, for example /chrome/pdf/url (https://www.api2pdf.com/, as of Sep 2026).

How does usage-based pricing compare with credits?

For small documents, usage pricing can cost less. At Api2Pdf's prices, 10,000 renders of 0.1 MB and 1 second each cost about $4 a month (https://www.api2pdf.com/pricing/, as of Sep 2026). pagespool costs €20 a month for 10,000 credits. Its price per render does not depend on render time or file size.

Hosted WeasyPrint vs Api2Pdf

Api2Pdf offers Chrome, wkhtmltopdf and LibreOffice behind one API and bills compute time. pagespool renders HTML with WeasyPrint 70 at 1 credit per render.

Last updated Oct 22, 2026

Api2Pdf engines	Headless Chrome, wkhtmltopdf and LibreOffice behind one REST API; URL to PDF; Word and PowerPoint to PDF; PDF merge (as of Sep 2026)
Api2Pdf pricing	$1 a month, plus $0.001 per MB of bandwidth and $0.00019551 per second of compute (as of Sep 2026)
pagespool	HTML to PDF with WeasyPrint 70 at one endpoint; 1 credit per render; €20 a month for 10,000 credits

Api2Pdf puts several engines behind one API. It converts HTML with Chrome or wkhtmltopdf, live URLs with Chrome, Office files with LibreOffice, and merges PDFs (as of Sep 2026). The WeasyPrint API is one engine at one endpoint, POST /v1/weasyprint/render, for HTML to PDF.

What each one costs

Api2Pdf bills $1 a month plus bandwidth and compute time (Api2Pdf pricing, as of Sep 2026). As an example, 10,000 documents of 0.1 MB that take 1 second each come to about $4 a month: $1 base, $1.00 bandwidth and $1.96 compute. Your own render time and file sizes set the real figure.

pagespool charges 1 credit per render with an API key, whatever the page count. €20 a month buys 10,000 credits (pricing). Without a key, 10 credits a day are free.

When Api2Pdf fits

You want Headless Chrome output, or a PDF of a live URL (POST /chrome/pdf/url, Api2Pdf, as of Sep 2026).
Your documents are small and quick to render, so usage pricing costs less than a €20 plan (see the example above).

The WeasyPrint API converts no Office files, merges no PDFs, runs no JavaScript and loads no URLs.

When the hosted WeasyPrint fits

Your workload is HTML to PDF: invoices, reports, generated documents.
You want to know the cost of a render before you send it. 1 render is 1 credit (API keys and rate limits).
Agents render PDFs through the MCP server.

Paste up to 100 KB of HTML without an account: render it in the free tool.

FAQ

Can the WeasyPrint API convert Word or PowerPoint files to PDF?: No. It converts HTML to PDF and nothing else. Api2Pdf converts Office files with LibreOffice and can merge PDFs (https://www.api2pdf.com/, as of Sep 2026). On pagespool, the Gotenberg engine converts Office files with the same key.
Can I choose the rendering engine per request?: Yes, by the path. /v1/weasyprint/render always runs WeasyPrint 70, and each other engine here has a path of its own. At Api2Pdf the engine is part of the endpoint path too, for example /chrome/pdf/url (https://www.api2pdf.com/, as of Sep 2026).
How does usage-based pricing compare with credits?: For small documents, usage pricing can cost less. At Api2Pdf's prices, 10,000 renders of 0.1 MB and 1 second each cost about $4 a month (https://www.api2pdf.com/pricing/, as of Sep 2026). pagespool costs €20 a month for 10,000 credits. Its price per render does not depend on render time or file size.