Wkhtmltopdf
is now an abandonware

With the proliferation of digital resources in our information era, an immense number of libraries have populated the internet landscape. These libraries, designed for a variety of uses, have become invaluable tools for developers, providing pre-written code to perform routine or complex tasks.

Yet, this universe of libraries is also fraught with challenges, notably the phenomenon of "abandonware." A prime example of this is the increasingly obsolete software, wkhtmltopdf. And unfortunately, the internet is still crowded with libraries that use wkhtmltopdf. If you want to generate a PDF from HTML, you have surely come across it.

So, should you still use a library based on wkhtmltopdf, even if it’s obsolete? What are the risks? How can you replace it?

That’s what you’ll learn in this article.

Wkhtmltopdf, a deprecated library for converting HTML to PDF #

Wkhtmltopdf, the open-source command-line tool that allows the conversion of HTML content to PDF using the WebKit rendering engine, gained significant popularity in the developer community for its simplicity and effectiveness.

Despite the tool's popularity, its usage has become problematic due to its recent abandonment. As of now, wkhtmltopdf is classified as abandonware, a term used for software that is no longer being updated or maintained by its developers.

The challenge with obsolete libraries #

While several software programs face a similar fate over time, the abandonment of a widely used tool like wkhtmltopdf poses a unique set of challenges.

The primary issue is the potential for security vulnerabilities.

Since wkhtmltopdf is no longer receiving updates, it doesn't benefit from patches to fix bugs or potential security weaknesses that might be discovered over time. This leaves it, and any systems that rely on it, vulnerable to potential exploitation.

Additionally, as technology evolves, new standards, tools, and practices are established. Abandoned tools like wkhtmltopdf may fail to align with these evolving standards, making them increasingly incompatible with other systems or less effective at performing their intended tasks.

Despite these risks, numerous digital libraries on the internet continue to use wkhtmltopdf, primarily because replacing it would require significant time and resources. Migrating to a new tool or software can be a daunting task, often requiring changes in underlying code and significant testing to ensure functionality.

The state of wkhtmltopdf serves as a stark reminder of the need for continuous innovation and maintenance in the realm of digital libraries.

It emphasizes the importance of ensuring that widely used tools receive ongoing support, both to maintain their effectiveness and to safeguard the security of systems that depend on them.

As the internet continues to evolve and expand, we must grapple with the growing concern of abandonware and the legacy it leaves behind.

Libraries using wkhtmltopdf that you should quickly replace #

We have search for libraries still using wkhtmltopdf as a dependency, that you should drop as soon as possible 😬.

This is not an exhaustive list, but these are the most commonly used.

Libraries for Python using wkhtmltopdf #

• pdfkit: A Python wrapper for wkhtmltopdf.
• wkhtmltopdf-wrapper: Another Python wrapper for wkhtmltopdf.

Libraries for Ruby using wkhtmltopdf #

• wkhtmltopdf-binary: Provides binaries for WKHTMLTOPDF project in an easily accessible package.
• wicked_pdf: A Ruby wrapper for wkhtmltopdf.
• pdfkit: PDFKit is a Ruby HTML to PDF converter powered by wkhtmltopdf.

Libraries for PHP using wkhtmltopdf #

• knplabs/knp-snappy: PHP library allowing thumbnail, snapshot or PDF generation from a url or a html page. Wrapper for wkhtmltopdf/wkhtmltoimage.
• mikehaertl/phpwkhtmltopdf: A slim PHP wrapper around wkhtmltopdf with an easy to use and clean OOP interface
• h4cc/wkhtmltopdf-amd64: Convert html to pdf using webkit (qtwebkit). Static linked linux binary for amd64 systems.

Libraries for Node.JS using wkhtmltopdf #

• node-wkhtmltopdf: A Node.js wrapper for wkhtmltopdf.

Libraries for .NET using wkhtmltopdf #

• NReco.PdfGenerator: HTML to PDF converter for C#/.NET (WkHtmlToPdf wrapper).
• DinkToPdf: .NET Core P/Invoke wrapper for wkhtmltopdf library that uses Webkit engine to convert HTML pages to PDF.
• Wkhtmltopdf.NetCore: This project implements the library wkhtmltopdf for asp net core and a view engine, working in windows, macos, linux and docker.
• Haukcode.WkHtmlToPdfDotNet: .NET Core P/Invoke wrapper for wkhtmltopdf library that uses Webkit engine to convert HTML pages to PDF.
• TuesPechkin: A .NET wrapper for wkhtmltopdf.

How to remplace wkhtmltopdf in 2023? #

If you have built a web tool using a wkhtmltopdf library, it’s time to plan its replacement.

OK, but what are the alternatives to wkhtmltopdf?

If you work with Node.JS, a popular solution would be to use Puppeteer, a powerful browser automation tool that can convert the HTML content of a web page using its URL or convert an HTML file directly into PDF.

But be careful: Using Puppeteer on your own can be quite challenging, particularly when it comes to scaling, security, and ensuring compatibility with Docker. And it can be tricky if you handle big volumes and care about performance.

Another solution would be to use a managed API service, that would handle all the technical stuff and be compatible with any development language.

Well, that’s what we have done with Doppio, a developer friendly API based on Puppeteer that allows to convert HTML to PDF or PNG in no time.

Our basic plan allows to generate up to 400 documents per months, for free, without giving your credit card number.

Sounds good, right?