QuestPDF VS library

What is QuestPDF? QuestPDF is an open-source .NET library for PDF document generation. It uses a fluent API approach to compose together many simple elements to create complex documents.

QuestPDF looks really good (I haven't used it) but I believe they changed their license recently.

I used that same library it worked great the only issue I had was the users would often have to manually set the scaling to fit to a page. I'm sure I could've fixed this in other ways if I was more competent with CSS but ended up just switching to use https://github.com/QuestPDF/QuestPDF in a backend instead of doing everything in front end.

Give this a try: QuestPDF

I think you should ask these questions in related discussion on Github: https://github.com/QuestPDF/QuestPDF/discussions/491

May I introduce you to QuestPDF!

➡️ James Newton-King ♔ on Twitter: "Coming in .NET 8: Route tooling for ASP.NET Core" / Twitter ➡️ Announcing .NET Community Toolkit 8.1 ➡️ Uno Platform 4.7 – New Project Template, Performance Improvements and more ➡️ C# Advent 2022 Awards | Cross Cutting Concerns ➡️ GitHub - QuestPDF ➡️ DNF Summit 2023 ➡️ .NET Frontend Day

Like many have suggested, I also cast my vote on QuestPDF. No more +50MB library including a Chrome browser to render HTML so a PDF of it can be created, which took 2-3 seconds each time. But with QuestPDF, it's so much faster!

Also, the library is open-source, so you can take a look at the exact implementation of the layout engine. It is inspired by Flutter and WPF, though optimized for pageable content: https://github.com/QuestPDF/QuestPDF/tree/main/Source/QuestPDF/Elements

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