Cloudflare Introduces Kitesurf: An Agent-First Web Browser That Runs Entirely in V8 Isolates on Cloudflare Workers

Cloudflare just shipped something genuinely odd: a web browser with no Chromium, no rendering engine you've ever heard of running the show, built entirely inside V8 isolates on its own Workers platform. It's called Kitesurf, and it's free in beta right now through Browser Run. The pitch is simple. Chromium was designed for humans who want tabs, extensions, and smooth 60fps video. AI agents want none of that. They want clean text, low token counts, and cheap isolation, and running a full browser per agent session gets expensive fast when all you're doing is grabbing a screenshot or scraping some HTML.

So Cloudflare tore the browser apart and rebuilt only the pieces that matter. The Engine handles sessions and speaks the Chrome DevTools Protocol, so existing Puppeteer, Playwright, and MCP tooling keeps working with just one added parameter: browser=kitesurf. Actual page rendering happens in PageScript, a disposable Worker isolate per page that parses HTML and CSS using Blitz and Stylo, borrowed rendering tech from Servo and Firefox respectively, and runs occasional JavaScript through Boa, a Rust-based ECMAScript engine bolted onto a runtime that already runs on another runtime. It's runtimes all the way down, and yet it works — Kitesurf already clears more than 215,000 Web Platform Tests, with hundreds more passing each week.

The numbers explain why anyone would bother. On Cloudflare's own 14-URL benchmark, Kitesurf burned 380 milliseconds of CPU per screenshot versus 1,173 for Chromium, and 229ms versus 877ms for HTML extraction — three to nearly four times cheaper. Memory usage dropped even harder, from 271 MiB down to 57.8 MiB for screenshots, a 4.7x cut, and from roughly 274 MiB to 39.4 MiB for extraction, a 7x reduction. The catch is wall-clock time: Kitesurf runs about 1.7 to 1.8 times slower than Chromium, mostly because rasterizing images and encoding them takes longer in this stripped-down setup. For bursty, one-shot agent tasks where CPU and memory are what actually shows up on the bill, that trade-off leans heavily in Kitesurf's favor.

It's not a full replacement yet. Video, WebGL, TLS-fingerprint bot checks, and long authenticated sessions still need Chromium as the fallback, and Cloudflare is upfront about that. But for agents doing screenshots, scraping, PDF generation, or feeding search and RAG pipelines, this is a meaningfully cheaper lane. Cloudflare says it plans to open source the whole thing eventually, which would let anyone self-host their own agent browser instead of renting Chromium by the gigabyte-second.