browserless

browserless wraps Puppeteer, Google's headless-Chrome library, into a friendlier toolkit for the boring production jobs: screenshot a page, render it to PDF, or pull clean HTML and text out of a site. It handles the parts that usually bite you, retries, device emulation, and a built-in ad blocker so junk requests do not slow the render. MIT-licensed and free to run yourself. (This is Microlink's browserless, not the separate browserless.io service.)

As a library it drops into a Node project with npm, using either full Puppeteer or the lighter puppeteer-core. A CLI ships too for quick one-offs. The real ops cost is the same one every headless-Chrome setup pays: Chromium is memory-hungry and crashes under load, so running it at scale means babysitting browser instances, and that is the work you are choosing to own.

For occasional screenshots or PDFs inside an app you already run, the self-hosted library is free and enough. When you do not want to manage Chromium yourself, the same team offers Microlink, a pay-as-you-go hosted API that starts free. Solo and small teams: self-host and save the cash. Teams generating renders at volume, or tired of Chromium falling over: the hosted API is the honest trade, you pay to make the ops problem someone else's.

The catch is that headless Chrome is never truly set-and-forget. Self-hosting saves money right up until a traffic spike takes your browser pool down at 2 a.m. Price your own time into the decision.