headless browser automation / rendering
The seed is a Node.js driver on top of Puppeteer that provides a high-level API for screenshots, PDF generation, and text/HTML extraction from web pages.
Solves the same problem with a different architecture or at a different layer. Expect to rewrite the integration.
Choose when you need a language-agnostic PDF conversion service in Docker rather than an embeddable Node.js driver.
A developer-friendly API for converting many document formats into PDF files, and more!
Choose if you're in PHP and need HTML-to-PDF without a headless browser, at the cost of CSS fidelity.
HTML to PDF converter for PHP
Choose for Python-native HTML-to-PDF rendering without a browser, trading JS runtime for Python dependencies.
The awesome document factory
Choose for client-side PDF generation in the browser, avoiding server-side headless Chrome.
Client-side HTML-to-PDF rendering using pure JS.
Choose when you want PDF/image rendering without a headless browser, using Rust/WASM for lighter runtime.
Render OG images and paged PDFs from JSX, HTML, and CSS. No headless browser. Runs on Node.js, Cloudflare Workers, browsers, and Rust.
Choose when you want a managed headless browser service instead of embedding a driver in your Node app.
Deploy headless browsers in Docker. Run on our cloud or bring your own. Free for non-commercial uses.
Choose if your stack is Ruby and you need a low-level headless Chrome API without Puppeteer.
Headless Chrome Ruby API
Choose if you prefer Go and direct CDP control over a Node.js Puppeteer wrapper.
A Chrome DevTools Protocol driver for web automation and scraping.
Choose for Python browser automation without WebDriver, as an alternative to the Node.js driver.
Pydoll is a library for automating chromium-based browsers without a WebDriver, offering realistic interactions.
An earlier or more limited way to do the job. Still the right call when you need something small, proven, or CPU-only.
Choose when you only need HTML-to-PDF/image via Chrome and want a smaller library, accepting fewer features.
HTML to PDF or image (jpeg, png, webp) converter via Chrome/Chromium
Choose for a minimal screenshot-only library, accepting no PDF or text extraction.
Capture screenshots of websites
Does the same job, but ships as an app. Useful to a person, not swappable into a codebase.
Choose as a turnkey PDF generation queue with S3/webhooks, not as a library to embed.
🤖 A Node queue API for generating PDFs using headless Chrome. Comes with a CLI, S3 storage and webhooks for notifying subscribers about generated PDFs
Choose as a self-hosted PDF/PNG rendering service, but it's a standalone API not a swap-in library.
Web page PDF/PNG rendering done right. Self-hosted service for rendering receipts, invoices, or any content.
Choose as a CLI screenshot tool for quick captures, not as a library in your codebase.
Make website screenshots and mobile emulations from the command line.
Choose as a CLI for Markdown-to-PDF conversion, not as an embeddable driver.
Hackable CLI tool for converting Markdown files to PDF using Node.js and headless Chrome.
Choose as a Go CLI screenshot utility for security recon, not as a library.
🔍 gowitness - a golang, web screenshot utility using Chrome Headless
These projects were analysed and named browserless among their alternatives. The relationship is not symmetric — how browserless rates them is a separate judgement, made when browserless is analysed in its own right.
calls browserless “Broader headless-browser service that includes PDF generation; pick when you also need general automation/screenshots, not just HTML-to-PDF.”
Web page PDF/PNG rendering done right. Self-hosted service for rendering receipts, invoices, or any content.