Rotativa VS gotenberg

I've been using Rotativa[1] for URL to PDF generation which is also a wrapper for wkhtmltopdf. They have a dotnet-core[2] version and also a SaaS[3] but I think it's worth mentioning that Azure PaaS supports wkhtmltopdf natively[4] so I just self-host.

Looking at QuestPDF's API docs, it doesn't look like they support URL / HTML to PDF generation. I think this would be a great addition especially given the age and issues with Rotativa and TuesPechkin on their GitHubs.

[1] https://github.com/webgio/Rotativa

I've used numerous technologies for doing that conversion, including WebSuperGoo's ABCpdf.net, and Rotativa's free library. (We even have an article on how to use it.) The latter is still in use on some of my projects, but it—and its newer .Net Core version—is based on wkhtmltopdf.exe, which is a problem. More about that later.

Use a server-side headless browser such as puppeteer to convert the HTML to PDF. This is the most reliable free option, but requires a server. If you need to use it in production, we recommend you use Gotenberg.

We're using Gotenberg[1] to convert a rendered web page (with Elixir/Phoenix, in our case) to PDF. Works like a charm and we can use our existing frontend code/styling (including SVG graph generators) which is a huge bonus.

1: https://gotenberg.dev/

If you also want to convert Markdown or LibreOffice formats, the self-hosted API Gotenberg is worth checking out

I found a project that does exactly that (https://github.com/gotenberg/gotenberg). It’s my best bet for now, but I still need to test GraalVM integration with JS runtimes (and test JS libraries) and the Kotlin compiler targeting Node.

Gotenberg is a Docker-based stateless API for PDF generation from HTML and Markdown files.

Think you mean https://gotenberg.dev ?

We use https://gotenberg.dev/ with handlebars templates.