library VS WeasyPrint

Give the official QuestPDF repository a star ⭐ so more people will know about it. Most developers evaluate project maturity based on the star count so let's help them make the right decision!

There are already a couple of free or paid libraries in the .NET ecosystem that can be used to generate PDF files. The way how QuestPDF differs is simple: instead of relying on an HTML-to-PDF conversion, it implements its own layouting engine that renders the full content using the SkiaSharp library (a Skia port for .NET, used in Chrome, Android, MAUI, etc.).

Hi, can you please elaborate more about your question? Or create a discussion on the repository page? https://github.com/QuestPDF/library/discussions I am not sure exactly what requirement you would like to achieve :)

QuestPDF is my go-to.

Hi :) That is a good point about most of the APIs available. I truly believe that it does not apply to the QuestPDF library. The Fluent API here is used only to describe the document's content, to create new element instances and assign them to parents. In other words, there is no business logic involved in this code area. Please analyze the QuestPDF.Fluent namespace. You will find that most of the API invocations are super simple and straightforward.

check out https://github.com/questpdf/library

Is there a reason you didn't consider something like Weasyprint?

https://weasyprint.org

I've gone through a number of systems to convert CV's, business cards, and other docs and it hasn't let me down yet.

You don't _have_ to use a browser. I had very good results with Weasyprint [0]. And there's also PrinceXML [1] if you're willing to pay.

[0]: https://weasyprint.org/

Thanks for your answer! I imagined you would be using PrinceXML behind the scenes since that is probably the gold standard in HTML+CSS rendering.

The only open source alternative I know of is WeasyPrint at https://weasyprint.org/. I'm not sure how well it fares against PrinceXML, though.

And thanks for the pointer to Taffy - I didn't know it before!

Flexbox support has been [included][1] since 2018, although my use case was the prototypical one - a single row w/ 3 columns - so YMMV with how it handles more complex layouts.

[1]: https://github.com/Kozea/WeasyPrint/pull/579

Performance is not the strength of WeasyPrint, meaning that heavy HTML files will increase generation time. You should always compress images before attaching them, as they are not compressed by default. Generating a 50-page-long PDF may take up to a minute in extreme cases, although multi-page documents generated on my project take fewer than 2 seconds to generate.

For Python there is Weasyprint: you prepare the invoice as an HTML document, and Weasyprint turns it into a PDF

https://weasyprint.org/

Well yes, but you can implement HTML+CSS. WeasyPrint did from scratch, and independent implementations of HTML+CSS are considerably more numerous than HTML+CSS+JS.

In a recent project I used https://github.com/Kozea/WeasyPrint/ it is written in python, so you will need to use it like so:

You should maybe check out weasyprint. https://weasyprint.org/