Browser Run review

Browser Run (formerly Browser Rendering) gives Workers a Puppeteer/Playwright-compatible binding to headless browsers on Cloudflare’s network. It handles screenshots, PDF generation, scraping, and rendered-page testing without leaving you to operate a Chrome fleet.

Headless browsers are miserable infrastructure at scale: memory-hungry, crash-prone, and forever needing updates. Paying per use to hand that work off is easy to justify, and the binding keeps the browser close to existing Workers code.

Deducted points for concurrency limits that bite at scale, an inactivity timeout that can quietly end long-running jobs stuck waiting on slow pages (sessions have no maximum duration, and the timeout default is a fair guard against forgotten browsers racking up charges), occasional version-drift surprises between the managed browsers and what your scripts expect, and costs that deserve a spreadsheet before you commit a heavy workload. For low-to-moderate volume automation, it’s a clear win.