Outperforming WeasyPrint: Generating PDFs with JavaScript in Python

The challenge of modern rendering in Python

Any developer who has tried to convert a complex HTML template to PDF has hit the same wall: the design looks perfect in the browser, but when processed with tools like WeasyPrint, charts generated by Chart.js or dynamic elements vanish, leaving blank gaps. This happens because traditional Python programming solutions lack a real JavaScript execution engine.

Although WeasyPrint is an open source gem for static documents, its architecture falls short when the design relies on the modern web. Since it does not execute scripts, any dynamic component is simply invisible to its rendering engine.

Why are traditional alternatives not enough?

Most current tools in the Python ecosystem have critical limitations:

• WeasyPrint: Excellent for static CSS, but its proprietary CSS engine is often years behind current browsers, forcing you to maintain parallel stylesheets.
• pdfkit / wkhtmltopdf: Obsolete projects that do not support modern standards like Flexbox or Grid.
• xhtml2pdf: Very limited for complex professional designs.
• Headless Chrome (Playwright/Puppeteer): While they render perfectly, they entail a huge operational burden (memory consumption, cold start times, and heavy dependency management).

"None of these tools fail because they are inefficient; it is simply the cost of trying to reimplement a rendering engine outside of a real browser."

The alternative: External rendering APIs

For those seeking precision without the heavy burden of managing headless browsers in production, the solution is to delegate rendering to an external API. This approach allows you to send HTML via POST and receive a finished PDF that respects the execution of any script, including animations and charting libraries.

By using an API, we eliminate the need to install dependencies like Pango or HarfBuzz in our containers, making deployment much lighter and more portable—ideal for AWS Lambda architectures or Alpine images.

Advantages of this workflow:

1. Full compatibility: The PDF is rendered exactly as you see it in Chrome.
2. No dependencies: You only need the requests library to communicate with the service.
3. Simplified maintenance: No more security patches for complex system libraries.

If you are looking to delve deeper into how to optimize your development environment, I recommend reading about Learning programming with Go: An efficient and modern alternative, a language that, like these modern APIs, seeks to simplify the infrastructure required to execute high-performance code.

Conclusion

If your project requires absolute control over CSS paged media or must function in a 100% offline environment, stick with traditional libraries. However, for most enterprise applications where visual fidelity and the use of JavaScript are essential, delegating rendering to an API is the most efficient path toward stability.

What tools do you currently use to generate documents in your projects? Have you struggled with rendering charts in PDFs? Share your experience in the comments.