ScreenshotNeo

BlogGuides

wkhtmltopdf Pricing: Is It Free for Commercial Use?

wkhtmltopdf is published under LGPLv3, and its project site lists no commercial-use purchase price. Whether your distribution complies depends on how you package, modify, and convey it.

By the ScreenshotNeo team4 October 20265 min read

Direct answer: wkhtmltopdf is described by its project as open-source software under LGPLv3. The official downloads page lists releases and downloads, but no purchase fee or separate commercial-use price. That means there is no upstream commercial-use purchase price stated by the project; it does not mean every use is free of license conditions. The project overview identifies the license, and the downloads page provides release information.

Using wkhtmltopdf in your business or paid product is a different question from distributing it to customers. If you convey the tool, bundle it with your application, modify it, or link its components into a combined work, LGPLv3 conditions may apply. Review the license and notices for the exact build and its dependencies. For a product distribution decision, have counsel assess your architecture and distribution model.

1. What does “free for commercial use” mean here?

There are two separate questions:

  • Does upstream charge a commercial-use fee? The reviewed project pages describe wkhtmltopdf as LGPLv3 software and provide downloads; they do not state an upstream purchase price or commercial tier.
  • Can I use or distribute it without obligations? No such blanket conclusion follows from “free.” LGPLv3 has conditions, especially when you convey a combined work or distribute the covered component.

A third-party vendor may charge for support, hosting, packaging, or a service built around wkhtmltopdf. That would be that vendor’s charge, not an upstream commercial-use fee established by the project pages.

2. What LGPLv3 means when you distribute software

The Free Software Foundation’s LGPLv3 text allows a combined work to be conveyed under terms you choose, provided you meet the license conditions. Depending on how the covered component is linked and conveyed, those conditions can include prominent notices, copies of the GPL and LGPL license texts, and a compliant way for recipients to replace or relink the covered component with a modified version. A suitable shared-library arrangement can be relevant.

The right answer depends on the actual build and architecture. For example, merely invoking a separate command-line program is a different technical arrangement from bundling or statically linking libraries. Do not infer a legal outcome from that distinction alone: review the license files and notices for the binary and its dependencies, then get advice for your specific distribution.

Practical compliance review

  1. Identify the exact wkhtmltopdf binary and version you deploy, including how it was obtained.
  2. Inspect the build’s license file, notices, and dependency licenses, including Qt components and any vendor packaging.
  3. Write down whether you only run the tool internally, offer it as a service, or convey it to customers as part of a product or installer.
  4. Record whether you modified, bundled, statically linked, or dynamically linked any LGPL-covered component.
  5. For conveyed software, check the applicable notice, license-copy, source, and relinking or replacement requirements against the LGPLv3 text.
  6. Ask qualified counsel to assess the exact product and distribution arrangement if the answer affects a release or compliance commitment.

3. Is wkhtmltopdf still maintained?

Price and maintenance are separate considerations. The official downloads page identifies version 0.12.6 as the stable series and gives its release date as June 11, 2020. The upstream GitHub repository says it was archived on January 2, 2023. These facts do not by themselves establish whether a particular packaged build is suitable or secure; assess maintenance and compatibility for your environment separately. Official downloads · Archived upstream repository.

4. Security and deployment considerations

The project warns against processing untrusted HTML without sanitizing user-supplied HTML and JavaScript, noting that it can put the server at risk. Treat rendering as a security boundary: do not pass arbitrary user content to a privileged process without appropriate validation and isolation. Follow the project’s security warning and review your own deployment controls.

Also check whether your chosen build works with the operating system, fonts, libraries, and HTML features your application needs. The age of the stable release and the archived upstream repository make compatibility and maintenance important procurement questions, even though they do not change the stated license or purchase price.

5. If you need screenshots rather than PDF generation

wkhtmltopdf is for rendering HTML into PDF; its sibling wkhtmltoimage renders HTML into image formats. If your requirement is taking website screenshots through an API, ScreenshotNeo is an alternative to try first: it returns PNG, JPEG, WebP, or PDF from a GET request and bills only clean shots.

Or skip the browser setup

Make a single request to capture a page. See the ScreenshotNeo API documentation for options.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
open("shot.webp", "wb").write(r.content)
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await Bun.write('shot.webp', res);

ScreenshotNeo removes cookie banners, popups, and chat widgets before the shot. Bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000.

Sign up free for 1,000 screenshots a month, with no card required.

6. Common questions

Does wkhtmltopdf require a commercial license?

The project describes it as LGPLv3 software and does not list a separate commercial-use purchase price. Distribution conditions can still apply.

Can I use wkhtmltopdf in a paid product?

Commercial use is not the same as unrestricted redistribution. Check the exact binary, linked components, modifications, packaging, and LGPLv3 conditions for your product.

Does the LGPL mean I must publish my whole application’s source code?

That conclusion does not follow from this general summary. LGPLv3 addresses covered components and combined works with specific conditions; the obligations depend on how the software is combined and conveyed.

Is every wkhtmltopdf download or hosted service free?

No. The upstream pages reviewed do not state an upstream purchase fee, but third parties can charge for their own packaging, support, hosting, or services.

What should I check before shipping it?

Start with the license and notices supplied with the exact build and dependencies. Then assess how your application conveys or links those components, and seek counsel for a definitive distribution review.