Compute · Browser Rendering

A browser in a Worker, on demand

This site's Worker launches headless Chromium through the Browser Rendering binding and drives it with the Puppeteer API. Point it at any URL and get a screenshot, a PDF, or extracted page data — rendered at the edge, streamed back live.

Browser Rendering primer

Headless Chromium as a Worker binding

Two slides, then render any URL live from this site's Worker.

Browser Rendering

A headless Chromium inside your Worker

The browser binding gives a Worker access to a real browser running on Cloudflare's network. Drive it with the familiar Puppeteer API — navigate, click, screenshot, print — without running any browser infrastructure yourself.

The demo below calls puppeteer.launch(env.BROWSER) from this very site's Worker and streams the result back.

Worker

Your code + Puppeteer API

Browser binding

Headless Chromium at the edge

Result

PNG · PDF · DOM data

No servers, no fleet of browsers to patch and scale

What people build with it

One API, three everyday jobs

Anything that needs a real browser — JavaScript-heavy pages included — without owning the browser fleet.

Screenshots

Social cards, link previews, visual regression tests, uptime evidence.

PDFs

Invoices, reports, receipts — rendered from the same HTML your users see.

Extraction

Scrape rendered DOM, run QA flows, feed AI pipelines with real page data.

page.screenshot() · page.pdf() · page.evaluate()

Live rendering

Screenshot, PDF, or extract

Enter a URL, pick an output, and watch the edge browser do the work. JavaScript-heavy pages render fully — this is a real Chromium, not an HTML fetcher.

Render any URL from this Worker

puppeteer.launch(env.BROWSER) — headless Chromium on Cloudflare's network.

Try:

Pick a mode and hit Render — output appears here.